> For the complete documentation index, see [llms.txt](https://ultimatewebsolutions.gitbook.io/qa-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ultimatewebsolutions.gitbook.io/qa-knowledge-base/what-should-a-bug-report-contain.md).

# What should a bug report contain?

A good bug report should be clear, concise, and reproducible. It should contain a descriptive title, environment and build information, preconditions, steps to reproduce, expected and actual results, severity and priority, and supporting evidence such as screenshots, videos, or logs. The goal is to give the developer enough information to reproduce and fix the defect without having to ask the tester for additional details.