Adding editing capabilities for custom fields in the test run and Run test case views

I would like to kindly request the addition of general and bulk editing capabilities for specific custom fields added to the test case template, in the test run and Run test case views, similar to the existing “ASSIGNED TO” and “RESULT” fields.

As our testing processes evolve, marking executed tests with additional information during a test run has become increasingly important.

I strongly believe this enhancement would not only streamline our workflow but also significantly improve the ability to capture relevant information during the test run more efficiently for other Testiny users.

3 Answers

3

Thank you for your feedback!

Just to clarify: I guess, what you want are fields that are only viewable and editable in the test runs view, i.e. that would only be edited on that very test case instance within the specific test run. E.g. to describe the current state of the test case only for that test run.

The currently supported custom fields are test case specific, i.e. they have a value that is intrinsic to the test case and the same for every test run. They describe the test case and not a state of the test case within a test run. You can also edit them from the test run by clicking the “Edit” button, but changing them changes the value for all instances of that test case in all test runs.

Best regards,
Alex

Hi Alex,

You’re absolutely correct. What I need is the ability to add existing custom fields to the test run scope, ensuring their state persists only for that specific test run and isn’t saved globally. As you pointed out, the current test case-specific custom fields do not meet this request; any adjustments made to them affect the global test case state.

Regards,
Taras

Thanks for the clarification!

Makes sense and our architecture is actually prepared for that: the custom result states are already such a custom field just for test runs :smiley:

We still need to see where this fits into our roadmap. Voting for this feature can up it in the list.

If somebody reads this request and also would like to have this feature, make sure to vote for this topic. We do consider the number of votes for feature requests in our roadmap and priority planning.

Best regards,
Alex