Bug report
Also called: Defect report, Ticket
A clear written description of a bug so developers can reproduce and fix it.
Definition
A bug report documents a defect with a short title, environment and build, steps to reproduce, expected result, actual result, severity, priority and evidence such as screenshots or videos. A good report lets a developer reproduce the bug without asking any questions.
In practice
Title: "Checkout: app crashes when tapping Pay with an expired card (Android 14, build 4.2.1)", followed by numbered steps, expected and actual results and a screen recording.
Learn it in context
Lessons that use this term.
- How QA Hiring WorksCareer
- How to Write Test CasesTutorials
- What Is Software Testing?Fundamentals
- How to Write a Bug ReportTutorials
- SDLC and STLCFundamentals
- A QA CV and Portfolio Without ExperienceCareer
- GesturesMobile
- Writing a Test PlanTutorials
- Estimating Testing EffortTutorials
- Security Basics for TestersWeb
Related terms
- SeverityHow much damage a bug does to the product or the user.
- PriorityHow soon a bug should be fixed, based on business needs.
- ReproducibleA bug that happens again every time you follow the same steps.
- Expected resultWhat should happen when you perform a test step, according to the requirements.
- Actual resultWhat really happened when you performed the test.