Bug report writing in Testing Fundamentals - Build an Automation Script

Write a clear and complete bug report for a login failure

Preconditions (2)

Step 1: Open the login page

Step 2: Enter a valid username '[e-mail]' in the username field

Step 3: Enter an incorrect password 'wrongpass' in the password field

Step 4: Click the 'Login' button

Step 5: Observe the error message displayed

✅ Expected Result: An error message 'Invalid username or password' is displayed clearly below the login form

Automation Requirements - None (manual writing task)

Assertions Needed:

Bug report includes a clear title

Bug report describes steps to reproduce exactly

Bug report states expected and actual results

Bug report includes environment details

Bug report is concise and easy to understand

Best Practices:

Use simple language without jargon

Include exact steps to reproduce

Mention the version and environment

Describe the actual behavior and expected behavior

Attach screenshots or logs if possible

Automated Solution

Testing Fundamentals

Title: Login fails with incorrect password showing unclear error

Steps to reproduce:
1. Open the login page at https://example.com/login
2. Enter username '[e-mail]'
3. Enter password 'wrongpass'
4. Click the 'Login' button

Expected result:
User sees error message 'Invalid username or password' below the login form.

Actual result:
User sees a generic error message 'Login failed' without explanation.

Environment:
Browser: Chrome 114.0
OS: Windows 10
App version: 1.2.3

Notes:
The error message is unclear and does not help the user understand the problem.

Screenshot attached showing the error message.

This bug report is written clearly and simply. The title summarizes the problem. The steps to reproduce are exact and easy to follow. Expected and actual results are clearly stated so developers understand the difference. Environment details help reproduce the issue. The note explains why this is a problem. Including a screenshot helps visualize the issue.

This format helps developers quickly understand and fix the bug.

Common Mistakes - 5 Pitfalls

{'mistake': "Writing vague titles like 'Login problem'", 'why_bad': 'It does not help identify the issue quickly among many bugs.', 'correct_approach': "Use specific titles like 'Login fails with incorrect password showing unclear error'."}

Skipping steps to reproduce or writing them unclearly

Not stating expected vs actual results

Omitting environment details like browser or app version

Using technical jargon or complex language

Bonus Challenge

Now write three bug reports for different issues using the same clear format.

Show Hint

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