Would it be possible to add an option to temporarily lock the ability to add test results a test run? We tend to set up multiple sets of testing in sequence and prepare test runs ahead of time, but we’ve had issues where a tester has run a test in a test run that isn’t ready to be executed yet (such as because the target environment for testing isn’t ready).
This differs from closing the test run, as it’s intended to be temporary and for the test run to be reopened at some indeterminate period, rather than permanently locking the run after being completed and archiving it. It also differs in that we would only want to prevent adding results; we would still need to be able to add or remove test cases while it’s in this locked state.
Hi and thank you for the suggestion!
Just to clarify: you would like to have some kind of “draft” mode, were the test run could be prepared, i.e. filled with test cases, but not be executed, yet.
Would you also require to limit the users that can edit the test run in this “draft” mode? So some kind of privilege?
Would a visual differentiation of the test run be enough or would you require a backend check that forbids changing results?
Thanks!
Best regards,
Alex
I added this “Test run Draft mode” to our feature wish list for test runs.
Please, if you read this and would also like to have this feature, upvote this topic and/or leave a comment. We do prioritize features which are highly requested from our community, so your vote counts 
Thank you!
Best regards,
Alex