Black box testing

__NOTOC__Black box testing takes an external perspective of the test object to derive test cases. These tests can be functional or non-functional, though usually functional. The test designer selects valid and invalid input and determines the correct output. There is no knowledge of the test object's internal structure.

This method of test design is applicable to all levels of software testing: unit, integration, functional testing, system and acceptance. The higher the level, and hence the bigger and more complex the box, the more one is forced to use black box testing to simplify. While this method can uncover unimplemented parts of the specification, one cannot be sure that all existent paths are tested.

:"Compare with white box testing".

Test design techniques

Typical black box test design techniques include:
* Equivalence partitioning
* Boundary value analysis
* Decision table testing
* Pairwise testing
* State transition tables
* Use case testing
* Cross-functional testing

Hardware

Functional testing devices like power supplies, amplifiers, and many other simple function electrical devices is common in the electronics industry. Automated functional testing of specified characteristics is used for production testing, and part of design validation.

ee also

*
* Sanity testing
* Smoke testing
* Software testing
* Stress testing
* Test automation
* Web Application Security Scanner
* White box testing
* Boundary testing

External links

* [http://www.testingeducation.org/BBST/index.html Center for Software Testing Education & Research - Black Box Software Testing]
* [http://www.buzzle.com/editorials/4-10-2005-68349.asp White Box Testing Strategy]
* [http://www.testingbrain.com BLACK BOX Testing Details]
*BCS SIGIST (British Computer Society Specialist Interest Group in Software Testing): [http://www.testingstandards.co.uk/BS7925_3_4.zip "Standard for Software Component Testing"] , Working Draft 3.4, 27. April 2001.