A Guide To: White Box, Black Box, and Gray Box testing

White Box testing

The main purpose of White Box testing is to check the code and the internal structure of a particular product that is being tested. A tester is looking at the input-output processes here, with a heavy focus on the inner workings of the product.

  • Loss of security
  • Workflow and scenarios for certain input processes
  • Conditional loop issues
  • Object malfunction
  • Wrong output

Black Box testing

Behavioral, or Black Box testing, is a method whereby the tester does not know what they are testing. The internal layout, application, and design of the product remain unknown to the quality assurance specialist. These tests are usually functional, and web pages are studied by using a browser, and some data is input and the outcomes are checked.

  • Integration testing
  • Acceptance testing
  • Boundary Value Analysis (input boundary determination)
  • Equivalence Partitioning (valid and invalid partitions)

Gray Box testing

Gray Box testing is a mix of White Box and Black Box testing. The tester aims to find all the possible code and functioning issues by using this method. At this stage a specialist is able to test the end-to-end functions.

  • Matrix testing
  • Regression testing
  • Orthogonal Array Testing or OAT

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store