Test coverage metrics in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is test coverage in software testing?

Test coverage measures how much of the software's code or features are tested by the test cases. It helps find untested parts.

beginner

Name two common types of test coverage metrics.

Two common types are code coverage (which checks how much code is tested) and requirement coverage (which checks how many requirements are tested).

intermediate

What does statement coverage measure?

Statement coverage measures the percentage of executable statements in the code that have been run by tests.

intermediate

Why is 100% test coverage not always enough?

Because tests might run code but not check if it works correctly. Also, some bugs happen in combinations or unexpected inputs not covered by tests.

intermediate

What is branch coverage and why is it important?

Branch coverage measures if every possible branch (like if-else branches) in the code has been tested. It helps find missing tests for decision points.

Which test coverage metric measures the percentage of code lines executed by tests?

A Requirement coverage

B Statement coverage

C Branch coverage

D Path coverage

Statement coverage counts how many code statements are run during testing.

What does requirement coverage focus on?

A Testing all functions

B Testing all code branches

C Testing all user requirements

D Testing all variables

Requirement coverage checks if all specified user needs are tested.

Why might 100% code coverage still miss bugs?

A Because code coverage only measures requirements

B Because code coverage tools are inaccurate

C Because tests run too slowly

D Because tests might not check outputs or logic correctness

Running code doesn't guarantee the test checks if the result is correct.

Branch coverage ensures testing of:

A All decision paths like if-else

B All user stories

C All code statements

D All database queries

Branch coverage tests every possible decision path in the code.

Which metric helps identify untested requirements?

A Requirement coverage

B Code coverage

C Branch coverage

D Statement coverage

Requirement coverage tracks which requirements have test cases.

Explain what test coverage metrics are and why they matter in software testing.

Think about how much of the software is tested.

Describe the difference between statement coverage and branch coverage.

One counts lines, the other counts decision points.