1. C L I C K

2. E T W A T R E S I N G T O F S 3 2 1 E D N A M V A R I C C N E A R U A S Y T I S Q A U L

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. 3

4. Software Testing & Development Life Cycle

5. Unit Testing module to be tested Result Software Engineer Test Cases

6. Unit Testing module to be tested Interface Local Data Structures Boundary Conditions Independent paths Error Handling Paths Test Cases

7. Interface Module Local Data Structures Boundary Conditions Driver Independent paths Error Handling Paths stub stub Test Cases Result

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.

11. Top-Down Integration A Top module is tested with Stub B F G Stubs are all Replaced one at a time, Depth first C As new modules are integrated, some subset of tests is re-run D E

12. Bottom-Up Integration A B F G Drivers are replaced one at a time, Depth First. C Worker modules are grouped into builds and Integrated D E Cluster

13. Thread-Based Integration A Top Modules are tested with stubs B F G C Worker modules are grouped into builds and Integrated D E Cluster

14. Systems testing

15. Trivial example Scenario-based Testing

16. Trivial Example-System Testing

18. After each change

19. Entire test suite of a system must be run again.Need for an automatic test suite execution.

20. Test activities Expected results when the inputs are executed; and Execution conditions or execution environment in which the inputs are to be executed. Boils down to selecting and executing test cases. Test case consists of…… Set of test inputs, of if the program is non-terminating, a sequence of test inputs. These steps generally remain same from unit testing to system testing.

21. Test Case selection

23. A program

24. A process

25. A body of data

26. In many cases - directly form the requirements.

27. For example, a test case assessing performance - performance threshold.

29. Test Evaluation Compare the actual behavior with the expected behavior. Generally can be automated to an extend !!!!

31. Developers

32. Project Mangers etc. Generally can be automated to an extend !!!!

33. Key points A system typically undergoes a range of testing types. Each type of testing is aimed at detecting different kinds of failures Testing boils down to the selection and execution of test cases.

34. The ability to convert ideas to things is the secret of outward success. Created By Srivignesh