Bug Report Practice

Write a report another teammate could act on: steps, actual result, expected result, evidence, severity, and impact.

0 / 5 scenarios completed

Scenario 1

Login error message is missing

A user enters an invalid password on the login page.

Observed behavior

The login request fails, but no visible error message appears on the page.

Expected behavior

User should see a clear, safe error message such as Invalid email or password.

Evidence

Network response: 401 Unauthorized
Console: no frontend error
Browser: Chrome desktop
Environment: staging

Suggested report structure

Title:
[Area] Short problem statement

Steps:
1. Open...
2. Do...
3. Observe...

Actual result:
What happened.

Expected result:
What should happen.

Environment:
Browser, device, build, environment.

Evidence:
Screenshot, network response, logs, test data.

Impact:
Who is affected and how serious it is.

Bug report editor

Write your report

TitleSteps to reproduce

Actual resultExpected result

SeverityEnvironment

Evidence / notes

Check your report to see score, what is strong, top improvements, checklist details, and a strong example.