What Causes the “Invalid” Bugs?

by Nataliia Vasylyna | August 17, 2015 8:04 am

Before reporting any incident to the bug tracker, a tester must ensure that it is not his fault during the test and that he has not missed any important detail during installation or configuration.

During functional testing, cross-browser testing, localization testing[1], and others a tester can detect a lot of bugs, but it is mandatory that each of them should be reported to the developers, who will view the ticket and approve or reject a bug report.

The Most Common Precipitating Factors of “Invalid” Bugs:

1. Configuration files for the test: a tester must ensure that the files are relevant and consistent with the requirements: one of the most common reasons for determining an incident as an error that it is really not such, may be a situation when there is a failure to maintain the file in accordance with the requirements of the software or the customer. To avoid such cases, experts recommend additionally apply configuration testing.[2]
2. Before proceeding directly to the desktop testing or mobile testing, there is a need to check the provided database on the validity and on the subject of whether all the necessary data are present.
3. If a tester performs automated testing[3], then, before reporting the incident to the bug tracker, the test should be run twice.
4. The correctness and relevance of the authentication credentials.
5. Compatibility of the software versions.
6. The correct installation of all software components and registry entries.
7. Before starting the check, a tester must ensure that all the latest file versions are uploaded to the test environment.

Related Posts:

• How to Solve Accessibility Problems?[4]

Source URL: https://blog.qatestlab.com/2015/08/17/causes-invalid-bugs/

---