Software Testing
“ Testing is the process of exercising a program with the specific intent of finding errors prior to delivery to the end user.”
Generic characteristics:-
 A software team should conduct effective formal technical reviews, so that many errors will be eliminated before testing commences.
 Testing begins at the component level works “outward” toward the integration of the entire system.
 Different testing techniques are appropriate at different points in time.
 Testing is conducted by the developer of the software and ( for large projects) an independent test group.
 Debugging must be accommodated in any testing strategy.
Verification And Validation( V&V)
“ Verification refers to the set of activities that ensure that software correctly implements a specific function”
“ Validation refers to a different set of activities that ensure that the software that has been built is traceable to customer requirements”
*Verification:- Are we building the product right?
*Validation:- Are we building the right product?
Strategic Issues
Following issues must be addressed if a successful software testing strategy is to be implemented:-
 State testing objectives explicitly( Test coverage, mean time to failure, cost incurred, test effectiveness).
 Understand the user of the software and develop a profile for each user category.
 Develop a testing plan that emphasizes “ rapid cycle testing”.
 Use effective formal technical reviews as a filter prior to testing.
 Conduct formal technical reviews to assess the test strategy and test cases themselves.
 Develop a continuous improvement approach for the testing process.
Criteria for completion of Testing:-
We are never done testing. Every time the customer executes a computer program, the program is being tested.

download full project
http://huson.edu.jo/~dr_mjab/SD/ch13.doc