Black box testing is a method of Software testing, which is also known as Specification-based testing, Behavioral testing, and Close box testing. Using the Software Requirements and Specifications provided by the Clients, Black box testing is performed to test the visual functioning of the software without looking into the internal code structure, design, and implementation. Black box testing is also known as Behavioral testing, as it focuses only on testing the functioning of Application under test. Black box testing is also known as Specification-based testing, as it is performed by verifying whether the Application under test is developed according to the Client provided Requirements and Specifications. It is called as Black box or Close box testing, as testers are not aware of the internal code structure, design and implementation of the Application under test. The below diagram depicts the Black box testing:
The below are few points which help us in understanding Black Box Testing in a better way:
- Black box testing a method of Software testing, which the testing team will perform without knowing the internal structure/design/implementation of the Application under test.
- Independent Testing teams having no programming knowledge will perform Black Box Testing.
- Black Box testing is generally performed as System Testing and Acceptance Testing.
- Black Box testing focuses on verifying the visual functioning of the Software using the Requirements and Specifications provided by the Business clients.
- The following are the different testing techniques involved in Black Box Testing:
- Equivalence Partitioning
- Boundary Value Analysis
- Decision Tables
- State Transition Testing
- Black box testing is not limited to Functional testing, instead, it involves the below types of testing:
- Functional Testing – To verify the Requirements and Specifications against the Application under test
- Non-Functional Requirements like performance testing, usability testing, accessibility testing etc. can be performed.
Please leave your questions/comments/feedback below.
Happy Learning 🙂
Arun Motoori (www.QAFox.com)