Defect density and detection rate in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is defect density in software testing?

Defect density is the number of defects found in a software module divided by the size of that module, usually measured in lines of code or function points. It helps measure software quality.

beginner

How do you calculate detection rate in testing?

Detection rate is calculated by dividing the number of defects found during testing by the total number of defects (found plus those found later). It shows how effective testing is at finding bugs.

intermediate

Why is defect density useful for project managers?

Defect density helps project managers understand which parts of the software are more error-prone and may need more attention or testing effort.

intermediate

What does a high detection rate indicate about a testing process?

A high detection rate means the testing process is good at finding defects before the software is released, reducing the chance of bugs reaching users.

beginner

If a module has 10 defects and 2000 lines of code, what is its defect density?

Defect density = Number of defects / Size of module = 10 / 2000 = 0.005 defects per line of code.

What does defect density measure?

A Number of defects per size of software

B Number of test cases executed

C Time taken to fix defects

D Number of users reporting bugs

Defect density measures how many defects exist per unit size of software, showing quality.

Detection rate is best described as:

A Defects found during testing divided by total defects

B Total defects divided by defects found during testing

C Number of test cases passed

D Time spent testing

Detection rate shows how many defects testing found compared to all defects.

A low defect density means:

A Software has many defects

B Software has fewer defects per size

C Testing was not done

D Software is very large

Low defect density means fewer defects per unit size, indicating better quality.

If detection rate is 100%, it means:

A Defects were found after release

B No defects were found

C All defects were found during testing

D Testing was skipped

100% detection rate means testing found every defect before release.

Which metric helps decide where to focus testing effort?

A Code coverage

B Detection rate

C Test case count

D Defect density

Defect density shows which parts have more defects and need more testing.

Explain defect density and why it is important in software testing.

Think about defects per size of software and what it tells us.

Describe detection rate and how it helps improve the testing process.

Consider how many defects testing finds compared to total defects.

Practice

1. What does defect density measure in software testing?

easy

A. Percentage of passed test cases

B. Total number of test cases executed

C. Number of defects per size of software

D. Time taken to fix defects

Solution

1. Step 1: Understand the definition of defect density

   Defect density is defined as the number of defects found divided by the size of the software (e.g., lines of code or function points).

2. Step 2: Compare options with the definition

   Only Number of defects per size of software correctly describes defect density as defects per size of software.

3. Final Answer:

   Number of defects per size of software -> Option C

4. Quick Check:

   Defect density = Defects / Size [OK]

Hint: Defect density = defects divided by software size [OK]

Common Mistakes:

• Confusing defect density with total defects
• Mixing defect density with test case count
• Thinking defect density measures fix time

2. Which formula correctly calculates the detection rate during testing?

easy

A. (Number of defects found) / (Total defects present)

B. (Total defects present) / (Number of defects found)

C. (Number of test cases passed) / (Total test cases)

D. (Number of defects fixed) / (Number of defects found)

Solution

1. Step 1: Recall detection rate meaning

   Detection rate measures how many defects testing finds out of all defects present.

2. Step 2: Match formula to definition

   (Number of defects found) / (Total defects present) correctly shows detection rate as defects found divided by total defects present.

3. Final Answer:

   (Number of defects found) / (Total defects present) -> Option A

4. Quick Check:

   Detection rate = Found / Total [OK]

Hint: Detection rate = defects found ÷ total defects [OK]

Common Mistakes:

• Reversing numerator and denominator
• Confusing detection rate with pass rate
• Using fixed defects instead of found defects

3. A software module has 5000 lines of code and 25 defects found. What is the defect density?

medium

A. 0.5 defects per line

B. 0.05 defects per line

C. 2 defects per line

D. 0.005 defects per line

Solution

1. Step 1: Apply defect density formula

   Defect density = Number of defects / Size of software = 25 / 5000.

2. Step 2: Calculate the value

   25 divided by 5000 equals 0.005 defects per line.

3. Final Answer:

   0.005 defects per line -> Option D

4. Quick Check:

   25 ÷ 5000 = 0.005 [OK]

Hint: Divide defects by lines of code for defect density [OK]

Common Mistakes:

• Multiplying instead of dividing
• Using wrong units or decimal places
• Confusing defect density with total defects

4. During testing, 40 defects were found but the total defects present were 50. The detection rate was calculated as 1.25. What is the error?

medium

A. Detection rate cannot be greater than 1

B. Detection rate should be less than 0.5

C. Detection rate equals defects fixed, not found

D. Detection rate is unrelated to defects

Solution

1. Step 1: Understand detection rate limits

   Detection rate is defects found divided by total defects, so it must be between 0 and 1.

2. Step 2: Check given value

   Given detection rate is 1.25, which is greater than 1, so it is invalid.

3. Final Answer:

   Detection rate cannot be greater than 1 -> Option A

4. Quick Check:

   Detection rate ≤ 1 [OK]

Hint: Detection rate max is 1 (100%) [OK]

Common Mistakes:

• Allowing detection rate > 1
• Mixing detection rate with fixed defects
• Ignoring ratio limits

5. A project has 10,000 lines of code with 80 defects found during testing. Later, 20 more defects were discovered after release. What is the updated defect density and detection rate?

hard

A. Defect density: 0.008; Detection rate: 1.0

B. Defect density: 0.01; Detection rate: 0.8

C. Defect density: 0.01; Detection rate: 1.0

D. Defect density: 0.008; Detection rate: 0.8

Solution

1. Step 1: Calculate total defects and defect density

   Total defects = 80 found + 20 discovered = 100. Defect density = total defects / lines of code = 100 / 10,000 = 0.01.

2. Step 2: Calculate detection rate

   Detection rate = defects found / total defects = 80 / 100 = 0.8.

3. Step 3: Match calculations to options

   Defect density is 0.01 and detection rate is 0.8, but Defect density: 0.008; Detection rate: 0.8 shows defect density as 0.008 which is incorrect. Defect density: 0.01; Detection rate: 0.8 shows correct defect density but detection rate 0.8. Defect density: 0.008; Detection rate: 0.8 has defect density 0.008 which is wrong. Defect density: 0.01; Detection rate: 0.8 matches defect density 0.01 and detection rate 0.8 correctly.

4. Final Answer:

   Defect density: 0.01; Detection rate: 0.8 -> Option B

5. Quick Check:

   Defect density = 100/10000=0.01; Detection rate = 80/100=0.8 [OK]

Hint: Add all defects for density; found ÷ total for detection rate [OK]

Common Mistakes:

• Using only found defects for defect density
• Ignoring defects found after release
• Mixing detection rate numerator and denominator