We discovered recently that concurrent editing of Test Plans/Runs could be dangerous, so I’m looking to see if there’s a workaround or a safeguard in place.
Basically, we have a big Test Plan that contain multiple Test Runs for several Test Suites.
It’s expected for different testers to be modifying the Test Runs within this Test Plan (adding/removing tests) at any time. Changes by the second tester always win and TestRail does not notify about mid-air collisions (similar to Bugzilla for example).
So if 2 testers are modifying the same Test Plan at the same time, the changes by whomever saves the Test Plan last will win and overwrite changes by the first, without notification.
Currently, we’re getting around this by communicating clearly who’s modifying which Test Plan, but I’d much rather have TestRail:
- simply lock it and prevent edits by someone else OR
- detect mid-air collisions and notify (i can elaborate more on the logic here) OR
- merge, if possible, the changes (for example, one can assume that testers won’t be modifying the same run within a test plan)
Keep in mind that the “big test plan contains multiple test runs” design is a requirement on our end. I do understand that if we removed the Test Plan from the picture, and just had test runs, this problem would be minimized.
Let me know your thoughts on this.