Are there plans to include the option to look at the Zephyr for JIRA gadgets based on test steps, as opposed to just tests?
We'd very much like to see a burndown chart that included all test steps in a cycle, for example.
Ok, I understand your reasoning. But I am curious yet on what you do with testcase results.
For example, if you have 15 testcases in a cycle and 200 steps, what does your chart show? Are there only 200 step values in the chart and no testcase results in the chart? Or do you also want the testcase results and someone have each step result included in a family of a single testcase's results?
Note, I think no matter which way we are going here, this is a feature request. But understanding your end goal can allow us to accuractly consider the feature request.
Thanks, Chris- I really appreciate the attention to detail. I suppose the absolute best case scenario would be to be view both - a chart that shows the 200 steps or a chart that shows the 15 tests, or possibly even a chart that shows a combination view (tests and test steps completed vs tests and test steps remaining).
The main goal, using your example, is to be able to take into account situations when you have 15 test issues, 10 of which have 5 test steps each (50 of 200) and 5 of which have 30 steps each (150 of 200). So when you look at test burndown with the current gadget, if the 10 tests with 5 test steps each are complete, you'd think you were 66.66% done with testing. But that is misleading. If you base it on test steps, then you are 25% done with testing - a very significant difference.
The reality so far in our usage of Zephyr for JIRA is that the number of test steps per test case varies quite a bit, so only looking at stats based on testcase completion doesn't tell the whole story.
Hope this makes sense, and again thanks for being so responsive and eager to improve the product for the users!
Thanks for the quick response! Essentially we just want a look at progress in terms of total test steps in a cycle instead of tests in a cycle. It would be great to be able to view the burndown chart based on test steps or an execution chart based on test steps. Basically just the option to be able to look at the entire testing effort in terms of all test steps in all tests in a cycle, instead of just all tests in a cycle.
The reason we want this is because looking at only tests can be a bit misleading as tests can vary widely in the number of test steps each one contains. So the ability to look at things at a test step level would give a better idea of how things are progressing.
I would also like to see burndown/report information using test steps (as well as test cases) for the same reason as above - a test case with 300 steps is counted in exactly the same way as a test case with 2 steps in a burndown chart. Using steps would reflect velocity more accuratly.
Thanks for all the input – is there any update or possible workaround for this…”Reporting by Test Steps”?
My request/requirement is similar if not the exactly same, we need the overall flexibility to report by Test Cycle the execution status by either “Test” (which we have currently) or “Test Steps” which doesn’t appear to be possible.
Any thoughts/suggestions would be appreciated.
Any progress on this request please?
I have similar needs. For example, we are doing end to end testing involving three check points to verify data flow in different systems. So, if my test case contain three steps for these three check points, it is important for us know any issues at a particular step level.
This report will help us see overall picture at different check points.
Hello Atlassian Community! Each month, we run a series of Spotlights to highlight Marketplace vendors and apps that our team thinks this Community would find valuable. In last month's Spotlig...
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!
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