Skip Navigation LinksHome Page > Forums > SpiraTeam Forums > SpiraTeam Issues & Qu... > Test Case Versioning?

Test Case Versioning?

Monday, August 22, 2011

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.

5 Replies

Saturday, August 27, 2011

inflectra.david

re: julierob Monday, August 22, 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.

Tuesday, August 30, 2011

julierob

re: inflectra.david Friday, August 26, 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?

Monday, October 3, 2011

gferreri

re: julierob Tuesday, August 30, 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.

Tuesday, October 4, 2011

inflectra.david

re: gferreri Monday, October 3, 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.

Wednesday, November 2, 2016