Optimizing Test Case Management Workflow for Build Versions

Wednesday, August 16, 2023
Avatar

We have implemented a workflow utilizing SpiraTeam as follows:

We maintain a substantial repository of test cases, numbering in the hundreds. Each time we receive a new build version, we have historically duplicated the entire test case folder and appended new test cases to this duplicated folder.

This approach allows us to conduct a comparative analysis of changes by contrasting the contents, while also enabling us to perform test case executions on both the previous server build by referencing the original folder and on the new server build using the updated test case folder.

Are there alternative methods to streamline this process, allowing us to differentiate between test cases associated with version 1 and version 2, without the necessity of duplicating test cases into new folders?

 

 

Thank you!

3 Replies
Friday, August 18, 2023
Avatar
re: szdravkovic Wednesday, August 16, 2023

You can simply map the same test cases to the new release.

Then (and only when) test cases need to change, you can clone them to keep the originals and the new versions.

That is another option.

Wednesday, August 23, 2023
Avatar
re: inflectra.david Thursday, August 17, 2023

Thank you!

Monday, January 1, 2024
Avatar
re: szdravkovic Wednesday, August 23, 2023

And when Spira adds the ability to map builds to requirements, incidents (not only if you have git integration) you may have much more power: you will be able to select build during testrun execution and you will know (and track) precise build that you are testing and easily see what features were included there.

Spira Helps You Deliver Quality Software, Faster and With Lower Risk

And if you have any questions, please email or call us at +1 (202) 558-6885

 

Statistics
  • Started: Wednesday, August 16, 2023
  • Last Reply: Tuesday, January 2, 2024
  • Replies: 3
  • Views: 315