Fixed Issue Verification

What to do when you are invited to complete a fixed issue verification task

Doris Sooläte avatar
Written by Doris Sooläte
Updated over a week ago

When you reproduce issues during or at the end of a run, the aim is to verify that the reported issues are indeed occurring and reproducible. Fixed issue verification tasks are created to see if the fixes to the previously reported issues are working or not. 

Issue Verification Steps:

Start out by reading the steps in the issue report and try to reproduce them accordingly.

  • If possible, then at first try it on a different type of device (issue was reported on phone -> try to reproduce it on tablet)

  • If the issue is reproducible, no need to reproduce on the same type of device

  • If the issue is not reproducible, try on the same type of device

When you are done, add a comment to the issue report as follows:

  • Comment Can not reproduce the issue (aka the issue is fixed).

  • Comment Can reproduce the issue (aka the fix is not complete).

  • Can Reproduce/ Can not Reproduce: 

  • Device and OS: <Device name>, <Operating system and version>

  • Testable App version: <App version>
    (Please add the full app version and not just the release number)

  • Network: <Network type, e.g WiFi, 4G>

And don't forget to attach necessary files! 

  • Screen recording, screenshot, and a device log

  • If it is a User Interface issue, only a screenshot is needed

Close as Fix confirmed if the issue is fixed and you cannot reproduce.
Leave as is if you can reproduce and the fix is not complete (do not remove Fixed label).

For Network freelancers: Send the Test lead (Coordinator) a list of issues which you cannot test and explain why.

Think you've got the hang of it? Continue by reading about old issue verification or go over when and how to reproduce issues


Did this answer your question?