Bug reproductions are tasks that testers can perform to earn additional income on the Test IO platform. Each bug reproduction is reviewed by a Team Leader and can be either accepted or rejected, with one of the reasons listed in the table below:
Reason | Explanation |
Screencast is too long | Your screencast is longer than 15 seconds. Please keep in mind that each bug reproduction requires a short screencast, not longer than 15 seconds. |
Action triggering the bug is not shown | The screencast does not prove what step was performed to lead to the bug, but e.g. only the final result. |
No URL bar or (identifiable) date | The URL bar of the browser or the current date is not visible in the screencast. Make sure always to show those in your screencast. |
Wrong reproduction type | You have submitted the reproduction as reproducible, although the screencast shows the opposite, and vice versa, or you found a different bug and selected that you cannot reproduce the given bug. Always ensure to select the proper reproduction type. |
Attachment can’t be opened in browser | If your attachment cannot be opened in the browser / if it is broken, it will be rejected. So make sure always that you record screencast in an .mp4 format, and that it is playable in the browser. For screen recording tools and how to create a screencast, we recommend you to check our Screencast article. |
Wrong or missing screencast | You have uploaded the wrong screencast, or you have uploaded a screenshot. Make sure that you always upload a correct screencast that clearly shows the bug reproduction. Keep in mind that for the Bug Reproduction attachments, only screencasts are allowed. |
Wrong device/browser | The attached screencast shows a different device or browser than the one stated for the reproduction, for example: you have selected "Android" browser, while you are actually using "Chrome" browser. |
Crash log is missing | The bug is a crash bug, and the required crash log, in addition to the screencast, was not attached. |
Instructions not followed | Each test cycle comes with specific instructions. Failure to follow these instructions will lead to rejection. For more details, please refer to our Test Scope article. |
Did not follow the bug steps properly | You have missed a bug reproduction step, or a few of them, while performing the reproduction. This often leads to the wrong outcomes. |
Rejected | None of the above rejection reasons matches the situation, e.g. the you have used Google Translate to translate the website contents, you have increased the playback speed of your screencast, etc. |