Custom field changes in one Test Run are syncing in other active Test Runs

Support
, ,
1

Hi everyone,

I am running into an issue with how custom fields behave across multiple open test runs, and I’m hoping someone can guide me on how to decouple them.

The Issue: I have created a custom field for my test cases. Currently, I have two separate Test Runs open. If I modify the value of this custom field for a specific test case inside Test Run A, the change automatically reflects and overwrites the value for that same test case in Test Run B.

What I want to achieve: I need the custom field values to be independent per Test Run. Changing a field in one run should not affect any other active runs.

I couldn’t find anything in the documents. Any help or workarounds would be greatly appreciated!

Thanks in advance,

Atharv

2

Hi and welcome to the Testiny forum!

Whenever you change a field (custom or builtin) on a test case in the Test Cases section, that change will immediately reflect on that test case in every (open) test run - only closed test runs will not be effected.

This is because the fields you changed are actually on the test case itself, not on the instance of the test case in the test run - you changed it in the Test Cases section, not in the Test Runs section.

Unfortunately, there are currently no custom fields for test cases within test runs. If that is something you need, please describe your use case and I will turn this post into a feature request. Thank you!

Best regards,
Alex