Quality is delighting customers
As a QA, why are you debugging the issue? Debugging is part of a developer's duties and he/she should be doing that assessment based on the results reported by QA. One thing you can do is to:
1. Capture the relevant screenshots, steps to reproduce and the timing of the issue.
2. Run that scenario a few times to see if that issue is consistently reproducible
3. If your testing scope involves testing the product on various OS combinations, then try executing the same test case in another OS and see if the results are consistent.
4. If there are logs that are accessible on the client machine, then capture those logs and append them to the defect
5. If this defect is causing your testing to halt as other downstream product functionalities are not accessible to test, then mention that clearly to the developer and mark the defect with the appropriate severity/priority.
Thanks for the info provided on the testing steps.
Posted this question in the forum as was curious to get some details on debugging the issue to a certain extent so that, it can be appended to the bug report.
I do this way,
Debugging is not the job of QA, however helping to debug and fix is job of QA.
1) Capture/gather all possibles proofs of the defect like, screenshots, logs, video
2) Try to reproduce the issue
3) Analyze the root cause of the issue
4) Gauge the impact of the issue
5) Escalate issue to product owner/stake holders (as application is at halt)
The point number 3 specified is what i was also trying to ask about.Can you please be more specific on that , as how it can proceeded further to get the root cause.