1. Static Testing • Static testing refers to testing something that’s not executing - examining and reviewing it. Dynamic Testing • Dynamic testing is what you would normally think of testing - executing and using the software.

2. Dynamic Testing • Techniques used are determined by the type of testing that must be conducted • Functional • Structural

3. Functional Testing • Structure of the program is not considered. • Test cases are decided based on the requirements or specification of the program or module • Hence it is often called as “Black Box Testing”.

4. Structural Testing • Concerned with testing ,the implementation of the program. • Focus on the internal structure of the program. • The intent of structural testing is not to exercise all the different input or output condition but to exercise the different programming structures and data structures in the program.

5. Testing Levels • Unit Testing • Integration Testing • System Testing • User Acceptance Testing (UAT)

6. Unit Testing • Test each module individually. • Follows a white box testing (Logic of the program)

7. Integration testing • Integrate two or more module.i.e. communicate between the modules. • Follow a white box testing (Testing the code)

8. System Testing • confirms that the system as a whole delivers the functionality originally required. • Follows the black box testing.

9. User Acceptance Testing (UAT) • Building the confidence of the client and users is the role of the acceptance test phase. • It is depend on the business scenario.

10. V-Model Business scenario UAT SRS System HLD Integration LLD Unit

11. Testing Techniques • White Box • Black Box • Incremental • Thread

12. White Box Testing Techniques • Statement coverage – execute all statements at least once. • Decision coverage - execute each decision direction at least once. • Condition coverage – execute each decision with all possible outcomes at least once

13. Black Box Testing Techniques * Equivalence Partitioning * Boundary Analysis * Error Guessing

14. Equivalence Partitioning • A subset of data that is representative of a larger class • For example, a program which edits credit limits within a given range ($10,000 - $15,000 would have 3 equivalence classes: • Less than $10,000 (invalid) • Between $10,000 and $15,000 (valid) • Greater than $15,000 (invalid)

15. Boundary Analysis A technique that consists of developing test cases and data that focus on the input and output boundaries of a given function

16. Boundary Analysis continued... • In the same credit limit example, boundary analysis would test: • Low boundary plus or minus one ($9,999 and $10,001) • On the boundary ($10,000 and $15,000) • Upper boundary plus or minus one ($14,999 and $15,001)

17. Error Guessing • Based on the theory that test cases can be developed based on experience of the Test Engineer • For example, in an example where one of the inputs is the date, a test engineer might try February 29,2000 or 9/9/99

18. Incremental Testing • A disciplined method of testing the interfaces between unit-tested programs as well as between system components • Incremental Testing Types - Top-down - Bottom-up

19. Top-Down • Begins testing from the top of the module hierarchy and works down to the bottom using interim stubs to simulate lower interfacing modules or programs

20. Bottom-Up • Begins testing from the bottom of the hierarchy and works up to the top • Bottom-up testing requires the development of drivermodules which provide the test input, call the module or program being testing, and display test output

21. Thread Testing • A technique, often used during early integration testing • Demonstrates key functional capabilities by testing a string of units that accomplish a specific function in the application

22. Illustrates various techniques used throughout the teststages