Completed

Users are unable to perform local runs for locked test cases that do not belong to them.

Users are reporting not being unable to perform local runs for locked test cases that do not belong to them, the Dataset Selection pop-up window's Ok button is disabled. Only by the test case's owner or a Admin user unlocking the affected test case would the Ok button be enabled (please see screenshot below).

We recently just upgraded to 9.3.2.1676, so prior to this version we have never encounter this behavior.

Ideally users should be able to run other users' test cases if they are part of the same team and share the same data sets; even if the test case is locked. what if the locked test case's owner is unavailable and there is no Admin user as well, what is the user trying to run the test case to so; make a copy? that to me does not make sense.

Thanks.

0
2 comments
Avatar
Joseph Hamdan

Hi Stephen,

Apologies for the inconvenience. This issue was already identified and fixed in the latest 9.3.2.1693 release version already in production server. 

Your instance will have to be upgraded and the issue will no longer occur.

Regards,
Subject7 Team

0
Comment actions Permalink
Avatar
Stephen Akinpelumia

Thanks Joseph.

0
Comment actions Permalink

Please sign in to leave a comment.