Defect prevention strategies in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main goal of defect prevention in software testing?

The main goal of defect prevention is to stop defects from occurring in the first place by improving processes and practices before the software is built.

beginner

Name two common defect prevention strategies.

Two common defect prevention strategies are code reviews and early requirement analysis to catch issues before coding starts.

intermediate

How does training help in defect prevention?

Training helps by teaching developers and testers best practices and standards, reducing mistakes caused by lack of knowledge.

intermediate

Explain the role of root cause analysis in defect prevention.

Root cause analysis finds the underlying reasons defects happen so teams can fix those causes and prevent similar defects in the future.

beginner

Why is early testing considered a defect prevention strategy?

Early testing finds defects soon after they are introduced, making it easier and cheaper to fix them before they cause bigger problems.

Which of the following is NOT a defect prevention strategy?

A Ignoring minor bugs

B Code reviews

C Root cause analysis

D Training developers

Ignoring minor bugs does not prevent defects; it allows defects to remain and possibly cause bigger issues later.

What is the benefit of performing requirement analysis early?

A It helps identify defects before coding

B It reduces the need for testing

C It increases the number of defects

D It delays the project timeline

Early requirement analysis helps find defects in requirements, preventing defects from being coded into the software.

Root cause analysis helps teams to:

A Fix defects without understanding why they happened

B Ignore defects that are hard to fix

C Find and fix the underlying causes of defects

D Create more defects intentionally

Root cause analysis focuses on understanding and fixing the real reasons defects occur to prevent recurrence.

Which activity is a proactive defect prevention technique?

A Fixing bugs after testing

B Performing code reviews during development

C Waiting for user feedback

D Skipping documentation

Code reviews during development help catch defects early, preventing them from progressing further.

Training developers on coding standards helps prevent defects by:

A Delaying the project

B Increasing the number of defects

C Making code harder to read

D Reducing mistakes caused by lack of knowledge

Training improves knowledge and skills, which reduces errors and defects in code.

Describe three key strategies used to prevent defects in software development.

Think about activities done before and during coding to avoid mistakes.

Explain how root cause analysis contributes to defect prevention.

Consider why defects happen repeatedly and how to stop that.

Practice

1. Which of the following is a primary goal of defect prevention in software testing?

easy

A. To find defects after software release

B. To stop defects before coding starts

C. To increase the number of test cases

D. To delay testing until the end of development

Solution

1. Step 1: Understand defect prevention purpose

   Defect prevention aims to stop bugs early, ideally before coding begins.

2. Step 2: Compare options with this goal

   Only To stop defects before coding starts matches this goal; others focus on later stages or unrelated actions.

3. Final Answer:

   To stop defects before coding starts -> Option B

4. Quick Check:

   Defect prevention = stop defects early [OK]

Hint: Defect prevention means stopping bugs before coding [OK]

Common Mistakes:

• Confusing defect prevention with defect detection
• Thinking testing only happens after coding
• Believing more test cases prevent defects
• Assuming testing should be delayed

2. Which of the following is a correct example of a defect prevention technique?

easy

A. Conducting code reviews before integration

B. Ignoring minor bugs during development

C. Writing test scripts after coding is complete

D. Skipping documentation to save time

Solution

1. Step 1: Identify defect prevention techniques

   Defect prevention includes activities like code reviews done early to catch issues.

2. Step 2: Evaluate each option

   Only Conducting code reviews before integration describes a proactive step before integration; others are reactive or harmful.

3. Final Answer:

   Conducting code reviews before integration -> Option A

4. Quick Check:

   Code reviews before integration = defect prevention [OK]

Hint: Code reviews before integration prevent defects early [OK]

Common Mistakes:

• Thinking testing after coding is prevention
• Ignoring small bugs helps prevent defects
• Skipping documentation is a prevention method
• Confusing defect detection with prevention

3. Consider this code snippet for a peer review process:

def review_code(code):
    defects_found = []
    for line in code:
        if 'TODO' in line:
            defects_found.append('Unfinished task')
    return defects_found

code_sample = ['print("Hello")', '# TODO: fix bug', 'return True']
defects = review_code(code_sample)
print(defects)

What will be the output after running this code?

medium

A. SyntaxError

B. []

C. ['TODO']

D. ['Unfinished task']

Solution

1. Step 1: Analyze the review_code function

   The function checks each line for 'TODO' and adds 'Unfinished task' to defects_found if found.

2. Step 2: Check code_sample lines for 'TODO'

   The second line contains '# TODO: fix bug', so 'Unfinished task' is added once.

3. Final Answer:

   ['Unfinished task'] -> Option D

4. Quick Check:

   TODO found = 'Unfinished task' added [OK]

Hint: Look for 'TODO' in lines to find defects [OK]

Common Mistakes:

• Assuming empty list if no exact match
• Confusing 'TODO' string with defect name
• Expecting syntax errors due to code formatting
• Ignoring the append operation

4. A team uses pair programming to prevent defects but notices many bugs still appear. What is the most likely issue?

medium

A. The pairs are not communicating effectively

B. Pair programming is not a defect prevention strategy

C. They are writing too many test cases

D. They are skipping code reviews

Solution

1. Step 1: Understand pair programming role

   Pair programming helps prevent defects by collaboration and communication.

2. Step 2: Identify why defects still appear

   If bugs persist, poor communication between pairs is a common cause.

3. Final Answer:

   The pairs are not communicating effectively -> Option A

4. Quick Check:

   Poor communication reduces pair programming effectiveness [OK]

Hint: Good communication is key in pair programming [OK]

Common Mistakes:

• Thinking pair programming doesn't prevent defects
• Blaming test case quantity instead of quality
• Ignoring the importance of code reviews
• Assuming pair programming alone fixes all bugs

5. A software team wants to reduce defects by combining multiple prevention strategies. Which combination is best to catch defects early and improve quality?

hard

A. Automated testing after coding, skipping reviews, and late integration

B. Skipping documentation, delaying testing, and using only manual code inspection

C. Code reviews before coding, pair programming during development, and static analysis tools

D. Writing test cases after release, ignoring minor bugs, and manual testing only

Solution

1. Step 1: Identify effective defect prevention methods

   Code reviews before coding, pair programming, and static analysis tools are proactive strategies.

2. Step 2: Evaluate each option's effectiveness

   Code reviews before coding, pair programming during development, and static analysis tools combines early and continuous prevention; others delay or skip key steps.

3. Final Answer:

   Code reviews before coding, pair programming during development, and static analysis tools -> Option C

4. Quick Check:

   Combine early reviews + collaboration + tools = best prevention [OK]

Hint: Combine early reviews, collaboration, and tools for best prevention [OK]

Common Mistakes:

• Choosing late testing as prevention
• Ignoring documentation and reviews
• Relying only on manual testing
• Skipping static analysis tools