I create test executions for test sets and link multiple test sets to test plan. The test plan also shows overall execution status bar.
If I have same test associated to two different test sets,
test set 1 -{ test 1 - pass, test 2 - failed }
test set 2 - { test 1 - failed, test 2 - pass }
And test plan includes,
test plan 1 - { test set 1, test set 2 }
Then the overall execution status bar in test plan shows failed for both tests.
As, It gives higher priority to failed.
How can I change this and provide pass a higher priority than fail so that it shows pass in overall execution status of test plan?
Hi @celeste.valambhia and welcome to the community,
Could you please share a screenshot of what you see?
As far as I know this view depends on a configuration wheter to show latest execution or a specific version, etc....
furthermore one question comes up for me:
assuming both test sets run within the same version/test cycle how could the same test fail in 1 execution but pass in the other one?
Best
Stefan
Hi Stefan,
Thanks for reply.
I have the following scenario:
When tested with tests in Smoke-Test Test set it failed and when tested with other tests in WiFa Test set it passed.
So in Overall result in Test Plan I would like to show it as passed instead of failed. Is it possible?
There is one more scenario where if test execution is aborted for one of the test sets, the and passed for another test set, it will show aborted instead of pass in overall status of Test Plan,
I would like to know how to change priorities of the statuses...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would ask the question more likely from a "testing process" perspective:
What is the difference between smoke and WiFa? Is the SUT the same one? and also the same version?
If so then the question from my last post still stands: how can one and the same test case on one and the same test system be passed and failed at the same time?
The test case status will show you the status of your latest execution as this tells you if your current version is working (or if your test case does what it should in the current version/System under test).
From my point of view (not only as a Jira Admin but as a long year experienced test manager) this is the expected result.
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please consider to accept the answer if this was helpful in order to help other users to find a solution in case they are faced with similar problem.
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.