White box testing

White Box Testing (also known as Clear Box Testing, Open Box Testing, Glass Box Testing, Transparent Box Testing, Code-Based Testing, or Structural Testing) is a software testing method in which the internal structure/design/implementation of the item being tested is known to the tester. The tester chooses inputs to exercise paths through the code and determines the appropriate outputs. Programming know-how and the implementation of knowledge are essential. White box testing is testing beyond the user interface and into the nitty-gritty of a system.

This method is named so because the software program, according to the tester, is like a white/transparent box; inside which one clearly sees.

White Box Testing – Example
A tester, usually a developer as well, studies the implementation code of a certain field on a web page, determines all legal (valid and invalid) AND illegal inputs, and verifies the outputs against the expected outcomes, which is also determined by studying the implementation code.
White Box Testing – Levels applicable

White Box Testing method is applicable to the following levels of software testing:

  • Unit Testing: For testing paths within a unit
  • Integration Testing: For testing paths between units
  • System Testing: For testing paths between subsystems

However, it is mainly applied to Unit Testing.

White Box Testing – Advantages
Testing can be commenced at an earlier stage. One need not wait for the GUI to be available.
Testing is more thorough, with the possibility of covering most paths.
White Box Testing – Disadvantages

Since tests may involve high complexity, they demand highly skilled resources who possess in-depth knowledge of programming and implementation. Test script maintenance can be a burden if the implementation changes too frequently. This method of testing is closely tied to the application being tested, tools to cater to every kind of implementation/platform may not be readily available.

White Box Testing is like the work of a mechanic who examines the engine to see why the car is not moving.

ISTQB definition:
Testing based on an analysis of the internal structure of the component or system.
White-box test design technique: Procedure to derive and/or select test cases based on an analysis of the internal structure of a component or system.
  • R@bbIT career fair 2025
    IT students โ€“ itโ€™s time to connect! If tech is your passion and future, you canโ€™t miss this! Join us at the 10th edition of the r@bbIT career fair at West Pomeranian University – an event where
  • Embedded World 2025 recap
    The Embedded World 2025 is now behind us, but the impression remains. A valuable experience of three days filled with meetings and discussions with professionals from diverse sectors, all focused on
  • Embedded World 2025-day 2
    It was a fantastic day one. Are you ready for the second round? Still havenโ€™t visited our booth? Take the opportunity to meet GRYFTEC team on-site, ๐—›๐—ฎ๐—น๐—น ๐Ÿฐ, ๐—ฏ๐—ผ๐—ผ๐˜๐—ต ๐Ÿฐ-๐Ÿฑ๐Ÿฌ๐Ÿญ๐—ฏ.
  • Embedded World Exhibition&Conference 2024Welcome to Embedded World 2025
    We are excited to be back at the Embedded World and ready for three days of networking, cutting-edge innovation, and industry connections. The traffic in the aisles and high energy clearly show a
  • Embedded World Exhibition&Conference 2024The countdown to EW25 begins
    The countdown begins, only a few days until the Embedded World Exhibition&Conference, the biggest event that brings the entire embedded community together. Do you have a new project in mind, need
  • GRYFTECEmbedded Systems Sp. z o.o.
  • ul. 1 Maja 3871-627 Szczecin, Poland
  • + 48 91 85 11 660info@gryftec.com
GRYFTEC Embedded Systems
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.