Lesson plan

Gray-box testing

Gray-box testing is a software testing method used to search for defects due to improper structure or application usage, where the tester has partial knowledge of the internal structure of the software. It is a combination of white-box testing, where the tester has broad access to the internal structure of the application, and black-box testing, where tester is unaware of the structure. The knowledge available to gray-box testers may comprise both high-level and detailed documentation, such as software architecture, Unified Modeling Language (UML) models, Web Services Description Language (WSDL) information and state models. Testing tools and techniques include exception handling, regression testing, functional testing, and orthogonal array testing. Gray-box testing is particularly used for testing web applications, that have distributed networks, and no source code or binaries that would allow for white box testing.

Back to article

Article summary

Gray-box testing is a software testing method used to search for defects due to improper structure or application usage, where the tester has partial knowledge of the internal structure of the software. It is a combination of white-box testing, where the tester has broad access to the internal structure of the application, and black-box testing, where tester is unaware of the structure. The knowledge available to gray-box testers may comprise both high-level and detailed documentation, such as software architecture, Unified Modeling Language (UML) models, Web Services Description Language (WSDL) information and state models. Testing tools and techniques include exception handling, regression testing, functional testing, and orthogonal array testing. Gray-box testing is particularly used for testing web applications, that have distributed networks, and no source code or binaries that would allow for white box testing.

Key claims

No claims recorded.

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  3. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.