Skip to content
All notes
46Manual TestingBug ManagementBest Practices

What information should be included in a good bug report?

Essential Components of a Bug Report

1. Bug ID/Title:

  • Unique identifier
  • Clear, concise title describing the issue
  • Example: “Login button not responding on mobile Safari”

2. Summary/Description:

  • Brief overview of the bug
  • What is broken and where

3. Steps to Reproduce:

  • Detailed step-by-step instructions
  • Should be clear enough for anyone to reproduce

4. Expected Result:

  • What should happen (correct behavior)

5. Actual Result:

  • What actually happens (incorrect behavior)

6. Environment Details:

  • Operating System (Windows 11, macOS 14, etc.)
  • Browser/App version
  • Device (if mobile)
  • Screen resolution
  • Test environment (Dev, QA, Staging, Production)

7. Severity & Priority:

  • Severity: Critical, Major, Minor, Trivial
  • Priority: High, Medium, Low

8. Attachments:

  • Screenshots showing the issue
  • Screen recordings/videos
  • Log files
  • Network traces

9. Additional Information:

  • Frequency: Always, Sometimes, Rarely
  • Workaround (if any)
  • Related bugs
  • User impact

Example Bug Report

Bug ID: BUG-1234
Title: Login button unresponsive on iPhone Safari

Summary:
The login button does not respond to tap on iPhone Safari browser.

Steps to Reproduce:
1. Open Safari on iPhone 13
2. Navigate to https://example.com/login
3. Enter valid username: testuser@example.com
4. Enter valid password: Test@123
5. Tap the "Login" button

Expected Result:
User should be logged in and redirected to dashboard

Actual Result:
Nothing happens when tapping the login button. No error message displayed.

Environment:
- Device: iPhone 13
- OS: iOS 17.2
- Browser: Safari 17.2
- Environment: Production
- Screen Resolution: 390x844

Severity: Major
Priority: High

Attachments:
- screenshot_login_issue.png
- video_recording.mp4

Additional Info:
- Frequency: Always reproducible
- Works fine on Chrome iOS and desktop browsers
- Affects all iPhone users on Safari
- Workaround: Use Chrome browser on iPhone

Best Practices

  • Be specific and objective
  • Use clear, professional language
  • Include all relevant details
  • Verify bug is reproducible before reporting
  • Check for duplicates before creating new bug
  • Update bug status as needed