Black box testing ( Behavioral/Closed box) | White box testing ( Structural/Gloss box) |
(1) This method focuses on functional requirements of the software i.e. it enables the software engineer to derive sets of input conditions that will fully exercise all functional requirements for a system. | (1) This method focuses on procedural details i.e. internal logic of a program. |
(2) Black box testing is applied during later stages of testing. | (2) White box testing is performed early in the testing process. |
(3) It disregards control structure of procedural design. | (3) It uses control structure of the procedural design to derive test cases. |
(4) It attempts to find errors in following categories: Interface errors, Incorrect or missing function, performance errors, Initialization and termination errors. | (4) White box testing attempts errors in following cases: Internal logic of your program and status of program. |
(5) Black box testing is “testing in large” i.e. testing bigger monolithic programs. | (5) White box testing is “testing in small” i.e. testing small program components (e.g. modules or small group of modules). |
(6) It includes the tests that are conducted at the software interface. | (6) A close examination of procedural detail is done. |
(7) Are used to uncover errors. | (7) Logical paths through the software are tested by providing test cases that exercise specific sets of conditions or loops. |
Advantages of Black box testing:
(1) Testers and programmers are independent of each other.
(2) Tests are done from user’s point of view.
(3) Test cases can be designed a soon as the specifications are complete.
Advantages of White box testing:
(1) It helps in optimizing the code.
(2) It helps in removing the extra line of codes, which bring in hidden defects.
(3) Every statement is tested thoroughly.
(4) Reveals errors in “hidden” code.
No comments:
Post a Comment