QA template

A bug report template developers can reproduce

A good bug report reduces back-and-forth. It gives the person investigating enough context to reproduce the issue, understand its impact and compare the actual result with the intended behavior.

Copy-and-paste bug report template

Title: [What is broken, where, and under what condition]

Environment
- App/version: [version or build]
- Device and browser: [details]
- Account or role: [if relevant]

Preconditions
- [State required before reproducing]

Steps to reproduce
1. [First action]
2. [Second action]
3. [Final action]

Expected result
- [What should happen]

Actual result
- [What happened instead]

Evidence
- [Screenshot, recording, log, request ID or error message]

Impact and frequency
- [Who is affected and how often it occurs]

Example: duplicate checkout charge

Title: Checkout submits the payment twice after a slow network response

Environment
- Web app build 2.14.0, Chrome 125, test account

Preconditions
- The basket contains one in-stock item and a valid saved card

Steps to reproduce
1. Open checkout and select the saved card.
2. Simulate a slow network response.
3. Select Pay once.

Expected result
- One order and one payment authorisation are created.

Actual result
- Two payment authorisations appear for the same basket.

Impact and frequency
- Financial impact; observed twice in five attempts.

Before you submit

• Use a factual title, not a diagnosis such as “API is broken.”
• Write steps someone else can follow from a clean state.
• Separate the expected result from what actually happened.
• Remove personal or production data from screenshots and logs.
• State impact and frequency so the team can triage responsibly.