Tester’s work is to find software bugs during mobile application testing, desktop testing or web site testing and document them correctly. Bug-tracking instruments are almost always used for recording and managing errors in software products and coordinating efforts of the testers and the developers.
When a defect is discovered in a software product a tester must record it in the bug-tracker. But first he must make sure that it is really a defect. If tests pass it is necessary to be sure that there are really no errors there. Such validation is especially needed in case of automated testing. It is wise to equip test instruments with diagnostic capabilities that help to monitor truth of the tests results.
Before Adding an Error into a Bug-Tracker or Reporting That no Software Bugs Were Found During Tests Execution One Should Verify:
- that it is not a false positive;
- it is not a false negative;
- this error has not yet been added to the bug-tracker.
When it is determined that the found error is really an error it is added to a bug-tracker. Nowadays there are many various error-tracking instruments. But mostly definite information about the discovered software bug is required.
Usually it Necessary to Enter in a Bug-Tracker:
1. Version of the tested application.
2. Description of the test environment in which the tests were performed.
3. Project part in which the error was discovered, for instance, User Interface.
4. Class of the discovered defect, for instance, the found error may be not a defect but a change request or an enhancement request.
5. Repeatability of the found error. Some errors may happen irregularly, at the fifth attempt, for instance.
6. Clear and detailed steps to reproduce the defect.
7. Screenshot or video record of the reported software bug.
This is common information about discovered error that is to be entered in a bug-tracker. Often it is required to add something else, like the error severity and priority. Indicating of these criteria a software testing company helps the developers to determine which errors are to be corrected first, which are urgent and which may wait for some time.
Usually Software Defects Are Prioritized in the Following Way:
1. Showstopper – defects that make it impossible to go on testing process.
2. Urgent – defects that must be corrected immediately.
3. Defects of High Importance– defects that must be corrected as soon as possible.
4. Defects of Medium Importance– fixing of such defects may be postponed for some time.
5. Defects of Low Importance– defects that may be fixed when there is some time and resources.
6. Defects with no priority – defects that cannot be prioritized.
Development team must mark corrected software bugs as ready for regression testing and add short description what was done to correct the error and what areas of the system may be affected by the fixing.
This entry passed through the Full-Text RSS service — if this is your content and you're reading it on someone else's site, please read the FAQ at fivefilters.org/content-only/faq.php#publishers. Five Filters recommends:
- Massacres That Matter - Part 1 - 'Responsibility To Protect' In Egypt, Libya And Syria
- Massacres That Matter - Part 2 - The Media Response On Egypt, Libya And Syria
- National demonstration: No attack on Syria - Saturday 31 August, 12 noon, Temple Place, London, UK