What should I include when submitting a Bug Report?

A clear and well-structured bug report helps teams reproduce issues faster and fix them more efficiently. Taking a few extra minutes to include all the right details can make a big difference.

Before submitting your report, make sure everything below is covered.

---

Your Bug Report should include

1. Title (Summary)
   A short, clear description of the issue.
   Example: “App crashes when tapping Login.”

2. Environment
   Include details such as:

• Device model

• OS version

• Browser or app version

3. Description
   Explain the issue clearly by covering:

• Actual Result: What happened during execution?

• Expected Result: What should have happened instead?

4. Steps to Reproduce
   List the exact steps you followed, in the correct order, so the issue can be reproduced reliably.

5. Evidence Attachments
   Add supporting materials such as:

• Screenshots

• Screen recordings or videos

• Crash logs or console logs

• Any other files that help verify the issue

6. Bug Frequency
   Indicate how often the issue occurs:

• Always

• Sometimes

• Rarely

7. Severity or Priority
   Specify the impact of the issue:

• Minor

• Major

• Critical

---

Often Required Fields

Depending on the assignment, you may also be asked to include additional information, such as:

• App or build version

• Network type (Wi-Fi, 4G/5G, VPN, etc.)

• Document used

• Section

• Device model

Always check the Tester Spec or bug reporting form to see which fields are mandatory.

---

Tip

Keep the Bug Reporting Guidelines close while testing. They work as a quick checklist and help you structure your reports correctly every time.