Users want to be able to view the native "Description" field and a custom "Preconditions" field while executing the test. Is there a way to add these fields to the Test Execution screen?
Thanks in advance!
Currently there is not a way to add any custom fields to the Test Execution screen in Zephyr for JIRA. I am going to add this to our feature request list. What this means is that our product team will review the idea and decide whether or not to add it in a future release. Currently this is only the second or third time this has been requested so it is a new item to our feature request list. The resaon I am letting you know this is becuase if our product team does decide to add it to Zephyr for JIRA it would not be a short term change.
Custom fields would be nice, but at a minmum it would be nice to see the test case name. (I just asked a separate question on this) Our list of unexecuted tests shows identical rows execpt for key. This makes it impossible to find the right one to execute.
This is a first priority request for us. Thanks.
I would like the capabliity to add a "Build Id" field to the Test Execution page. Generally, a test cycle encompasses 1 or more builds - it is useful to track the specific build a test failed on - and have the capability to run reports against that later. Please consider this enhancement.
Here are two current approaches to partically resolve this today:
1. Add any field to a Zephyr Testcase as a JIRA custom field. You can call them preconditions, postconditions... Have your JIRA admin make it and assign it to the Issue Type Testcase. It can be made on the create screen and view issue screen per JIRA administration.
2. I acknowledge this doesn't put these specific fields on the Zephyr for JIRA execution screen. We did recently move the description field to the execution screen. So you have a few places to work if you want to get this information on the execution screen today. These include a teststep you could clearly identify as a "precondition" instead of an actual test step. Here you would just read it and not execute it. Or you could put information in the testcase description field and label it accordingly.
As Emily said before, our developement team is considering adding the ability to put custom fields on the execution screen in a future build. However today - this is what I can offer as potential solutions.
Our team works with pre-conditions by adding it as a section to the description field, along with several other sections, and distinguishing each section by using markup (or markdown) editing (a feature that has to be 'enabled' in the description field). The description is always included in the execution view so the reference is available at the top of the actual test execution screen.
A little more detail... our 'Test' case/issue description field contains the user story, acceptance criteria, prerequisite condition/s, and could easily contain a 'post-condition' @Julien as/if needed. In markup it's formatted like this... with some basic examples:
The ' * ' above are part of the markup edits where *xxxx* causes a bold font appearance and '*, **, ***' add bulleted indentation. The <JIRA-####> represents the issue key containing the project abbreviation and issue reference # assigned by JIRA. JIRA 'really conveniently' auto-links anything with that format (at least in the description and comment sections).
While I love the JIRA customization we use and are developing... I have observed less OoB customization leads to:
So... again, we are customizing with success... but YMMV.
Meanwhile... our solution mentioned above is effective, incredibly useful, and rapidly implementable NOW.
- Gray -
I would like to add "Executed Build(s)" to the Test Execution screen, as said before, cycles can sometimes include a number of builds. This could be worked around by having the cycle name include the build, but this would mean many cycles being defined and would change the nature of a cycle away from a period of time or a group of tests.
So generally the ability to add custom fields to test executions would be excellent.
Specifically, an "Executed Build(s)" field would be useful.
We're currently evaluating Zephyr plug-in to be used by a team of 7 QA engineers to manage thousands of test cases. It's crucial to know how many and what test cases were executed per a build. Unfortunately, after googling around I still don't know how to solve this challenge. Zephyr is lacking "Executed Build(s)" field on Execute Test dialog, the attribute important in test case execution.
My hope was that I can use Comment field (either common Comment field or step Comment field in Execution) for that by simply entering free form text build number. BUT the problem is there is no way to search by Execution Comment field
Another execution field or just test field would be valuable - Time Spent on running a test case. This measurement is important in estimating time for various test cycles.
If the community had same challenges and found workarounds, your insight would be appreciated.
This looks like a couple years old, is there a response from the product team?
Will this be implemented? If so when?
Has it maybe already been implemented in some newer release?
Having ability to add custom and visible fields is important, we may want to store such differentiating factors as environment as well as capabilities used for the test, localization indicator, etc etc
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot