Eight Steps To Writing Bug Reports

Why We Need Bug Reports

1. There is documentation on the existence of a bug.

2. Bug reports help the developer.

3. It becomes possible to prioritize fixes.

4. It becomes possible to analyze errors.

5. The tester contributes to fixing the bug.

6. It becomes possible to control at which stage you fix the bug.

7. It becomes possible to assess the current quality of the product.

Steps to Writing a Bug Report

1. A more detailed description of the problem than in the title.

2. Description of the initial state of the system and other data about the environment:

  • The browser and its version
  • Test environment: dev, stage, prod
  • The device on which the test took place: mobile phone, tablet, desktop with their operating system

3. Steps to reproduce the error.

4. Describe the actual result.

5. Describe the expected result.

6. Set priority and severity.

  • P1 High (urgent)
  • P2 Medium (can wait)
  • P3 Low (not urgent)
  • Blocker (disrupts performance)
  • Critical (affects significantly)
  • Major (distorts the displayed information but does not bring noticeable changes)
  • Minor (does not affect the operation of the program)

7. Assign to the developer or PM.

8. Click “done.” :)

The Life Cycle of a Bug Report

  • Open (Open) — you created a bug report and handed it over to the developer/PM (so that PM can issue it to a developer). The bug may go to the backlog, a special place where bugs wait to be selected and sent to development. It is like players on the bench waiting for their chance to play.
  • In Work (In Progress) — the bug is transferred to the developer to fix it.
  • Fixed (Ready for Design/QA) — the developer fixed the bug and submitted to the designer (if one is on the team) or tester for re-checking. If the bug turns out to be unfixed, it is returned to the developer (it is advisable to attach a photo/video report that the bug is still displayed).
  • Closed — the bug has been verified and is no longer reproduced. When closing a bug, the tester writes in the comments on which environment it was tested and attaches a screenshot or video that the bug is really fixed. This last action confirms that the bug was fixed if it appears again later and questions arise.

Main Mistakes When Writing Bug Reports

1. Title that is incomprehensible or too long.

2. Not enough data in the description or missing screenshots.

3. Bug reports are repeated.

4. One problem, one report.

5. The expected result links the requirements without specifying the exact section.

In Conclusion



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store


Сareer accelerator that is going to help individuals get high-paying jobs, regardless of their financial capabilities and professional experience. careerist.com