Code coverage metrics in Software Engineering - Mini Project: Build & Apply

Understanding Code Coverage Metrics

📖 Scenario: You are part of a software development team. Your team wants to improve the quality of the code by measuring how much of the code is tested by automated tests. This measurement is called code coverage. You will learn about the basic types of code coverage metrics and how to identify them.

🎯 Goal: Build a simple list of common code coverage metrics with their descriptions. This will help you understand what each metric means and how it relates to testing your code.

📋 What You'll Learn

Create a dictionary named coverage_metrics with exact keys and descriptions

Add a variable named minimum_coverage to set a coverage threshold

Use a loop to select metrics with descriptions longer than 50 characters

Add a final summary string explaining the importance of code coverage

💡 Why This Matters

🌍 Real World

Software teams use code coverage metrics to understand how well their tests cover the codebase, helping to find untested parts and improve software quality.

💼 Career

Knowing code coverage metrics is important for software developers, testers, and quality assurance engineers to ensure reliable and maintainable code.

1

Create the code coverage metrics dictionary

Create a dictionary called coverage_metrics with these exact entries: 'Line Coverage' with value 'Measures the percentage of lines executed by tests.', 'Branch Coverage' with value 'Measures the percentage of branches (if-else) executed.', 'Function Coverage' with value 'Measures the percentage of functions called during testing.', and 'Statement Coverage' with value 'Measures the percentage of executable statements run.'.

Software Engineering

# Create the coverage_metrics dictionary with exact keys and values
# Your code here

Hint

Use curly braces {} to create a dictionary. Each key is a string with its description as the value.

2

Set the minimum coverage threshold

Create a variable called minimum_coverage and set it to the integer 80. This represents the minimum acceptable coverage percentage for your tests.

Software Engineering

coverage_metrics = {
    'Line Coverage': 'Measures the percentage of lines executed by tests.',
    'Branch Coverage': 'Measures the percentage of branches (if-else) executed.',
    'Function Coverage': 'Measures the percentage of functions called during testing.',
    'Statement Coverage': 'Measures the percentage of executable statements run.'
}
# Set the minimum_coverage variable to 80
# Your code here

Hint

Just assign the number 80 to the variable minimum_coverage.

3

Select metrics with long descriptions

Create a list called long_description_metrics that contains the keys from coverage_metrics whose descriptions have more than 50 characters. Use a for loop with variables metric and description to iterate over coverage_metrics.items().

Software Engineering

coverage_metrics = {
    'Line Coverage': 'Measures the percentage of lines executed by tests.',
    'Branch Coverage': 'Measures the percentage of branches (if-else) executed.',
    'Function Coverage': 'Measures the percentage of functions called during testing.',
    'Statement Coverage': 'Measures the percentage of executable statements run.'
}
minimum_coverage = 80
long_description_metrics = []
for metric, description in coverage_metrics.items():
    # Your code here

Hint

Use len(description) > 50 inside the loop to check description length.

4

Add a summary about code coverage importance

Create a string variable called coverage_summary with the exact text: 'Code coverage helps ensure tests check important parts of the code.'

Software Engineering

coverage_metrics = {
    'Line Coverage': 'Measures the percentage of lines executed by tests.',
    'Branch Coverage': 'Measures the percentage of branches (if-else) executed.',
    'Function Coverage': 'Measures the percentage of functions called during testing.',
    'Statement Coverage': 'Measures the percentage of executable statements run.'
}
minimum_coverage = 80
long_description_metrics = []
for metric, description in coverage_metrics.items():
    if len(description) > 50:
        long_description_metrics.append(metric)
coverage_summary = ""
# Your code here

Hint

Assign the exact sentence as a string to coverage_summary.

Practice

1. What does code coverage primarily measure in software testing?

easy

A. The number of developers working on the code

B. The number of bugs found in the code

C. The speed of the test execution

D. The percentage of code executed by tests

Solution

1. Step 1: Understand the purpose of code coverage

   Code coverage shows how much of the program's code is run during testing.

2. Step 2: Identify what code coverage measures

   It measures the percentage of code lines or branches executed by tests, not bugs or speed.

3. Final Answer:

   The percentage of code executed by tests -> Option D

4. Quick Check:

   Code coverage = executed code percentage [OK]

Hint: Code coverage = how much code tests run [OK]

Common Mistakes:

• Confusing coverage with bug count
• Thinking coverage measures test speed
• Assuming coverage counts developers

2. Which of the following is a common type of code coverage metric?

easy

A. Branch coverage

B. Memory coverage

C. Network coverage

D. User coverage

Solution

1. Step 1: Recall common code coverage types

   Common types include line coverage, branch coverage, and function coverage.

2. Step 2: Identify valid coverage types

   Branch coverage measures if all decision branches are tested; memory, network, and user coverage are not standard metrics.

3. Final Answer:

   Branch coverage -> Option A

4. Quick Check:

   Branch coverage is a standard metric [OK]

Hint: Branch coverage is a standard metric name [OK]

Common Mistakes:

• Choosing non-existent coverage types
• Confusing coverage with unrelated terms
• Ignoring common coverage categories

3. Consider a program with 100 lines of code. A test suite runs 80 lines and covers all branches in those lines. What is the approximate line coverage percentage?

medium

A. 20%

B. 100%

C. 80%

D. 50%

Solution

1. Step 1: Calculate line coverage

   Line coverage = (lines executed / total lines) x 100 = (80 / 100) x 100.

2. Step 2: Compute the percentage

   80 divided by 100 equals 0.8, multiplied by 100 gives 80% coverage.

3. Final Answer:

   80% -> Option C

4. Quick Check:

   80/100 = 0.8 = 80% [OK]

Hint: Divide executed lines by total lines, multiply by 100 [OK]

Common Mistakes:

• Confusing branch coverage with line coverage
• Calculating 100% because all branches covered
• Mixing up executed and total lines

4. A developer reports 90% code coverage, but some bugs remain. What is the most likely reason?

medium

A. High coverage does not guarantee all bugs are found

B. The coverage tool is broken

C. Tests ran too slowly

D. Code coverage measures bug count

Solution

1. Step 1: Understand code coverage limits

   Code coverage shows tested code amount but does not ensure test quality or bug detection.

2. Step 2: Identify why bugs remain

   Even with 90% coverage, tests might miss edge cases or logic errors causing bugs.

3. Final Answer:

   High coverage does not guarantee all bugs are found -> Option A

4. Quick Check:

   Coverage ≠ bug-free code [OK]

Hint: Coverage shows tested code, not bug absence [OK]

Common Mistakes:

• Assuming coverage means no bugs
• Blaming coverage tools without evidence
• Confusing coverage with test speed

5. You want to improve your test suite to cover all decision branches in a function with multiple if-else statements. Which approach best increases branch coverage?

hard

A. Write tests that only check the function's return value

B. Write tests that execute both true and false paths of each condition

C. Run the existing tests multiple times

D. Add print statements inside the function

Solution

1. Step 1: Understand branch coverage goal

   Branch coverage requires testing all possible paths of decision points (true and false).

2. Step 2: Choose the best testing approach

   Writing tests that cover both true and false branches ensures all decision paths run during testing.

3. Final Answer:

   Write tests that execute both true and false paths of each condition -> Option B

4. Quick Check:

   Branch coverage = test all decision paths [OK]

Hint: Test both true and false branches for full coverage [OK]

Common Mistakes:

• Testing only return values misses branches
• Rerunning tests doesn't increase coverage
• Adding print statements doesn't affect coverage