When are you expected to reproduce issues?

In most test cycles, the issue must be reproduced at least once by a different tester before it gets approved. That helps us to confirm that the steps are correct and the issue is not an edge case or a one-time fluke.

There are usually 3 situations where reproducing is expected:

1. The specific issue gets assigned to you after the cycle ends. 

In that case, you can't choose which issues you reproduce. Proceed with reproducing and add the result as a comment for those issues.

You can also let the Test Lead know if you want to or for some reason can't reproduce issues after the cycle. 

2. Reproducing is the final task list step. 

In some projects there are task lists require you to pick and reproduce a number of other tester's bugs. In this case, you have to choose the appropriate reports that don't have comments yet, reproduce them, and add the issue numbers as comments to the task list step.

If you are one of the first people who has finished testing in the test cycle, you might not be able to find enough issues to reproduce (there are no other issues except yours, or other issues have comments on them already). In these cases, it would be great if you could check back in 2-3 hours and see if there are enough issues then. Otherwise, you should write that there were no issues.

3. You stumble upon the same bug while testing
If you're testing and during your duplicate search you find an issue that was already reported, provide the reproducing information in the comments.

Comment only issues that are open and not reproduced yet. Do not reproduce or comment issues that were closed as "works as designed" or "low priority".

What are the steps of reproducing?

First, if there is already a comment that an issue is (not) reproducible, skip that issue and move on to the next one. 


  • Read the steps in the report and try to reproduce the issue
  • If possible, try reproducing with a different account than the original issue submitter
  • If possible, first try reproducing on a different type of device (issue was reported on the phone -> try to reproduce it on a tablet for example)
  • If the issue does not reproduce with a different device, then try on a same/similar device to see if it is a device-specific issue or just a fluke. If issue reproduces with a different device, no need to reproduce further with a similar one.
  • Add reproduce comments and attachments.

From Reproduce tab of bug comment:

  • If you are able to reproduce > select ‘Is reproducible’ radio button, fill in the template, attach screen recording, or screenshot, if it is a user interface issue. No need to attach logs.
  • If you are not able to reproduce > select ‘Is not reproducible’ radio button, fill in the template, attach screen recording,  and device log for proof. 

In case: 

  • You cannot understand steps or there isn't enough information to reproduce > reach out to Test lead via project chat to clarify. 
  • You find a duplicate issue > comment it with the duplicate issue link.
  • You can't test some issues assigned to you > send the links to Test Lead and explain the problem.

    Think you've got the hang of it? Continue by reading about (fixed) issue verification and old issue verification.
Did this answer your question?