No doubts, a good bug report is a high quality document. Writing a bug report is an important task, because that’s the main point of communication between a tester, the developer and the project management. A well-written bug report will not only create a good relationship/relations between you and the developers, but will also save company resources to work with it.
Moreover, a good bug report must consist of a correctly written Summary. As a rule, the Summary consists of 150 characters or less. It is important to ensure that the Summary fully answers the following questions: What is the problem? Where and when is the problem reproduced?
It is also essential to understand that while writing the Summary you need to clearly indicate the nature of the problem - in other words, to specify what exactly does not work. That is why it is not necessary to use words that describe the problem abstractly, without concretization, for example, nothing happens, incorrectly/correctly displayed, works wrong/right etc.
Here are some of the examples of the incorrect Summary:
- Nothing happens after going to the page.
- The «About company» section is displayed incorrectly.