Bug report writing in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start a bug report with a clear title.

Testing Fundamentals

bug_report = {"title": "[1]", "description": "App crashes on login."}

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

ABug

BCrash

CApp crash on login

DError

Attempts:

3 left

💡 Hint

Common Mistakes

Using vague titles like 'Bug' or 'Error' which don't explain the issue.

The title should be clear and descriptive. "App crash on login" tells exactly what the problem is.

2fill in blank

medium

Complete the code to add a severity level to the bug report.

Testing Fundamentals

bug_report = {"title": "App crash on login", "severity": "[1]"}

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

Alow

Bhigh

Cmedium

Dminor

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'low' or 'minor' which understate the problem's impact.

The severity 'high' indicates the bug is serious and needs urgent fixing.

3fill in blank

hard

Fix the error in the bug report by completing the steps to reproduce field correctly.

Testing Fundamentals

bug_report = {"title": "App crash on login", "steps_to_reproduce": [1]

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

A"Open app, enter username, click login"

B{Open app, Enter username, Click login}

COpen app, enter username, click login

D["Open app", "Enter username", "Click login"]

Attempts:

3 left

💡 Hint

Common Mistakes

Using a single string or wrong data structure for steps.

The steps to reproduce should be a list of clear, separate actions. Option D uses a list of strings, which is correct.

4fill in blank

hard

Fill both blanks to complete the bug report dictionary with expected and actual results.

Testing Fundamentals

bug_report = {"expected_result": "[1]", "actual_result": "[2]"}

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

AUser logs in successfully

BApp crashes with error message

CLogin page reloads

DBlank screen

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up expected and actual results.

The expected result is that the user logs in successfully (A). The actual result is the app crashes with an error message (B).

5fill in blank

hard

Fill all three blanks to complete the bug report with environment, status, and assigned_to fields.

Testing Fundamentals

bug_report = {"environment": "[1]", "status": "[2]", "assigned_to": "[3]"}

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

AWindows 11

BOpen

CQA Team

DLinux

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing environment with status or assigned_to.

The environment is 'Windows 11' (A), status is 'Open' (B), and the bug is assigned to the 'QA Team' (C).

Practice

1. What is the main purpose of writing a bug report in software testing?

easy

A. To clearly explain the problem and how to reproduce it

B. To praise the software for its features

C. To describe the software's design

D. To list all the software's functions

Solution

1. Step 1: Understand the role of a bug report

   A bug report is meant to communicate a problem clearly so developers can fix it.

2. Step 2: Identify the correct purpose

   Among the options, only explaining the problem and how to reproduce it matches the bug report's goal.

3. Final Answer:

   To clearly explain the problem and how to reproduce it -> Option A

4. Quick Check:

   Bug report purpose = clear problem explanation [OK]

Hint: Focus on clear problem explanation and reproduction steps [OK]

Common Mistakes:

• Confusing bug report with feature description
• Writing vague problem statements
• Ignoring reproduction steps

2. Which of the following is the correct way to write the 'Expected Result' in a bug report?

easy

A. The software crashes sometimes.

B. The software is slow.

C. I don't like how the software looks.

D. The software should save the file without errors.

Solution

1. Step 1: Understand what 'Expected Result' means

   It describes what should happen when the software works correctly.

2. Step 2: Choose the option that clearly states the correct expected behavior

   The software should save the file without errors. clearly states the expected behavior: saving the file without errors.

3. Final Answer:

   The software should save the file without errors. -> Option D

4. Quick Check:

   Expected result = correct software behavior [OK]

Hint: Expected result shows correct behavior, not opinions [OK]

Common Mistakes:

• Writing vague or subjective expected results
• Confusing actual and expected results
• Skipping expected result section

3. Consider this bug report snippet:

Steps to reproduce:
1. Open the app
2. Click 'Save'
3. Observe error message

Expected result:
File saves successfully

Actual result:
Error message 'Save failed'

What is the main problem this bug report helps identify?

medium

A. The save function shows an error instead of saving

B. The app crashes on startup

C. The error message text is correct

D. The app saves files too quickly

Solution

1. Step 1: Analyze the steps and results

   The steps show clicking 'Save' leads to an error message instead of saving.

2. Step 2: Match the problem with options

   The save function shows an error instead of saving correctly describes the issue: save function shows error instead of saving.

3. Final Answer:

   The save function shows an error instead of saving -> Option A

4. Quick Check:

   Bug report identifies save error issue [OK]

Hint: Match steps and results to find the problem [OK]

Common Mistakes:

• Ignoring actual vs expected results
• Misreading the steps
• Choosing unrelated options

4. A tester writes this bug report:

Steps:
1. Login
2. Click 'Profile'
3. See blank page

Expected: Profile page loads
Actual: Blank page

What is missing that would improve this bug report?

medium

A. The tester should add unrelated screenshots

B. The tester should remove the expected result

C. The tester should add environment details like browser and OS

D. The tester should write a longer story

Solution

1. Step 1: Review the bug report content

   The report has steps, expected and actual results but lacks environment details.

2. Step 2: Identify what improves bug reports

   Adding environment details helps developers reproduce and fix bugs accurately.

3. Final Answer:

   The tester should add environment details like browser and OS -> Option C

4. Quick Check:

   Environment details improve bug reports [OK]

Hint: Always include environment info for better bug reports [OK]

Common Mistakes:

• Skipping environment details
• Adding irrelevant information
• Ignoring clear reproduction steps

5. You find a bug that only happens when the user uploads a file larger than 5MB on a slow internet connection. What is the best way to write this bug report?

hard

A. Report the bug without any reproduction steps.

B. Report the bug with steps, expected vs actual results, and mention file size and network speed.

C. Report the bug but say it happens on all file sizes.

D. Report only that the upload fails without details.

Solution

1. Step 1: Identify key details for reproduction

   File size and network speed are important to reproduce this bug.

2. Step 2: Choose the option that includes clear steps and environment details

   Report the bug with steps, expected vs actual results, and mention file size and network speed. includes steps, expected vs actual results, and important conditions.

3. Final Answer:

   Report the bug with steps, expected vs actual results, and mention file size and network speed. -> Option B

4. Quick Check:

   Include all relevant details for complex bugs [OK]

Hint: Include all conditions that trigger the bug [OK]

Common Mistakes:

• Omitting important reproduction conditions
• Giving vague or incomplete steps
• Ignoring environment factors