TEST DOCS
Bug Report Generator
Structure a bug report so a developer can reproduce it in minutes instead of chasing you for details.
Title that reproduces
Good titles combine the failure with the key condition: "Login fails with valid credentials on mobile" beats "Login broken". Include the area, the action and the unexpected outcome.
Reproducible steps
Numeral steps with exact data. Mention the account, the browser, the environment and the build. If it only happens sometimes, say so and add the frequency.
Severity vs priority
Severity is how bad the impact is; priority is how soon it must be fixed. A cosmetic typo on the marketing homepage is high priority but low severity. Learn more in the Bug Reporting Guide.