Bug tracking process issues that need attention
Many friends have asked me why I like so much of bug reports, bug report fact that individuals have been above all, it is the ultimate expression of the value of the tester. Perhaps the nature of the work, I often colleagues in Hong Kong and Shenzhen colleagues compared and found them an advantage in particular worth learning: doing things that are generally not to measure the ultimate benefit, is more a decision to consider how to better to make things better.
Down to earth, I hope that I can push hard.
??minimize the steps to reproduce with a minimum of steps to reproduce the problem; this is helpful to programmers find the roots of problems.
??best verified by the newspaper bug who can close the bug. Anyone can fix bug, but only that people can find bug bug really believe that has to be repaired.
??resolved in the bug to make it clear solution to this. General bug system allows you to such “fixed (fixed)”, “won''t fix (not going to fix)”, “postponed (beyond repair)”, “not repro (not reproduce)”, “duplicate ( repeat) “or” by design (design is) “to resolve bug. At the same time the best way to write the solution to solve the problem or normal (such as the above types) reasons.
??When your bug report “not repro (not reproduce),” hit back to you, first check whether there is missing a step or clear, then go to the programmer. Programmers usually can not report on the steps to reproduce the bug bug when select this option.
??carefully track the version information. You to test officers every build should have a build ID number, so just started testing personnel will not re-test are they not repair that version.
??If you are a programmer, and is caught using the bug to test the management of the troubled bank, you just do not have other means to accept the bug report. If your bug report will be used to test the form by mail sent to you, you just reply with a brief message to them: “Please enter them in the bug database, because I can not track the message.”
??If you are a tester, and are caught using the bug to test the management of distress in the library, and they said you just do not do any bug - the bug entered into the database, the database will automatically send the email to them.
??Do not add too many new fields. Some people like to add some new fields to track the information he needed. Imagine, testers take much time to fill out a form dozens of fields, but how many people still willing to fill out a bug under it.
??If you know the bug appears or a responsible officer of the module will address the bug the developers, please clear that in the title, such as you find the bug is related to additional personnel, then it may be noted in the heading “additional personnel when xx error” .
??If the English newspaper bug, the best use of present tense or past tense, for example, “appears” instead of “will appear”.
??Do not use full capital form, that would make people feel like a complaint. Do not use an exclamation point or other performance of individual emotional words or symbols.
??Do not use ambiguous terms (for example, as it seems) to describe the phenomenon found.
??Please consider the following questions:
1. The same software similar functions have the same problem?
2. Other browsers have the same problem?
3. Other hardware and software configurations have the same problem?
4. Other areas (locales) have the same problem?
5. Different arrangements are set have the same problem?
6. The previous version not have the same problem?
??no written bug report is formulated, there is no absolute model, the basic goal is to allow customers or changes, visit the bug report personnel understand, and in a short time without having to think again. Other times to consider a number of target audiences like. For example, some similar bug in the end is combined or presented separately, bug steps to establish (in the end is every step as one point or some points could be combined). At this point I think the “flexible and adapt” is very critical.
??found a Bug, and after filling out the bug report, at review time, require special attention to the point: This bug report will not let other people have a Lenovo or play space. A good bug report can not be broken down, in other words, this bug will not let others think you need to test some places, there may be other issues. For example, a test found in the input 16 of this number (allowable range) and submitted to the system will return an error: can not enter the 48 following figures. This is indeed an error, but If it is only on the steps now to submit, another might be such a thought: is not imported 48 of these the figure available will have this problem then? So that he may ask you to test other data. This extends the life of this bug, but a waste of our time.
Picked Inventory And Barcoding
samsung F480 mobile phone secret codes