Defect reporting best practices in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Key elements in a defect report

Which of the following is NOT a key element to include in a clear defect report?

A Expected and actual results

B Tester’s personal opinion about the developer

C Environment details like browser or OS version

D Steps to reproduce the defect

💡 Hint

Think about what information helps fix the defect, not personal feelings.

A good defect report focuses on facts and clear information to help developers reproduce and fix the issue. Personal opinions do not help and should be avoided.

❓ assertion

intermediate

Correct assertion for defect severity

You want to write an assertion to check if a defect's severity is set to 'Critical'. Which assertion is correct?

Testing Fundamentals

defect = {'id': 101, 'severity': 'Critical'}

# Choose the correct assertion below:

A assert defect.get('severity') == 'Critical'

B assert defect['severity'] == 'critical'

C assert defect['severity'] = 'Critical'

D assert defect['severity'] != 'Critical'

💡 Hint

Remember Python is case-sensitive and assignment '=' is not used in assertions.

Option A correctly uses the get method and matches the exact case 'Critical'. Option A fails due to case mismatch. Option A uses assignment instead of comparison. Option A asserts the opposite.

🔧 Debug

advanced

Identify the error in defect report code

What error will this defect report submission code raise?

Testing Fundamentals

def submit_defect(defect):
    if defect['title'] and defect['description']:
        print('Defect submitted')
    else:
        print('Missing information')

submit_defect({'title': 'Crash', 'description': 'App crashes on start'})

A TypeError because defect is not a dictionary

B KeyError because 'title' key is missing

C SyntaxError due to missing colon after else

D No error, prints 'Defect submitted'

💡 Hint

Check the syntax of if-else statements carefully.

The else statement is missing a colon at the end, causing a SyntaxError.

❓ framework

advanced

Best practice for defect tracking tool usage

Which practice is best when using a defect tracking tool?

A Update defect status promptly and add comments when progress is made

B Only update defect status at the end of the testing cycle

C Create multiple duplicate defect entries for the same issue to get faster attention

D Assign defects randomly without considering expertise

💡 Hint

Think about clear communication and avoiding confusion.

Updating defect status promptly and adding comments helps everyone stay informed and speeds up resolution. Creating duplicates causes confusion. Delayed updates reduce transparency. Random assignment wastes resources.

❓ Predict Output

expert

Output of defect report filtering code

What is the output of this Python code that filters defects by priority?

Testing Fundamentals

defects = [
    {'id': 1, 'priority': 'High'},
    {'id': 2, 'priority': 'Low'},
    {'id': 3, 'priority': 'Medium'},
    {'id': 4, 'priority': 'High'}
]

high_priority_ids = [d['id'] for d in defects if d['priority'] == 'High']
print(high_priority_ids)

A [2, 3]

B []

C [1, 2, 3, 4]

D [1, 4]

💡 Hint

Look for defects where priority equals 'High'.

The list comprehension selects defects with priority 'High', which are ids 1 and 4.

Practice

1. Which of the following is the most important information to include in a defect report?

easy

A. Number of team members working on the project

B. Steps to reproduce the defect

C. Tester's personal opinion about the software

D. The color scheme of the application

Solution

1. Step 1: Understand the purpose of a defect report

   A defect report should help developers find and fix the problem quickly by providing clear information.

2. Step 2: Identify key information needed

   Steps to reproduce the defect allow developers to see the problem themselves, which is essential.

3. Final Answer:

   Steps to reproduce the defect -> Option B

4. Quick Check:

   Include reproduction steps = C [OK]

Hint: Always include how to reproduce the defect [OK]

Common Mistakes:

• Including irrelevant personal opinions
• Omitting reproduction steps
• Ignoring environment details

2. Which format is best for writing the 'Expected Result' in a defect report?

easy

A. A clear, specific statement like 'The login button should redirect to the dashboard.'

B. A list of unrelated features.

C. A long paragraph about the software's history.

D. A vague description like 'It should work better.'

Solution

1. Step 1: Understand the role of 'Expected Result'

   The expected result tells what should happen if the software works correctly.

2. Step 2: Choose the clear and specific statement

   A clear, specific statement like 'The login button should redirect to the dashboard.' clearly states what the correct behavior is, helping developers understand the issue.

3. Final Answer:

   A clear, specific statement like 'The login button should redirect to the dashboard.' -> Option A

4. Quick Check:

   Expected result must be clear and specific = D [OK]

Hint: Write expected results clearly and specifically [OK]

Common Mistakes:

• Being vague or unclear
• Adding unrelated information
• Writing too much unnecessary detail

3. Given the following defect report snippet, what is missing?

Title: App crashes on clicking 'Save'
Steps:
1. Open app
2. Enter data
3. Click 'Save'
Actual Result: App crashes

medium

A. Environment details like OS and app version

B. Steps to reproduce the defect

C. Actual result description

D. Title of the defect

Solution

1. Step 1: Review the defect report snippet

   The snippet includes title, steps, and actual result but no environment details.

2. Step 2: Identify missing key information

   Environment details (like OS, app version) help reproduce the defect accurately.

3. Final Answer:

   Environment details like OS and app version -> Option A

4. Quick Check:

   Missing environment info = A [OK]

Hint: Always include environment details in defect reports [OK]

Common Mistakes:

• Forgetting environment info
• Assuming steps are enough
• Ignoring actual result clarity

4. A tester writes this defect report:

Title: Error message shown
Steps:
1. Click 'Submit'
2. See error
Expected Result: No error
Actual Result: Error message appears

What is the main problem with this report?

medium

A. The actual result is missing

B. The expected result is incorrect

C. The steps are too vague and not detailed enough

D. The title is too long

Solution

1. Step 1: Analyze the steps provided

   The steps only say 'Click Submit' and 'See error' without details like what page or data was entered.

2. Step 2: Understand why detailed steps matter

   Without clear steps, developers cannot reproduce the defect reliably.

3. Final Answer:

   The steps are too vague and not detailed enough -> Option C

4. Quick Check:

   Vague steps cause confusion = A [OK]

Hint: Write detailed, clear steps to reproduce defects [OK]

Common Mistakes:

• Writing vague reproduction steps
• Ignoring environment info
• Not specifying expected results clearly

5. You are reporting a defect that happens only on mobile devices running Android 12. Which combination of details is best to include in your defect report to help developers fix it quickly?

hard

A. Only the error message text and your phone brand

B. Expected result and a list of all tested devices

C. Steps to reproduce and a long history of previous defects

D. Steps to reproduce, expected vs actual results, device model, OS version, and a screenshot

Solution

1. Step 1: Identify key details for mobile-specific defects

   Device model and OS version are critical to reproduce issues on specific platforms.

2. Step 2: Combine with clear reproduction steps and evidence

   Including steps, expected vs actual results, and a screenshot gives full context for developers.

3. Final Answer:

   Steps to reproduce, expected vs actual results, device model, OS version, and a screenshot -> Option D

4. Quick Check:

   Complete details + environment + evidence = B [OK]

Hint: Include environment, steps, results, and screenshots for clarity [OK]

Common Mistakes:

• Omitting device or OS details
• Providing incomplete reproduction steps
• Not attaching helpful evidence like screenshots