How to make BUG-reports correctly?

4059

22

2018-08-13 20:54

Show all posts
Hello everyone, in this lesson I would like to tell you how to correctly compose BUG-reports on the Flyme forum!

Let's start with what we learn - what are bugs and why they need to be reported to developers!



Russian Verison
-------------------------------------------------------------------------------------------------------------------------------------------


A bit of history  


On September 9, 1947, scientists at Harvard University who tested the Mark 2 computer found a stuck moth between the contacts of an electromechanical relay that caused the machine to stop. Bug in English is a moth, a beetle, an insect. Since then, any malfunctions in computer technology are called: BUG


The bug can be called:


- non-compliance with requirements or specifications
- failure of the program, leading to its completion
- program hang (no response)
- issuing any errors (software or system)

- minor inaccuracies, etc.


-------------------------------------------------------------------------------------------------------------------------------------------


From the above information it can be understood that "BUGS" exist everywhere, and in the development of any software to make a mistake more than possible, and this is normal! After all, the software is written by a person, and people are prone to make mistakes.
To do this, there are testers (we are with you), which help developers bring software to the mind and correct mistakes.

We will need to describe the problem as accurately as possible when composing the BUG-report!


For this we need:

- The report should be ONLY IN ENGLISH LANGUAGE !!!! NO MORE !!!!
- An accurate descr iption of the problem
- Step-by-step descr iption of the call of a particular problem.
- Screenshots (if this is a visual problem), where you can see the problem visually.
- LOG file, which contains all the detailed information about this problem

And this is the minimum set for a good report!


Below I will give some examples with a descr iption.

-------------------------------------------------------------------------------------------------------------------------------------------

HOW TO DO NOT!

Безымянный.png

This screenshot shows that the report does not contain any information, no firmware version, no step-by-step instructions, no screenshots, logs and anything else. A simple descr iption without details ... Such a report developers will not even consider, because nothing is clear.

-------------------------------------------------------------------------------------------------------------------------------------------



AND HOW TO MAKE A NORMAL REPORT!


Безымянный2.png


  Here we see that the firmware version in the descr iption is also indicated, and the exact name of the error, descr iption, step-by-step instruction, screenshots, log file and contact information for communication with the tester.
Such a report will fall into the hands of developers, because. everything is more than clear and experts will be able to understand the problem.

-------------------------------------------------------------------------------------------------------------------------------------------






Also VERY IMPORTANT!

At the bottom there is a button "i have the same" - it must be pressed if you notice the same problem! This will help to weed out more important problems in the list of reports, because if the error has only come out of you, and no one else has, then that means that the problem is not serious, and when you press on "I have the same" it highlights the report "from the crowd."

-------------------------------------------------------------------------------------------------------------------------------------------






Thank you very much for your attention, Yours faithfully Alex Deor!