In the given article, we won’t “waffle” about the importance of bug detection and elimination in the software products, because in the previous articles we have discussed this issue for hundreds of times. So let’s start with the main subject.
Definition
What is a bug? Testers from independent software testing companies know that answering this question is and easy, and complicated at the same time. First of all, under the bug we understand an error or defect in the program. Also, under the bug, we may understand some undocumented or undesirable “side” reactions of the program on some user actions, as well as on using it with other software at the same time or some other hardware configuration.
It’s also essential not to mix up bugs (errors, defects, etc.) with so called features. We tend to unite under this concept the peculiar features and properties of the program, which it doesn’t possess. As a rule, in a well-organized and – planned project they shouldn’t appear because all the functionality has been already discussed by SQA consultants before development stage. It is especially true for those projects, which are made by a specific customer. The customer determines the number of features/properties/functions to be present in the program.
As a rule, the majority of bug tracking systems have the possibility to compile not only bug reports but also make a Feature Request. It allows dedicated testers make their offers for improvement of the program under test.
Classification
There are many bug classifications. First, in my opinion, it is due to the fact that these classifications lie various criteria. One part of classification possesses a theoretical character; another part would be useful for practical point of view. Regretfully, to cover all the possible classifications – is a complicated task. So let me stop on the most important ones.
“Minor” Bug Classification
- Bugs in user interface.
- Bugs in functionality.
- Programming logic bugs.
- Installation bugs.
- Bugs in memory usage, system resources, etc.
The given classification possesses a purely practical nature.
Bug Description
To describe the bug, testers use various utilities, because bug description in text editors may be very time-consuming and boring activity. We offer to consider the following:
- Registration information (description, identification number, priority, membership classification, build, the name of the tester and date).
- Report – is a more detailed information about bug content.
- Steps to recreate – detailed step-by-step actions of Tester.
- Workaround – description of workarounds, if any errors.
- Configuration – the description of the hardware and software configuration, as well as configuration installations in tested software itself.
Add Comment