Skip Navigation LinksForums > SpiraTeam Forums > SpiraTeam Issues & Questi... > Test Case Versioning?

Test Case Versioning? RSS Feed

Monday, August 22, 2011
Does SpiraTeam have a good approach for handling Test Case Versioning?

  • 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.
5 Replies
Adam SAdam S
re: Julie Robertson on Monday, August 22, 2011
Friday, August 26, 2011
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.
Julie RobertsonJulie Robertson
re: Adam S on Friday, August 26, 2011
Tuesday, August 30, 2011
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?
Greg FerreriGreg Ferreri
re: Julie Robertson on Tuesday, August 30, 2011
Monday, October 3, 2011
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.
Adam SAdam S
re: Greg Ferreri on Monday, October 3, 2011
Tuesday, October 4, 2011
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.
Oleg TyulinOleg Tyulin
re: Adam S on Tuesday, October 4, 2011
Wednesday, November 2, 2016
What is status of versioning, branching and tagging now?
  • Started: 8/22/2011
  • Last Reply: 11/2/2016
  • Replies: 5
  • Views: 1001
Powered by KronoDesk v1.1.0.15 | © Copyright Inflectra Corporation 2011-2017 | Licensed to Inflectra Corporation.