Anatomy of a good bug report
A good defect report lets the reader reproduce the problem without asking you anything. The difference between a bug that gets fixed quickly and one that gets ignored is often in the quality of the report.
- Clear, specific title (what fails and where).
- Steps to reproduce, numbered.
- Expected result vs actual result.
- Evidence: screenshots, video, logs.
- Environment: browser, OS, version, data used.
- Proposed severity and priority.
text
Título: El total del carrito no se actualiza al eliminar un producto
Pasos:
1. Añadir 2 productos al carrito
2. Eliminar 1 producto
Esperado: el total se recalcula
Real: el total sigue mostrando el importe de los 2 productos
Entorno: Chrome 124 / Windows 11 / v2.3.0Defect report example
Report facts, not opinions, and be respectful: the goal is to improve the product, not to point fingers.
QuestionToca para voltear
Which two results must never be missing in a bug report?
What is the main purpose of the 'steps to reproduce'?