logging in or signing up software testing and quality assurance Vigneshasromio Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINT lite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: Embed: Flash iPad Copy Does not support media & animations WordPress Embed Customize Embed URL: Copy Thumbnail: Copy The presentation is successfully added In Your Favorites. Views: 252 Category: Education License: All Rights Reserved Like it (0) Dislike it (0) Added: May 13, 2011 This Presentation is Public Favorites: 0 Presentation Description download the ppt and see it.Give your feed back at email@example.com Comments Posting comment... Premium member Presentation Transcript Slide 1: C L I C K Slide 2: 3 2 1 M A V E R I C S O F W A R E T E S T I N G N Q A I A T Y A S S U R A E D L T U C N Slide 3: 3 Testing Policy Only exhaustive testing can show a program is free from defects. However, exhaustive testing is impossible; Testing policies define the approach to be used in selecting system tests; For example, All functions accessed through menus should be tested; Combinations of functions accessed through the same menu should be tested; Where user input is required, all functions must be tested with correct and incorrect input. Slide 4: Software Testing & Development Life Cycle Slide 5: module to be tested Software Engineer Result Test Cases Unit Testing Slide 6: module to be tested Test Cases Interface Local Data Structures Unit Testing Boundary Conditions Independent paths Error Handling Paths Slide 7: Test Cases Interface Local Data Structures Boundary Conditions Independent paths Error Handling Paths Result Slide 8: Integration Testing Involves building a system from its components and testing it for problems that arise from component interactions. Top-down integration Develop the skeleton of the system and populate it with components. Bottom-up integration Integrate infrastructure components then add functional components. To simplify error localisation, systems should be incrementally integrated. Slide 9: Integration Testing The Big-bang Approach. Incremental Approach. Slide 10: Top-Down Integration Top module is tested with Stub Stubs are all Replaced one at a time, Depth first As new modules are integrated, some subset of tests is re-run A B C F G D E Slide 11: Bottom-Up Integration A B F G Drivers are replaced one at a time, Depth First. Worker modules are grouped into builds and Integrated C D E Cluster Slide 12: Thread-Based Integration A B F G Top Modules are tested with stubs Worker modules are grouped into builds and Integrated C D E Cluster Slide 13: Systems testing Slide 14: Trivial example Scenario-based Testing Slide 15: Trivial Example-System Testing Slide 16: Regression Testing Change do not always effect the entire program. After each change Entire test suite of a system must be run again. Need for an automatic test suite execution. Slide 17: Test activities These steps generally remain same from unit testing to system testing. Slide 18: Test Case selection Slide 19: Test Oracles Slide 20: Text Execution Test inputs on the ‘program-under-test’ Record the actual behavior. Generally can be automated to an extend !!!! Slide 21: Test Evaluation Compare the actual behavior with the expected behavior. Generally can be automated to an extend !!!! Slide 22: Test Reporting Report the outcome of the testing. Developers Project Mangers etc. Generally can be automated to an extend !!!! Slide 23: Key points Each type of testing is aimed at detecting different kinds of failures Testing boils down to the selection and execution of test cases. A system typically undergoes a range of testing types. Slide 24: Created By Srivignesh The ability to convert ideas to things is the secret of outward success. You do not have the permission to view this presentation. In order to view it, please contact the author of the presentation.