Is there an ability to link to shared test cases/steps, for example:
If we have a test case for the JIRA product called "Create an Issue" and the first steps of that test case is to login, for which we have a test case already created with the login steps called "JIRA login", can you reference that shared login test case in other test cases so that when the login steps change, they are only needed to be changed in one place?
If this feature is not available, can it be added as a new feature request?
This isn't currenlty supported in Zephyr for JIRA. I will add it to the feature request list, but however I want to caution you that this will be lower on the feature request list than others due to the complexity of the implimentation.
The only way we have been able to work around this is by cloning the test cases. This is not ideal because it causes you to know that the test cases will become out of date. They could create a Shared Step section to hold the shared steps (like Microsoft Test Manager), or they could link steps to other test cases because you will have to run those basic steps at some point in regression. Either way would give nice functionality.
Those are the lines i was thinking along thanks Jason. Writing small test cases and cloning/using those. and again the MTM shared step functionality would be a definite fix. It appears Zephyr handles test steps only within test cases and not as seperate items like MTM does. Thanks for your response Jason.
Thanks for your interest in Zephyr.
Can you share with us the use case or how important is this feature for you so that we can forward it to our product management team?
Also let us know your official email id as we need it while raising a feature request
So my use case is the following:, have a taste test which is the same action but for several tests as such as uploading the files to your server and there are several results which I expect from that action but they are different features so I don't want them to be in different steps in the same test case because if one test if fails theoretically you need to stop the test they are different features which implemented in the way that they do not rely on each other such as a long message or a file created by that uploaded file so each of them is a different test for different future but the first action is the same the first step and if I change that first step the first feature and I want them all to change accordingly. I would like to be able to use one test step more as sort of a template which I can point to and they will be used when the test is executed. This feature existed in qc alm and seemed to be very efficient and also correct from the testing methodology point of view.
This is an enormous product gap. Copy test steps is only 10% of the battle. If I have 100 tests and I need to change the way someone logs in to a website, for example, then i have to go to 100 tests and update them manually. Sorry that's a show stopper for out team.
ALM had some similar functionality (the old Quality Centre) - while writing a test you could go and select a pre-existing step from another test case and add it into the actual test case - this way we would not have to write duplicated steps hundreds of times (e.g. Login)
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events