Branch coverage in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is branch coverage in software testing?

Branch coverage measures whether each possible branch (true/false decision) in the code has been executed at least once during testing.

beginner

Why is branch coverage important?

It helps find bugs in decision points by ensuring all branches of conditional statements are tested, improving test thoroughness.

intermediate

How does branch coverage differ from statement coverage?

Statement coverage checks if each line runs, but branch coverage checks if each decision path (true/false) runs, making it more detailed.

beginner

Example: If a code has an if-else statement, how many branches are there?

There are two branches: one for the 'if' condition being true, and one for it being false (the 'else').

intermediate

What does 100% branch coverage mean?

It means every possible branch in the code has been executed at least once during testing, covering all decision outcomes.

What does branch coverage measure in testing?

A Whether the code is free of syntax errors

B Whether each line of code is executed

C Whether the software meets user requirements

D Whether each decision branch (true/false) is executed

Branch coverage focuses on testing all possible paths of decisions, like true and false branches.

If an if statement has no else, how many branches does it have?

A Two

B One

C Three

D Zero

Even without an else, the if condition can be true or false, so there are two branches.

Which coverage is more detailed: statement coverage or branch coverage?

A Both are the same

B Statement coverage

C Branch coverage

D Neither

Branch coverage checks all decision paths, which is more detailed than just checking lines executed.

What does 100% branch coverage guarantee?

A All decision outcomes are tested

B All code lines are executed

C No bugs remain

D All user requirements are met

100% branch coverage means every true and false path in decisions has been tested.

Why might branch coverage miss some bugs?

A Because it only tests syntax

B Because it doesn't check data values inside branches

C Because it tests all user inputs

D Because it ignores decision points

Branch coverage ensures paths run but may miss bugs related to specific data values inside those paths.

Explain branch coverage and why it is useful in testing.

Think about how decisions in code create different paths to test.

Describe how you would achieve 100% branch coverage for a simple if-else statement.

Consider testing both outcomes of the condition.