I want to execute these test cases in Zephyr Essentials but unable to do so, What can I do?

[Sonal_Kumbhare]

Hi, I created Release, User Stories and Test cases in JIRA. I want to execute these test cases in Zephyr Essentials but unable to do so, What can I do?

Previously after creating Release in JIRA , I used to associate User Stories to release and then Test cases were created in JIRA under those user stories.

Once this is done, Release used to reflect automatically under Released/Unreleased category as per status. Now that is not happening. If I create Release and Sprint manually, I cannot add test cases to the cycle since these created test cases are not appearing in search while adding test cases. I want to execute test cases but don't know how, help me.

[Germán Morales _ Hiera]

Hi @Sonal_Kumbhare, welcome to the community.
The key thing is that in the current Zephyr (Essentials is the new name for what used to be Zephyr Squad / Zephyr for Jira), a test case is its own Zephyr object, not a Jira issue. That's almost certainly why they don't show up when you add tests to a cycle: the "Add test cases" picker only lists Zephyr test cases, so anything you created as a Jira issue under your user stories (a story, task or sub task) won't appear there. The older approach of making test cases as Jira issues changed in this version.

The flow to get them executing:

• Create the test cases as Zephyr objects: open your Zephyr space and use + New Test Case, or from the Jira issue open the Zephyr panel and click Create New Test Case (the + icon), which auto links that issue on the test case's Traceability tab.
• In your cycle, click Add Test Cases. Your Zephyr test cases will now appear, so you can add, assign and run them.
• Execute from the cycle's Test Player, or run a single test straight from the linked issue's Traceability section.

Zephyr is a SmartBear app, so their docs are the authoritative source and their support is the place for any bug. Creating test cases is covered here: Creating a test case in Zephyr. The release reflecting under Released or Unreleased is separate Jira version behaviour, so if that part is still off it's worth its own question.