Skip to main content
User Story Review & Payout

In this article, you will learn how User Story executions are reviewed, the most common rejection reasons and how User Stories are paid.

Evgeniya Graich avatar
Written by Evgeniya Graich
Updated over a week ago

Your User Story executions will be reviewed by the Team Leader who can either approve or reject them. You will see the status of your reviewed User Stories on the test overview page.

Note that if a high percentage of your executions get rejected by Team Leaders, you can be excluded from testing User Stories on the Test IO platform.

User Story Rejection Reasons Explained

User Story Rejection Reason


Actions (clicks) not visualised / important step is not shown

This means that your clicks (Desktop recordings) or taps (Android) are not visible in the screencast, or you did not show the important step (such as: you did not show how you triggered the result). More rules for User Story attachment you can find here.

The attachment can't be opened in the 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 a .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 execution

If the tested User Story "works", but you have selected "No" (failed), or you have selected "Not possible to test" (Blocked), it will be considered as a wrong execution and will be rejected. Also, if you did not follow the User Story instructions precisely, it will be considered as wrong execution. Please always select the correct execution.

Screencast is too long

Your screencast is longer than 15 seconds. Please keep in mind that each User Story requires a short screencast, not longer than 15 seconds.

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 which will show the tested User Story and its execution. Keep in mind that for the User Story attachments, only short screencasts are allowed.

Low-quality comment

If the comment is poorly described it will be rejected. In your comment, you should always include a summary of what you did in 2-3 sentences and you should highlight the main steps (not all). For more examples of how the User Story comment should look, please visit our User Stories - More Good and Bad Examples article.

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.


Usually, you will get this rejection because you have used the wrong device or because of some other reason. Keep in mind that General attachment requirements, Date and Time specific rules, Screencast-specific rules, and Screencast-specific rules for Streaming devices from the Bug Report Attachments article also apply to the User Story Execution attachment rules.
Just in case, we advise you to read once again our Executing a User Story article.

The payout you receive for each executed User Story is displayed in the test details of each test.

Your User Story payout will be credited to your tester account once the test gets archived (up to 10 days after the test end).

Note: If your User Story execution doesn't get reviewed by TL, it is still going to be credited to your tester account after the test gets archived.

Note: Each User Story execution will be evaluated by our Compliance team. Irrelevant comments (not related to the selected User Story) in the How Did You Test field might lead to warnings or even a ban from our platform.

Did this answer your question?