Does SpiraTeam have a good approach for handling Test Case Versioning? Imagine: TC-xx created for Release 1.0 minor modifications to TC-xx required for Release 1.1 substantive modifications to TC-xx required for Release 2.0 patch Release 1.0.1 needs to execute same version of TC-xx originally created for Release 1.0 I'd like to figure out something that's efficient/manageable - preferably not "copying the Test Case, sticking a version/release# in the TC Name" and then having to keep manually track/organize artificially versioned TCs... Currently, we copy Test Sets from Release to Release (thus maintaining a history of tests/results from particular releases); however, that doesn't take into consideration the idea of TC versioning - which is becoming more an issue now that we've "gotten our feet wet" with SpiraTeam. Note: We're currently still on ST3.0. Hope to update to 3.1 by end-month. en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spirateam/issues-questions/143.aspxthreadId=143Julie Robertson (jrobertson@aperio.com) Does SpiraTeam have a good approach for handling Test Case Versioning? Imagine: TC-xx created for Release 1.0 minor modifications to TC-xx required for Release 1.1 substantive modifications to TC-xx required for Release 2.0 patch Release 1.0.1 needs to execute same version of TC-xx originally created for Release 1.0 I'd like to figure out something that's efficient/manageable - preferably not "copying the Test Case, sticking a version/release# in the TC Name" and then having to keep manually track/organize artificially versioned TCs... Currently, we copy Test Sets from Release to Release (thus maintaining a history of tests/results from particular releases); however, that doesn't take into consideration the idea of TC versioning - which is becoming more an issue now that we've "gotten our feet wet" with SpiraTeam. Note: We're currently still on ST3.0. Hope to update to 3.1 by end-month. Mon, 22 Aug 2011 18:31:17 -04002016-11-02T15:20:57-04:00/Support/Forum/spirateam/issues-questions/143.aspxmessageId=265David J (adam.sandman+support@inflectra.com)We added version control to v3.1 so that changes can be made to test cases and the changes can be rolled-back. However we've not yet added support for multiple branches, so currently you'd need to copy the test case if you want to be able to work off different versions for each release.Sat, 27 Aug 2011 03:00:57 -04002011-08-27T03:00:57-04:00/Support/Forum/spirateam/issues-questions/143.aspx#reply265messageId=277Julie Robertson (jrobertson@aperio.com) I see. Thanks for the response. Is this sort of functionality/enhancement currently only your internal product roadmap? (Unfortunately, I don't see it on the public high-level roadmap...) I'd love to hear how other ST users/admins are currently handling this within their environments. Surely it's a common problem? Tue, 30 Aug 2011 16:38:02 -04002011-08-30T16:38:02-04:00/Support/Forum/spirateam/issues-questions/143.aspx#reply277messageId=318Greg Ferreri (gferreri@glneurotech.com)I was looking forward to the versioning control provided in 3.1, but it kind of fell short of my expectations. In our environment, we work around the limitations by exporting all test cases for a particular release to a word document that is saved outside of ST. I'm hoping that eventually ST will provide the ability to tag specific versions of Test Cases that were run as part of a test set for a particular release. Mon, 03 Oct 2011 20:06:07 -04002011-10-03T20:06:07-04:00/Support/Forum/spirateam/issues-questions/143.aspx#reply318messageId=323David J (adam.sandman+support@inflectra.com)The ability to do full tagging and branching is planned, we just were not able to get it in the first release of the versioning.Tue, 04 Oct 2011 15:46:14 -04002011-10-04T15:46:14-04:00/Support/Forum/spirateam/issues-questions/143.aspx#reply323messageId=2796Oleg Tyulin (oleg.tyulin@searshc.com) What is status of versioning, branching and tagging now?Wed, 02 Nov 2016 15:20:56 -04002016-11-02T15:20:56-04:00/Support/Forum/spirateam/issues-questions/143.aspx#reply2796