This article presents a requirement for our freelancers. Failure to follow the process might represent a breach of the Freelancer Services Agreement.
When are you expected to reproduce issues?
In most test runs, the reported issues must be reproduced at least once by a different tester before they can be approved. This process helps us to confirm that the steps are correct and the issue is not a corner case or a one-time occurrence.
Usually, there are 3 situations where testers are expected to reproduce issues.
1. When you find a duplicate issue during run execution
You need to reproduce the issue if you find out during the duplicate issue search that the same issue has been reported previously.
2. You are allocated a specific issue to reproduce after the run ends
In this case, you cannot choose which issues you can reproduce. Proceed with reproducing the allocated issue and add the result as a comment under those issues. Please let the Test Lead know if for some reason you can not reproduce issues after the run.
3. Reproducing is the final task list step
In some workspaces, there are tests that require you to pick and reproduce issues reported by other testers. In this case, you have to choose the appropriate issues that do not have comments yet, reproduce them, and add the issue numbers as comments to the test step.
If you are one of the first testers to finish testing in the run, you might not be able to find enough issues to reproduce as there might be no other issues except yours, or the existing issues might already have reproduction comments. In such cases, you could check back in a couple of hours (2-3) to see if there are enough issues to reproduce, otherwise, you can write that there were no issues.
How to reproduce issues?
Once you have found a duplicate issue using these guidelines, the first step is to check its status. If the found duplicate issue is closed, check the reason and take actions according to the table below:
Reason for closing the issue | Action |
Fixed or cannot reproduce | Report a new issue |
Duplicate or Merged | Check the original issue and continue based on its status. |
Spec change, Working As Designed (WAD), out of scope, low priority, invalid | The test case most likely needs to be updated, make sure to leave feedback in such cases. |
If the status of the found duplicate issue is Open, follow the issue reproduction guidelines below:
Follow the steps in the steps to reproduce section in the issue report and try to reproduce it.
If possible, try reproducing on a different type of device at first. For example, if the issue was originally reported on a phone, try to reproduce it on a tablet.
If you are unable to reproduce the issue on a different type of device, try to reproduce it on the same/similar device as in the issue report.
If possible, try reproducing with a different account (if applicable) than the original issue submitter.
Once you have followed the reproduction steps, click on the Reproduced or Not Reproduced button accordingly.
Provide your environment details by completing the template. If you need to Reproduce the same issue for other steps in the same run, you can simply click I have provided my environment information - this way you can skip filling the template again and adding another reproduction comment under the issue.
For Reproduced issues, attach a screen recording and a screenshot.
For Not reproduced issues, attach a screen recording, screenshot, and a device log for proof.
Good to know:
If the reproduction steps are not easily understandable or if there is incomplete information to reproduce, reach out to the Testing Manager or the Test Lead via workspace chat to clarify.
If you find a duplicate issue, comment it with the duplicate issue link.
In case you are unable to test an issue allocated to you, send the issue link to the Testing Manager or the Test Lead and explain the problem.
#TestlioBot