Defect reporting best practices in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add a clear and concise defect title.

Testing Fundamentals

defect = {
    'title': '[1]',
    'description': 'App crashes on login',
    'severity': 'High'
}

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

AApp crashes on login

BBug found

CCrash

DLogin issue

Attempts:

3 left

💡 Hint

Common Mistakes

Using vague or too short titles that don't explain the issue.

Leaving the title empty or generic.

The defect title should be clear and concise, describing the issue precisely. 'App crashes on login' clearly states the problem.

2fill in blank

medium

Complete the code to include the correct severity level for a critical defect.

Testing Fundamentals

defect['severity'] = '[1]'

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

ALow

BMinor

CCritical

DTrivial

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing 'Critical' with 'Low' or 'Minor' severity.

Not assigning severity at all.

Critical severity indicates a defect that causes major failure or data loss and needs immediate attention.

3fill in blank

hard

Fix the error in the defect report by completing the code with the correct status value.

Testing Fundamentals

defect['status'] = '[1]'

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

ACloseded

BOpen

CIn Progress

DResolved

Attempts:

3 left

💡 Hint

Common Mistakes

Typos in status values causing confusion.

Using invalid or unsupported status terms.

The status 'Open' is correct for a newly reported defect. 'Closeded' is a typo and invalid.

4fill in blank

hard

Fill both blanks to create a defect report dictionary with a proper priority and reproducibility.

Testing Fundamentals

defect_report = {
    'priority': '[1]',
    'reproducible': '[2]'
}

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

AHigh

BNo

CYes

DLow

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing priority levels or using invalid values.

Incorrectly marking reproducibility.

Priority 'High' means the defect should be fixed soon. 'Reproducible' set to 'Yes' means the defect happens every time under the same conditions.

5fill in blank

hard

Fill all three blanks to complete the defect report with correct reporter, environment, and steps format.

Testing Fundamentals

defect = {
    'reporter': '[1]',
    'environment': '[2]',
    'steps_to_reproduce': '[3]'
}

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

Atester01

BWindows 11

C1. Open app\n2. Click login\n3. Observe crash

Dadmin

Attempts:

3 left

💡 Hint

Common Mistakes

Using generic or unclear reporter names.

Not specifying environment details.

Writing vague or incomplete reproduction steps.

The reporter is 'tester01', environment is 'Windows 11', and steps to reproduce are clearly listed to help developers understand the issue.

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