Hi David,
For info, SmartBear have a Zephyr Scale Community and you might find it easier to find help and learn from that source (I'm one of the community leaders).
To answer your question, I think it's a good approach to have a central store of test cases that is shared among projects. I haven't had an opportunity to use this method in my project stack yet, but if the opportunity does arise I can't think of reason not to do it this way. You can still report on test progress per project - the test cases may reside in another project library but your report will be by test cycle (which contains said shared test cases). I'm presuming it's also possible to report on the entire test execution history of shared test cases from the source project library which you wouldn't be able to do easily if the shared test cases were spread across multiple projects.
The only downsides I can think of:
- No surprises here, but you won't be able to tweak shared test cases for any minor changes per project
- If you do update a shared test case it will not auto-update across all projects - you will have to go into each project and manually update (there is currently a request to bring an 'update all' function into the roadmap for development). On the flipside, having the test case shared centrally, it will be easy to find all test executions that need updating!
Some useful links for you:
SmartBear support team portal
Zephyr Scale Roadmap portal
Zephyr Scale Community
Cheers, Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.