Black box testing?? - csmates.com

Black-box testing

Black-box test design treats the system as a black-box. So it is a software testing technique whereby the internal workings of the item being tested are not known by the tester. It is also known as Functional testing.
black-box testing

Other names for black-box testing include specification testing, behavioral testing, data-driven testing, and input/output testing.

Generally, black-box testing attempts to uncover these things:
  • Incorrect functions
  • Data structure errors
  • Missing functions
  • Performance errors
  • Initialization and termination errors
  • External database access errors
The functionality of each module is tested with regard to its specifications and its context. Only the correct input/output relationship is scrutinized.

For example, in a black box test on a software design, the tester only knows the inputs and what the expected outcomes should be and not how the program arrives at those outputs. The tester does not ever examine the programming code and doesn't need any further knowledge of the program other than its specifications.

In general, every combination of input/output would require an inordinate number of test cases. Consequently, exhaustive black-box testing is usually either impossible or unreasonable. The art of testing is to design a small, manageable set of test cases so as to maximize the chances of detecting a fault while minimizing the redundancy (Duplication of data) amongst the cases.

Advantages of Black-box testing

  • The test is unbiased because the designer and the tester are independent of each other.
  • The tester does not need knowledge of any specific programming language.
  • The test is done from the point of view of the user, not the designer.
  • Test cases can be designed as soon as the specifications are complete.

Dis-advantages of black-box testing

  • The test can be redundant if the software designer has already run a test case.
  • The test cases are difficult to design.

Post a comment