Can anyone confirm if Zephyr Squad test cases (i.e., Jira test issue types) persist after ending a Zephyr Squad license?
For reasons outside my control, my company is not renewing our Zephyr Squad licenses. We have lots of regression tests we reuse. Each is a Zephyr test Jira issue type. I’m hoping those issue types are still available. Otherwise we would lose our entire history of test results.
Unfortunately, those issue types won’t be available.
I’d recommend to download all the data.
Just curious, what alternative will be used instead of Zephyr?
Oh really, @poliarush ? Do you have first hand knowledge of this?
Alternatives? I’m actually not a fan of test case management tools, so I’m not too worried. So far the ideas are to use a combination of Confluence and Jira issues. For in Sprint “deep story testing”, I’m thinking just add test plan in Jira Story comments, and log testing results as well as new tests in Jira Story comments. SBT using Rapid Reporter is encouraged and those artifacts can be linked to Story as well. Anything needed to be repeated should be added to automation suite if possible.
For non-automatable regression test, I think those need to persist in a Confluence table or Spreadsheet. Also toying with using a Kanban board for “release candidate testing activities” performed for each weekly release of the cross-team monolith. The cards on the board would be test activities like “Analyze the visual test results”, “Analyze the Selenium results”, “Run the Load Tests”, “Perform the interactive regression checks for Region A”.
Thoughts?
Thoughts?
It’s fine on small scale but don’t work if you have hundreds or thousands or test cases. It will be really hard to manage jira comments and confluence tables.
However, need to go iteratively, so I think it’s fine to go your way and then solve other problems once you have it