Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,552,588
Community Members
 
Community Events
184
Community Groups

How to efficiently manage test case lifecycle with a JIRA issue

Hello Everyone,

We use JIRA for our backlog management. As part of user stories, we are developing test cases where ever applicable. The test cases will be formalized by a person in the test team. The JIRA will be worked on by someone from the development team. Today, when a developer completes the JIRA development process, he creates a test JIRA as a subtask and closes it. The person from the testing team would formally test that JIRA story later. Our question is how to track this efficiently - the tester may take some time before the current JIRA gets picked up for testing. All this while, we do not want to have the JIRA open. So what are the best practices for managing the test cases lifecycle - authoring and execution in JIRA.

3 comments

Fabian Lim
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 06, 2021

Hi @pavan dittakavi

You would need a plugin such as xray or zephyr to track cycles and executions efficiently. Approved test cases can be added to cycles,/test plans.

For the test case lifecycles you need a workflow to identify when the test case is ready to be used for testing. You can use something like draft -> ready for review -> ready for testing. And also have a cancelled status to avoid old test cases.

Regards

Rogério Paiva - Xray Xporter
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Sep 07, 2021

Hi @pavan dittakavi 

If you wish to know more about the Xray capabilities please get in touch with Xray Support (http://xraysupport.getxray.app); we would gladly assist you.

Thank you.

Kind regards,
Rogério Paiva [Xray Support Team]

Noopur Varshney _AIO Tests_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Sep 08, 2021 • edited

Hi @pavan dittakavi 

 

You can try out AIO Tests. It keeps Development and Testing in Jira but at the same time doesn't bundle them up by using Jira for managing the testing process.

The developer can mark the story as "Ready for Testing" or something similar and then once testing team picks it up, they can mark it closed or "Testing Complete".

Another way is to mark the story as done, but link cases to the story and the AIO Tests Jira panel would show you the latest status of all cases associated with the story for easy decision making.

AIO Tests also exposes APIs to fetch the latest status of test cases of a story to automate the process.

If you would like to get a demo of AIO Tests, please reach out to us via our Support portal.
You can also schedule time with us at your own convenience from here.

Here is our documentation link.

Regards,
Noopur

Comment

Log in or Sign up to comment