When the Tester finds a bug/issue with the application/product he/she is testing, things to do:
Analysis:
- First and foremost thing is to try to reproduce the issue couple of times and make a note of steps that has been followed to reproduce OR Screen shot/Video Recording (If needed).
- Find the impact of the issue from a customer point of view.
- Now you may need to proceed as per process followed by your organization.
Communication:
- From communication point of view, the first thing needs to be done is to report the issue in the bug tracking tool(which will be generally available in all company) in detail (Steps to Reproduce, severity)
- If agile process is followed in your company then it’s easy to communicate to the concerned developer. If they sit near to you, you may prefer to go to their desk and talk to them about the Issue but it is always advisable not to disturb them. They may have high priority work to finish. You may first seek his permission to discuss on the issue via email/chat window. Your approach should be to the point and polite which will draw the developer attention. If the developer wanted to reproduce issue, you may help him to do it.
Tester role does not end till the bug/issue has been fixed or have a proper reason for deferred (if it is deferred). Tester should keep an eye on this.
Hi,
ReplyDeleteCan you point to two instances where we will have to follow a different approach than the one mentioned in this blog post?
Are you sure you would try to reproduce and then analyze the customer impact?
~Ajay Balamurugadas
Reply To Ajay:
ReplyDeleteHi Ajay,
Thanks for spending some time on my Blog and commenting on it. I appreciate your comment.
Are you sure you would try to reproduce and then analyze the customer impact?
In My View:
1.Yes, First the reproduce of Issue has to be done before analyzing the actual impact on
customer.
2. If the tester has seen the issue due to wrong Test Environment setup or due to bad network or due to network traffic or due to network port occupancy. There could be N no. of reason which is not foreseen to the tester.
3. In this Case Tester may log an Issue which is not the actual Issue.
4. First to ensure that Issue is exist by reproducing couple of times and ensuring correct environment.
5. Then Tester should analyze the Impact of issue on customer which will help him to set the priority to assign for fixing the issue.
6. There could be High Severity Issue but needs low priority to fix or Vice Versa.
Let me know your thoughts on this.