37 / 71 · 11 Manual Testing Fundamentals · Effective Bug Reports← prev⊞ allnext →☰ Read as one page
5.3Bad vs Good Bug Reports
| Aspect | Bad | Good |
|---|---|---|
| Title | "Login broken" | "Login returns 500 when email contains '+' character" |
| Steps | "Try to log in" | "1. Go to /login 2. Enter user+tag@test.com 3. Enter valid password 4. Click Submit" |
| Expected | "Should work" | "User is authenticated and redirected to /dashboard" |
| Actual | "Doesn't work" | "Server returns HTTP 500. Response body: {error: 'invalid_parameter'}. Console: no client-side errors." |
| Environment | (missing) | "Chrome 122, macOS 14.3, staging env, build #4521" |
The bad report requires a conversation before anyone can start investigating. The good report lets the developer reproduce and start debugging immediately.