How to split test cycle between multiple people in Zephyr for JIRA?

We have a team of testers who are about to executing tests defined in Zephyr. The problem is that some of the Test Cycles we've defined are large enough (have many Tests) that they could be split amongst multiple testers.

  1. How would you indicate who should execute which test?
  2. Since it doesn't seem like you can assign tests (https://answers.atlassian.com/questions/111415/how-do-you-assign-a-test-to-someone-in-zephyr-for-jira), is there a way to at least indicate if someone has started executing a particular Test?

5 answers

1 accepted

Hi Eldon,

Tests are not assigned to folks really. You can assign a Test issue just as you can assign an "Asignee" to any JIRA issue type. However, how Zephyr for JIRA works is you create tests and assign them to cycles. Once they are assigned to cycles, any tester that is assigned to the JIRA project can begin grabbing and executing tests.

The same goes for test cycles. There is not the ability to assign cycles to separate testers. The best way to "assign" a cycle to a tester or group of testers is too place their name/s in the cycle description. What this will do is display their names right on the cycle so they will know if it belongs to them or not by a quick glance.

In Zephyr for JIRA, one a test has been executed, it will display the testers name and the time they executed it. The best way to see if someone has executed a test is to use the Search Test Executions Navigator. What you can do here is enter in a ZQL too search for tests you want to know about. Once you search for them, it will display who executed it and when.

As a side note, we do have the ability to assign tests to different member's of the team in our Zephyr Enterprise Edition. Our Zephyr Enterprise Edition does tightly integrate with JIRA as well.

http://www.getzephyr.com/zephyr/zephyr_enterprise/overview.php

Kind Regards,

Emily

The concern we have is that two testers would grab the same test and start executing. WHILE they're executing, there's no way for them to indicate a test is in progress, right? Imagine a test that take 2 hours to test... Someone can start on it, be in the middle of testing, and another tester can start it as well. Unlike Tasks on the rest of our scrum boards where we can assign a name and mark it In Progress.

I think one way we may handle this is to create a Task issue in JIRA and specify a set of tests within a Test Cycle and assign it to testers. This way we can divide up the work.

Seems like this is a pretty big missing feature, especially for an Enterprise 500 user license like we are on...

I agree with Eldon. I think this would be a great feature to add. Seems like once a test is being executed by User A, if User B looks at the same test, he could see some indication that says "Currently being executed by User A". Or maybe he only sees this notice if he hits the Execute button on this test.

Tests need to be assignable in the test cycle! This is a must for our business when we do regression and smoke test cycles. Please hurry this fundamental functionality please.

Hi C K,

Thanks for posting! Currently Zephyr for JIRA does not have the ability to assign testers to cycles available with native functionality. Our Product Management team has been made aware of this feature request. They will review the same for consideration. We appreciate your valuable feedback in making Zephyr for JIRA better.
For further questions/assistance please feel free to open a service request by sending us an email.
Kind Regards,
Emily

Yes test case execution should be assignable.

Assigning tests in an execution cycle is of highest importance. We have a big testing team. For a lead it is important to track the status of testing by tester. For tester knowing how much work he has to complete in given time is important.

Now when everything is open for grabbing ... testers usually have a tendancy to grab the easiest tests first. And the attitude of "somebody else will do that hard to do 4 hour test".

Do consider implementing this feature ASAP.

EUREKA!!!

Here is how I solved this problem ...

Say you have 300 tests to be executed.

Steps:

  1. Create Filter_A to filter out 50 tests (not all 300) that are to be assigned to Tester_A.
  2. Add these 50 tests "via Filter_A" to the Test_Execution_Cycle
  3. Go to Tester_A desk.
  4. Search the Test_Execution_Cycle for all un-executed tests.
  5. Bulk Change the status of all 50 tests to "WIP".
  6. Now the tests have "ExecutedBy = Tester_A"

Repeat above steps for every tester. Ensuring that the 300 tests are covered in various filters.Note: By using Jira filters, you have labels, assignee, custom fields, and everything else to filter by.

At the end of above exercise, you have a test execution cycle, with all tests marked "WIP". Plus every test has the name of the assigned tester in "ExecutedBy"

Now testers just filter out their tests with:

cycleName = Test_Execution_Cycle AND executedBy = <Tester_A>

Tester's issue of seeing assigned tests is solved. And all under ONE execution cycle.

* This works if you have a small number of testers.

How well has this worked for you over time?

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,861 views 12 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot