Feb 21
Add a "Skip Step" Option During Test Case Execution for Setup/Technical Blockers
The Problem:
Currently, if a tester is blocked on a specific test case step due to a setup issue, technical limitation, or incorrect credentials, there is no way to bypass it. To exit or stop the test case, the platform forces the tester to submit a bug. Because the issue is test setup-related and not an actual defect, the bug inevitably gets rejected. This negatively impacts the tester's approval rate.
The Solution:
It would be useful to add the "Skip" option in the test case steps. The testers could use it if they can't execute a step due to technical issues or an incorrect test setup.
Why it helps:
If a tester encounters a setup issue, they can use this button to skip the step and leave a comment explaining the technical issue. This will prevent testers from being compelled to submit invalid bugs just to close the execution.
Reviewing
Hi Basit! Thank you very much for bringing this to our attention. It does seem that there is an opportunity to improve the tester experience when executing test cases. We truly appreciate you highlighting this, as it helps us better understand where improvements may be needed. We have started looking into this situation with the goal of making the tester interface as clear, simple, and user-friendly as possible. We’ll be sure to keep you updated as we learn more. Thank you again for your valuable feedback!