Skip Navigation LinksHome Page > Forums > SpiraTest Forums > SpiraTest Best Practices > Test Cases which involve ...
We have what we believe o be a very common situation:
How would you do the above in SpiraTest? We're quite excited about the Test Configuration feature, where we could Test Case parameters like "Client1, Client2, Server" and create custom lists with all the currently supported app and server versions, but then we miss out on the traceability via Release and Build.
Alternatively, we could account for the fact that each of our 5 software projects above has their own releases and builds by creating 5 corresponding SpiraTest projects. However, how would we deal with Test Cases which involve multiple software projects (see above)? We could use the cross-project feature introduced in SpiraTest 5.1 by expressing our expectations for such multi-project scenarios as SpiraTest Requirements, copy the same Test Case into all SpiraTest Projects representing the involved software projects, and link all those Test Cases to the one Requirement. However, how would execute all those Test Cases? Using Automation, we're scheduling Test Sets and have RemoteLaunch execute them. How would that work if we're running a test which involves multiple software projects, represented by multiple Test Case clones across corresponding SpiraTest projects?
Any suggestions very welcome!
I think you have thought of the main options I would normally suggest:
You could just add the test case to the test set multiple times and set the parameter values for each instance. That might make the reporting back more clear (vs. test configurations).
In SpiraTeam 6.0 we will be linking test configurations to the Test Run so you can see which configuration entry was used.