Bug Is Discovered: What Is Next?
by Nataliia Vasylyna | October 11, 2016 6:56 am
Software testing is a complex concept which involves many types of activities, the set of standard rules, and the roles distribution. Each professional tester, preparing to functional, security, mobile application [1]or user interface testing, should strictly and fully understand what actions should be executed after the bug is detected.
The loss of time is often too expensive under software development cycle. Thus, each employee should realize his direct responsibilities and make no delay.
Now it is time to define the step-by-step actions that should be performed by a software expert after the errors detection.
How Should a Tester Behave when the Bug Is Detected?
- Open the bug tracking system and start to fill the required fields accurately and clear in order for the developers to be able to easily understand the problem.
- Define bug priority[2] and severity, steps to reproduce, specify the actual and expected result.
- Choose the bug status and assign resolution (e.g. “Opened/Closed”, “In progress/Acknowledged”), write the defect[3] description.
- Do not forget to mention the OS version and browser name (especially, in the case of cross-browser testing[4]).
- Make screenshots or video of the detected mistake.
- Check whether the bug is reproducible.
- Be ready for the retest procedure and regression testing[5] if required.
- Always analyze the results of returned/fixed defects.
Reporting of bugs is an inherent and very important part of the test process and QA activity[6] as an entire. A tester should not neglect its obligatory performance and strictly follow all the listed stages.
Learn more from QATestLab
Related Posts:
- mobile application : http://mobile.qatestlab.com/
- bug priority: https://blog.qatestlab.com/2015/03/10/software-bugs-severity-levels/
- defect: https://blog.qatestlab.com/2011/10/11/main-types-of-defects-in-software-testing/
- cross-browser testing: https://qatestlab.com/services/let-s-compare/cross-browser-testing/
- regression testing: https://qatestlab.com/services/Step-by-Step/regression-testing/
- QA activity: https://blog.qatestlab.com/2011/12/28/planning-of-quality-assurance-activities/
Source URL: https://blog.qatestlab.com/2016/10/11/bug-is-discovered/