palmerbw
Occasional Contributor
Joined 5 years ago
User Profile
User Widgets
Contributions
Re: Multiple testcases with Zephyr results from Jenkins
What is it showing is that every single run create a new automation phase under the same cycle. Since this is automation I will have thousands of phases pretty quickly. The othe images show each testcase under those phases and shows that each one is identical except for the testcase ID and it show s that they is only one execution on each. It means that as the Jenkins job run for each code check in by I develop I will get a new test case with only one execution and a new phase also. If I look at metric I will look like I have hundreds of testcases when I really only have one testcase with hundreds of executions. Where does zeeReporter look for testcases to match up with? In ZBot you can define this in the folder watcher.Re: Multiple testcases with Zephyr results from Jenkins
This is not the behavior that I am seeing. I get a new phase for each execution (Annoying). In each phase i have new new testcase that is identical to the other testcase with the exception of the ID. I currently have 10 testcases produced by the pipeline and each one has one execution. I should have one testcase with 10 executions.Multiple testcases with Zephyr results from Jenkins
Each time I run a Jenkins pipeline I get a new testcase in Zephyr. I want it to add execution to the existing testcase. This happens when I predefine a testcase and when I allow Zeereporter to create the first test case. Occasionally it will add results to one testcase for a little while and then make a new testcase. How do I fix this?Jenkins Zephyr plugin and Test Cycles
I am using the Zephyr plugin for Jenkins to report results. I cannot find any documentation on how it handles test cycles. Ideally I would like the results from a Jenkins pipeline reported in one cycle for a two week sprint and then have it automatically create a second cycle when the next sprint starts. When I select new cycle I get a new cycle on every execution even through my cycle is set to 7 days long. I have have not tried to pre-define a cycle and see what happens the next execution after the cycle end date. Ideas?
