Defect prevention strategies in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to identify the primary goal of defect prevention.

Testing Fundamentals

def defect_prevention_goal():
    return "[1]"

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

AReduce defects before they occur

BFind defects after release

CIgnore defects

DIncrease defect count

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing options that focus on finding defects after release.

The main goal of defect prevention is to reduce defects before they occur in the software.

2fill in blank

medium

Complete the code to select a common defect prevention technique.

Testing Fundamentals

def defect_prevention_technique():
    return "[1]"

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

AIgnoring requirements

BSkipping tests

CCode reviews

DDelaying fixes

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing options that ignore or delay defect handling.

Code reviews help catch defects early, which is a key defect prevention technique.

3fill in blank

hard

Fix the error in the code that applies defect prevention by using a checklist.

Testing Fundamentals

def apply_defect_prevention():
    checklist = ['requirements', 'design', 'code']
    for item in checklist:
        if item == '[1]':
            print('Check completed')

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

Atest

Breview

Cdeploy

Dcode

Attempts:

3 left

💡 Hint

Common Mistakes

Using a word not in the checklist for the condition.

The checklist includes 'code', so the condition should check for 'code' to print the message.

4fill in blank

hard

Fill both blanks to complete the defect prevention code that logs defects and notifies the team.

Testing Fundamentals

def log_and_notify(defect):
    log = []
    log.append([1])
    if [2]:
        notify_team(defect)

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

Adefect.description

Bdefect.severity == 'high'

Cdefect.severity != 'low'

Ddefect.id

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect comparison operators or logging wrong defect attributes.

The defect description is logged, and the team is notified only if severity equals 'high'.

5fill in blank

hard

Fill all three blanks to create a defect prevention function that filters defects by type and counts them.

Testing Fundamentals

def count_defects(defects):
    filtered = [d for d in defects if d.type == [1]]
    count = len(filtered)
    return [2] + [3]

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

A'UI'

Bcount

C0

D'backend'

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong defect types or incorrect return expressions.

The function filters defects of type 'UI', counts them, and returns the count plus zero (no offset).

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