Forum Discussion
2 Replies
- josh42Community Hero
Hi alyssa-grantham ,
ZS interprets any status that is not "Not Executed" or "In Progress" as completed. For the "Blocked" status the argument could be made, that the test execution is completed if it is blocked, because it can not be continued at this point. Only after the "blockage" is dealt with can a new execution be run. But I can also see your point for it to be considered as not completed. 😉
For custom statuses the option should definitely exist (it does not atm), to define them as not completed.
A quick search yielded two ideas in the ZS Server Ideas Portal. Give them a vote.
https://zephyr-scale-server-dc.ideas.aha.io/ideas/TM4JS-I-434
https://zephyr-scale-server-dc.ideas.aha.io/ideas/TM4JS-I-483
If they don't match your needs or you feel, they are not clear enough, you can add a new idea.
https://zephyr-scale-server-dc.ideas.aha.io/ideas
If you're on cloud, use the corresponding Ideas Portal.
https://zephyr-scale-cloud.ideas.aha.io/ideas
Cheers
Josh
- alyssa-granthamNew Contributor
Thanks for the links - have voted for those suggestions. Hopefully the custom status option will be possible one day soon, and the ability to choose whether a core status counts as completed or not, because it sounds like there is not uniform agreement on the usage of Blocked.
Cheers.
Related Content
- 8 years ago
Recent Discussions
- 3 days ago
- 5 days ago