How do I export tests with test steps in Zephyr Jira for Cloud

[Liz Niada]

Hi, I need to export tests from Zephyr JIRA for Cloud. I can see how to do it for all tests, but excluding test steps, or how to do it for test cycles, showing execution details, where each individual test step goes into a separate row in excel. However, I just want to export all tests under a project (not execution details, just the tests including steps, so they can be reviewed).

I created a new issue query with all the tests in it, and tried to add the test steps column, so I could then export. However, when I go to add/edit columns, none of the Zephyr columns are displayed, which I guess is the root of the problem.Please help - I'm going round in circles!

Thanks.

[Gretchen]

I think the answer is that we have always (since I've been using bamboo, 3 years now) been able to deploy using the build side. The deployment side is new and has a lot of overlap with the build side because previously that was what we had. I suspect the goal was to allow you to migrate (copy/recreate etc.) the deployment tasks over to the deployment side and remove them from the build side.

This takes a bit of adjustment and acceptance to break away from the concept that the dev deployment is part of the CI build rather than a valid deployment in its own right. Even though it's "only dev" it's still a deployment to an environment and should configured that way if you want to represent it via the deployments component of bamboo. Now whether you can do that without configuring it as a true "release" (which I wouldn't expect every dev deployment to be considered a part of - though that is arguable) I don't know. That gets into the whole partial/full deployment discussion and I don't want to go there right now.

Now your second question regarding the integration with JIRA and how releases in JIRA are linked to deployments in Bamboo and how the controls on this should work is a bit trickier and an area I don't have much insight into. It seems that you wouldn't ever want anyone, except the annointed few, to trigger a deployment to production from JIRA (unless your CI/CD mindset is pure - and I suspect most aren't). CCB's and paperwork that typically accompany deployments to highly controlled environments would prevent that type of access in any company I've ever worked for. Perhaps QA leads would have rights to deploy to QA and maybe UAT type environments if full responsibility (aka ownership) of those environments belongs to them.

In general I wish there were more test cases like this available on any of the atlassian sites to provide visibility to complex deployment projects with exception cases to promote discussion of this type.

I'd like to hear more from users who are actively using the deployment functionality on how it's working for them. I have several projects that are moving in that direction (a couple set up but not being used at this time) and I'm looking forward to working with it. I don't however expect it to be without its challenges. No one can code for all the ways we crazy devops people think up to use an application.

Thank you for posting this question, it has given me some things to think about. I hope you were successful in your testing, I noticed this post was rather old and hadn't been responded to. I would be interested to hear what you decided and how you ended up implementing this in it's final version.