Either allow them to choose which one they want, or just resubmit with the latest one, and tell them to fix their suite that holds the older one. a. To have a latestVersionWins option we can pass to the suite-adding call b. If the latestVersionWins option is not used, the error message should name which test case had the version conflict. That'll give us the flexibility we need. I can first try without latestVersionWins, and if I get that error back I'll have the data I need to warn the user, and I can immediately re-submit with latestVersionWins. And if in future we decide to change the behavior, we don't need a platform change for it.
A Pivotal Tracker story has been created for this Bug: http://www.pivotaltracker.com/story/show/14718947
Carl Meyer added a comment in Pivotal Tracker: Cam: it's not clear to me from the description here what exactly it is you want to have happen when two conflicting versions of a case are added to a run. Maybe you can clarify that first, and then I can verify we have the platform support we need to make it happen, before we have eric wireframe something.
Carl Meyer added a comment in Pivotal Tracker: This story might be obsoleted by the fact that for now we're going to treat all test suites as if they always contain the latest version of every case, but I'm not sure - it depends on the details of how we implement that. I'll ask more questions on that story.
Cameron Dawson added a comment in Pivotal Tracker: carl: yeah. this is obsolete now. Deleting...
This is now invalid, because we don't care about test case versions in suites anymore. Only in test runs.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INVALID
Cameron Dawson deleted the linked story in Pivotal Tracker
Bumping to verified invalid, due to age of bug and comment 3
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.