Contributions
Re: Zephyr Scale: Same test cycles associated with multiple test plans
A Test Plan should be able to show the correct execution status of the associated test cycles. What I am seeing is that if multiple Test Plans point to the same Test Cycle then both test plans will indicate that the Test Cycle is "Done" even though it wasn't run for that Test Plan. I can easily clone a set of Test Cycles and have one set for Release 1 and one set for Release 1.1 and that will work, but it gets messy fast. Another unfortunate thing is that the Test Plan just indicates "Done", not that it Passed, Failed, or other.591Views0likes1CommentRe: Zephyr Scale: Same test cycles associated with multiple test plans
Thanks for the info. However, Test Plans don't appear to have any concept of "release version" so both Test Plans still show the same status versusTest Plan Release 1.0 showing status for Release 1.0 andTest Plan Release 1.1 showing status for Release 1.1. Is there a way to associate a Test Plan with a "release version"?602Views0likes0CommentsZephyr Scale: Same test cycles associated with multiple test plans
Zephyr Scale: Same test cycles associated with multiple test plans. For example, we have: Test Plan Release 1.0 Test Plan Release 1.1 Both test plans include the same test cycles. When we run the associated test cycles, the result is updated in BOTH test plans. What is the best way to set up Zephyr Scale? What we've done is clone the test cycles for each release, but this doesn't seem practical.623Views0likes5CommentsZephyr Scale: "Start a New Test Execution" is setting this supported by the API?
"Start a New Test Execution" is setting this supported by the API? For example, we want to run all of the same cycles again on a new release, is there a bulk way to set all of the cycles to Not Executed?397Views0likes1CommentRe: In TestRail you can easily re-run a Test Plan by click Rerun on the Test Plan, how to do this Scale?
Thank you for the response. Closing the project itself isn't really ideal either but we can look into that. What would be great would be the ability to Clone from the folder structure for Test Cycles and to maintain that when cloning. And also not adding (cloned) to the cloned Test Cycle names. What if we created a script to utilize the API and used that as a template for creating Test Cycles (and folder structure)? Would that be a possible way to essentially clone a set of Test Cyles?1.2KViews0likes0CommentsIn TestRail you can easily re-run a Test Plan by click Rerun on the Test Plan, how to do this Scale?
In TestRail you can easily re-run a Test Plan by click Rerun on the Test Plan, how to do this Scale? Basically, we could create a Test Plan template and maintain that and whenever we have a new release we'd Rerun that template Test Plan. Is this at all possible in Zephyr Scale? It seems like we can clone Test Cycles but that doesn't clone the folder structure and all of the cloned Test Cycles now have (clone) in the name. It's nearly a 1 button process in TestRail.1.2KViews0likes2CommentsZephyr Scale Configuring Environments: Can you copy/share between projects?
Zephyr Scale Configuring Environments: Can you copy/share between projects? For example, Project A and Project B cover the same different environments, do I need to manually enter them for both projects or can I copy/share them from one project to another?Solved584Views0likes1Comment