Testing methodologies


Following are the most common test methodologies that are followed to test
A product
1) Black box testing
2) White box testing
3) Gray box testing


Black box testing:-
Is the most common test methodology which is very frequently used to test the Product Testing is done with out knowing the internal structure of the application or the code. Black box testing can be considered testing with respect to the specifications.

Advantages of black box testing:-
1) More effective on larger units of code than white box testing
2) Tester needs no knowledge of implementation, including specific programming Lang.
3) Tester and programmer are independent of each other
4) Tests are done from a user's point of view
5) Will help to expose any ambiguities or inconsistencies in the specifications
6) Test cases can be designed as soon as the specifications are complete


White box testing:-
Examines the program structure and derive test data from the program logic. Structural testing is sometimes referred to as clear-box testing since white boxes are considered opaque and do not really permit visibility into the code.

Advantages of White Box Testing
1) Forces test developer to reason carefully about implementation
2) Approximates the partitioning done by execution equivalence
3) Reveals errors in "hidden" code
4) Beneficent side-effects
5) Optimizations (e.g. chartable that changes reps when size > 100)

Few of the white box testing techniques are
1) Syclomatic complexity
2) Branch coverage
3) Path coverage
4) Statement coverage

Gray box testing:-
Is a combination of black box and white box testing. In this type of test approach Part of the application will be tested with white box testing and remaining application features are tested with black box testing methodology.

(Note)Selection of the module which has the maximum impact on other modules of the
Application should be considered for white box testing and rest of the modules Should be tested with black box testing.

Test Report


Test report is a document which will be prepared at the end of the project or at the End of the build. It contains over all project proceedings along with the entire Project details .it has the following information

a) Test phase actual start date & end date (this can be for build wise also)
b) Environment (all operating systems & software’s)
c) Total Number of builds
d) Total number of Test cases executed (this can be for build wise also)
e) Total number of test cases passed
f) Total number of test cases failed
g) Total number of test cases blocked
h) Total number of bugs reported
i) Total number of major, minor, trivial bugs (this can be given build wise also)
j) Total effort (calculating in man hours)

          (Here ends the testing life cycle)