Once you start executing a User Story, you will see the following screen: 

In the following example, the User Story is formulated as “Existing users can login”.

Depending on the result of your execution, you should choose one of the following options:

  • "Works" if you have tested the User Story thoroughly and it works as described. (here: an existing user can login).

  • "Fails" if the tested User Story does not work as expected. In this case, we recommend submitting a bug report following the general rules of bug reporting if in scope and not listed under "Known Bugs". (here: an existing user is not able to login).

  • "I'm blocked" if you can not test the given User Story. Please describe the reason for being blocked in the comment field. This is often the case due to technical reasons or missing instructions. For example, if there’re no login credentials available, you can’t test this User Story.


Please describe here what you did to test the User Story. There is no character limit, but please keep your feedback as short and precise as possible.

If you submit the User Story as ‘Works’, please provide a few details about what exactly you did to confirm that the given function works as expected – describe your steps and the result of your steps. Please refrain from copying-pasting the text of the User Story or leaving comments like ‘Passed’ or ‘It works’ – more details are required here otherwise your execution will be rejected.

Another important note is that your comment should be directly connected to the given User Story and could not be applicable to any other User Story in the test (e.g. saying ‘I followed the given instructions’ is insufficient).

Example: "I logged in to my account, added 2 items to the bag, selected ‘Master card’ as the payment method". You basically document the steps you performed to confirm the result. This will help us and the customer verify if your execution is correct and understand possible issues reported by other testers.

If you submit the User Story as ‘Fails’, please describe the bug that you’ve encountered according to the general rules on our platform. If the bug is in scope for the test and is not in the ‘Known Bugs’ list, please submit a bug report as well.

If you submit the User Story as ‘Blocked’, please provide a detailed description of why you are not able to execute the given User Story and how you’ve encountered this problem.

Please submit your User Story execution only when you've tested the User Story, otherwise your execution will be rejected.


For every User Story execution, it’s mandatory to attach a screenshot or a short screencast (no longer than 15 seconds) that shows the result of the execution. The attachment should contain the current date and the URL of the website or the app name. If you can not show this in one screenshot, you can upload several screenshots. Make sure that your attachment is under 25MB and have the JPG or PNG file format for screenshots and the MP4 format for screencasts. Every attachment should be created exclusively for each User Story execution and must not be used multiple times.


Please test User Stories with the device that is displayed as your requested device (the device you see when submitting a bug). Other devices are not relevant.


When you cannot confirm a User Story or you are blocked, because you cannot reach the right feature area, it is very likely you discovered a bug.

When there is already a submitted bug report in the test that fits, please use the dropdown to search for it and link it to the User Story. This will help the customer to understand the User Story execution and the bug better.

When there is no bug reported yet (and it's also not listed under "Known Bugs") we recommend you submit a new bug first and then finish the User Story execution.

Hint: The button "Submit bug" opens in a new tab, so you can create the bug report and then go back to your unsubmitted User Story.

You can only link bugs, when the User Story is not confirmed, and find features of the same test cycle, that belong to the same feature as the User Story.

Related articles:

Did this answer your question?