Test metrics and KPIs in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to calculate the defect density.

Testing Fundamentals

defect_density = total_defects / [1]

Drag options to blanks, or click blank then click option'

Atotal_test_cases

Btotal_lines_of_code

Ctotal_test_runs

Dtotal_testers

Attempts:

3 left

💡 Hint

Common Mistakes

Using total_test_cases instead of total_lines_of_code.

Defect density is calculated as the number of defects divided by the total lines of code.

2fill in blank

medium

Complete the code to calculate test execution progress percentage.

Testing Fundamentals

progress = (executed_tests / [1]) * 100

Drag options to blanks, or click blank then click option'

Atotal_tests

Bpassed_tests

Cfailed_tests

Dblocked_tests

Attempts:

3 left

💡 Hint

Common Mistakes

Using passed_tests or failed_tests instead of total_tests.

Progress is the ratio of executed tests to total tests, multiplied by 100 for percentage.

3fill in blank

hard

Fix the error in the code to calculate test pass rate.

Testing Fundamentals

pass_rate = (passed_tests / [1]) * 100

Drag options to blanks, or click blank then click option'

Ablocked_tests

Btotal_tests

Cfailed_tests

Dexecuted_tests

Attempts:

3 left

💡 Hint

Common Mistakes

Using total_tests instead of executed_tests causes incorrect pass rate.

Pass rate is the percentage of passed tests out of executed tests, not total tests.

4fill in blank

hard

Fill both blanks to calculate defect removal efficiency.

Testing Fundamentals

defect_removal_efficiency = (defects_found_in_testing / [1]) * [2]

Drag options to blanks, or click blank then click option'

Atotal_defects

B100

Ctotal_test_cases

Dexecuted_tests

Attempts:

3 left

💡 Hint

Common Mistakes

Using total_test_cases or executed_tests instead of total_defects.

Defect removal efficiency is defects found in testing divided by total defects, multiplied by 100 for percentage.

5fill in blank

hard

Fill all three blanks to create a dictionary of test metrics with conditions.

Testing Fundamentals

metrics = {test + [1]: result for test, result in test_results.items() if result [2] [3]

Drag options to blanks, or click blank then click option'

A_id

B==

C'pass'

D!=

Attempts:

3 left

💡 Hint

Common Mistakes

Using '!=' instead of '==' causes wrong filtering.

This dictionary comprehension creates a dictionary of test IDs and results only for tests that passed.

Practice

1. Which of the following best describes a test metric in software testing?

easy

A. A tool used to automate tests

B. A measurable value that shows testing progress or quality

C. A list of test cases to be executed

D. A document describing software requirements

Solution

1. Step 1: Understand the definition of test metrics

   Test metrics are measurable values that help track testing progress or quality.

2. Step 2: Compare options with the definition

   Only A measurable value that shows testing progress or quality describes a measurable value related to testing progress or quality.

3. Final Answer:

   A measurable value that shows testing progress or quality -> Option B

4. Quick Check:

   Test metric = measurable value [OK]

Hint: Test metrics measure progress or quality, not tools or documents [OK]

Common Mistakes:

• Confusing test metrics with test cases
• Thinking test metrics are tools
• Mixing metrics with documentation

2. Which of the following is the correct formula for calculating Defect Density?

easy

A. Number of defects / Size of software module

B. Number of test cases executed / Total test cases

C. Total test time / Number of testers

D. Number of passed tests / Number of failed tests

Solution

1. Step 1: Recall Defect Density formula

   Defect Density is calculated as the number of defects divided by the size of the software module (e.g., lines of code).

2. Step 2: Match formula with options

   Number of defects / Size of software module matches the correct formula; others describe different metrics.

3. Final Answer:

   Number of defects / Size of software module -> Option A

4. Quick Check:

   Defect Density = defects / size [OK]

Hint: Defect Density = defects divided by size of module [OK]

Common Mistakes:

• Mixing defect density with test execution ratio
• Confusing numerator or denominator
• Using passed tests instead of defects

3. Given the following data:
Total test cases = 100
Test cases executed = 80
Test cases passed = 60
Defects found = 10
What is the Test Execution Rate (in percentage)?

medium

A. 90%

B. 60%

C. 75%

D. 80%

Solution

1. Step 1: Understand Test Execution Rate formula

   Test Execution Rate = (Test cases executed / Total test cases) * 100

2. Step 2: Calculate using given data

   (80 / 100) * 100 = 80%

3. Final Answer:

   80% -> Option D

4. Quick Check:

   Execution Rate = executed / total * 100 = 80% [OK]

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

Common Mistakes:

• Using passed tests instead of executed tests
• Forgetting to multiply by 100 for percentage
• Mixing up numerator and denominator

4. A test report shows:
Total tests = 50
Passed tests = 45
Failed tests = 10
Identify the error in the report.

medium

A. Total tests should equal passed plus failed tests

B. Failed tests cannot be more than passed tests

C. No error, the report is correct

D. Passed tests cannot be more than total tests

Solution

1. Step 1: Check sum of passed and failed tests

   Passed tests (45) + Failed tests (10) = 55, which is greater than total tests (50).

2. Step 2: Verify consistency of totals

   Total tests should equal the sum of passed and failed tests for accuracy.

3. Final Answer:

   Total tests should equal passed plus failed tests -> Option A

4. Quick Check:

   Total = passed + failed [OK]

Hint: Total tests must equal passed plus failed tests [OK]

Common Mistakes:

• Ignoring mismatch in totals
• Assuming passed tests can exceed total
• Not validating report consistency

5. You want to improve your testing process by focusing on the most important metrics. Which KPI should you track to measure the effectiveness of your testing in finding defects?

hard

A. Test Case Preparation Status

B. Test Execution Rate

C. Defect Detection Percentage (DDP)

D. Test Environment Availability

Solution

1. Step 1: Understand KPI purpose

   KPIs highlight key metrics to track for specific goals, here to measure defect finding effectiveness.

2. Step 2: Identify KPI related to defect detection

   Defect Detection Percentage (DDP) measures how many defects are found compared to total defects, showing testing effectiveness.

3. Step 3: Compare other options

   Test Execution Rate measures progress, Test Case Preparation Status and Environment Availability do not measure defect finding effectiveness.

4. Final Answer:

   Defect Detection Percentage (DDP) -> Option C

5. Quick Check:

   Effectiveness KPI = Defect Detection Percentage [OK]

Hint: Track Defect Detection Percentage to measure defect finding [OK]

Common Mistakes:

• Confusing progress metrics with effectiveness KPIs
• Choosing environment or preparation metrics
• Ignoring the goal of measuring defect detection