1. SOFTWARE TESTING Sampath Kumar Vuyyuru

2. INTRODUCTION Software Testing is a way of executing the software in a controlled manner to check whether the software works as specified. Software Testing is a way of executing the software in a controlled manner to check whether the software works as specified.

3. Software Testing Verification Verification Validation Validation

4. Software Specification and Test Design

6. Test Design Document Test Strategy Test Strategy Test Plan Test Plan Test Cases Test Cases Test Procedure Test Procedure

7. Types of Software Tests Unit Test Unit Test Integration Test Integration Test System Test System Test Regression Test Regression Test Acceptance Test Acceptance Test

8. Rules to be followed Software should be tested against what it is specified to do but not against what it is observed to do. That means the testing is totally dependent upon specification. Software should be tested against what it is specified to do but not against what it is observed to do. That means the testing is totally dependent upon specification. Both positive and negative tests should be performed. Both positive and negative tests should be performed. Testing hierarchically against each level of specification will help in identifying errors or bugs earlier. Testing hierarchically against each level of specification will help in identifying errors or bugs earlier. Always use test result documentation for future reference. Always use test result documentation for future reference.

9. Facts about testing Testing can only show the presence of faults not their absence. Testing can only show the presence of faults not their absence. A good test is one that has a high probability of finding a fault. A good test is one that has a high probability of finding a fault. A test can be called a successful test if it finds a fault. A test can be called a successful test if it finds a fault. A test can be called an unsuccessful test if it does not find a fault. A test can be called an unsuccessful test if it does not find a fault.

10. Conclusion

11. Any questions

12. Thank you