When you are executing a test case step and notice that you cannot perform the described action, it means your step execution fails and we ask you to describe what happens instead in more detail. There are three possible options here:
Submitting a new Test Case Bug
In case the bug you've encountered while executing a test case step has not been submitted by any other tester before, we ask you to submit a new bug report and describe your observed behavior in more detail. When you're creating a new test case bug, please make sure to follow our regular bug report requirements. As soon as you click Failed in your test case execution form, you will be offered to either submit a new bug report or to choose the bug submitted by another tester.
If you cannot find your bug in the list, please select Submit a new bug.
When the Create Bug Report section is shown to you, you will need to choose which bug are you reporting, whether is it a Functional, Content, or Visual bug. Make sure to select the appropriate bug type, and also for the Functional bugs you will need to choose between the severity of Low, High, or Critical. Afterward, you will need to fill in the bug details and submit the bug.
Just like in exploratory tests, your bug report will be reviewed by the Team Leader and the customer who can both send you information requests. If your bug report is not valid, it will be rejected.
Submitting a Test Case Bug Reproduction
If you encounter the same bug that has already been submitted by another tester, we ask you to submit a test case bug reproduction. In this case, you only need to select the appropriate bug report from the drop-down list and provide the necessary attachment.
Please note that your attachment should meet our standard bug reproduction requirements.
Note that you will not be able to edit the original bug report from another tester or update your reproduction once you submitted it.
In test case tests, you can find a list of all your submitted test case bug reproductions under My Issues > My Reproductions.
Once you start executing the Test Case Bug Reproduction you will reserve the seat for 30 minutes. If you don't submit a reproduction within 30 minutes, the seat will become available for other testers and you again. Starting the Bug Reproduction will activate the session which disallows you to start any other session like User Stories, Bug Fix Confirmation, Bug Report Confirmation, Test Session for other test cycles, or Bug Reproduction Execution for functional exploratory test.
When you open a particular test case bug reproduction from the list, you will be redirected to the initial bug report.
You can find the payout per test case bug reproduction on the test details page.
Linking a Known bug
If the Test Case test contains a Known Bugs list, and you experience the same bug as in the Known Bugs list in your Test Case execution, you will have the possibility to link that Known Bug. To link a Known bug, after you select in Step execution "Failed", you will need to open the menu and select the Known bug. You can identify the Known bug by its icon (badge) as you can see in the screenshot below.
After you select the Known bug, Bug Details will be shown to you, and at the end, you will see a "Link Known Bug" section where you will need to upload a screencast. When you upload it, you will need to press the "Link known bug" button in order to link it and proceed future.
