What does statement coverage measure in white-box testing?

What does statement coverage measure in white-box testing?

• A. It measures the time to execute a program.
• B. It measures whether each executable statement in the code has been executed.
• C. It measures the number of functions invoked.
• D. It measures network throughput.

Answer: (B)

Statement coverage measures whether every executable statement in the code has been executed by the test suite. By instrumenting the program or using a coverage tool, you track which statements actually run during tests and identify any statements that were never touched, helping to reveal dead code and gaps in test coverage. This focus on the basic building blocks of the code is different from performance metrics like how long the program runs, from function-level coverage that counts whether each function is invoked, or from network throughput, which is unrelated to code execution. So the idea is to ensure every executable statement is executed at least once.

Statement coverage measures whether every executable statement in the code has been executed by the test suite. By instrumenting the program or using a coverage tool, you track which statements actually run during tests and identify any statements that were never touched, helping to reveal dead code and gaps in test coverage. This focus on the basic building blocks of the code is different from performance metrics like how long the program runs, from function-level coverage that counts whether each function is invoked, or from network throughput, which is unrelated to code execution. So the idea is to ensure every executable statement is executed at least once.