We have a test project, that consists of automated and manual tests.
Automated tests are executed in different environment and mostly they are stable. After automated tests have been executed we need to mark these tests as PASS/executed in Zephyr.
We have about 1000 automated tests, so is it possible to set them as PASS by one click, because it's wasting of time to click on each of them and change their execution status?
In search test execution provide the zql and use the bulk execute option and change the status
Also you can use ATOM feature which manage all your automation testcases, plan in cycle summary, assign and execute the automation tests
You can enable this feature by navigating to project setting and enable
@Nataliya_M ATOM is available for zpehyr for jira server/Data Center. By default ATOM option is enabled for all users. If one cannot see the ATOM option jira administrator has to provide the "Zephyr Browse ATOM" permission.
Updating all automated executions to PASS is can be done through ZQL in search test executions page and bulk status update to PASS.
Hi @Manmeet Chadha
Zephyr identifies whether TestCase is created by A.T.O.M or not by below jql
jql: project="xyz" and Issuetypeid="1234" and summary ~" abc" and labels="ZFJ_Automation"
note: here 1234 is test issue type id
if test case matches the above query then it will not create duplicate TestCase, if doesn't matches then it will create new test case and it will create the execution
I suggest below things to do to avoid duplicate test cases
1. Change your manual tase to automation test case by updating the label for existing test cases : ZFJ_Automation (Case sensitive)
2. Make sure your test case summary matches same as your ATOM results file
3. Now execute the atom task and check it won't create duplicate test cases
To avoid duplicate execution and update existing execution
1. Use the existing cycle or folder while creating the automation task, this will update the results in same cycle/folder for every run and you can see the difference in execution history
For example I'm attaching sample Junit file which consists of 3 test cases
1. name="should default path to an empty string"
2. name="should default consolidate to true"
3. name="should default useDotNotation to true"
Imagine you have already testcases present with the above names in your jira now you have updated the 1st 2 test cases with label ="ZFJ_Automation" and if you will execute then A.T.O.M will create only 3rd test case as duplicate since it doesn't have label ZFJ_Automation
Sample Junit result file: Junit.xml
<?xml version="1.0" encoding="UTF-8"?>
<testsuite name="JUnitXmlReporter" errors="0" tests="0" failures="0" time="0" timestamp="2013-05-24T10:23:58" />
<testsuite name="JUnitXmlReporter.constructor" errors="0" skipped="1" tests="3" failures="1" time="0.006" timestamp="2013-05-24T10:23:58">
<property name="java.vendor" value="Sun Microsystems Inc." />
<property name="compiler.debug" value="on" />
<property name="project.jdk.classpath" value="jdk.classpath.1.6" />
<testcase classname="JUnitXmlReporter.constructor" name="should default path to an empty string" time="0.006">
<failure message="test failure">Assertion failed</failure>
<testcase classname="JUnitXmlReporter.constructor" name="should default consolidate to true" time="0">
<testcase classname="JUnitXmlReporter.constructor" name="should default useDotNotation to true" time="0" />
If you are still facing the issue please raise support ticket :
Atlassian's marketplace partners have had a very productive start to 2021! Since our last roundup, our developer community has added over 160 new cloud apps to the Atlassian Marketplace to help you...
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