How do we handle retest executions with Zephyr when defect is fixed for the failed test case? With xRay we are able to create a retest execution to include failed test case to re-run. Test plan will take the latest result leaving both - failed and passed results in both executions, so we can track the history. Zephyr will just overwrite the status when re-executed, deleting the failed status, causing the issue with tracking fail status.
If I create a test issue, I don't see Test Details, Test Steps, or Test Executions. How are these fields added to the issue? The on-boarding for this product is very hands-off, and the documentation is also lacking quite a lot (or simply way out of date)
It turns out these fields are hidden on purpose, you won't see them until after you create an issue, save it, open the issue, then click the Zephyr buttons to show the hidden fields. According to support, this is a "fix for performance issues"... I'm sure Zephyr used to be a far better tool than this. We'll be looking for something a little more mature.
Very convoluted when you are really trying to do real work. There is a lot of overhead with this product but it's the 'best' around for the price at the moment.
Hello, When I want to create a new test case or add a test on the Cycle Summary page, I always get this warning on every page: "The Zephyr Test issue type must be added to the issue type scheme to use Zephyr in Project Cloud Development. An issue type scheme determines which issue types will be available to a project or set of projects." but I have already made the "Test" issue type settings.
How do we handle retest executions with Zephyr when defect is fixed for the failed test case? With xRay we are able to create a retest execution to include failed test case to re-run. Test plan will take the latest result leaving both - failed and passed results in both executions, so we can track the history. Zephyr will just overwrite the status when re-executed, deleting the failed status, causing the issue with tracking fail status.
If I create a test issue, I don't see Test Details, Test Steps, or Test Executions. How are these fields added to the issue? The on-boarding for this product is very hands-off, and the documentation is also lacking quite a lot (or simply way out of date)
It turns out these fields are hidden on purpose, you won't see them until after you create an issue, save it, open the issue, then click the Zephyr buttons to show the hidden fields. According to support, this is a "fix for performance issues"... I'm sure Zephyr used to be a far better tool than this. We'll be looking for something a little more mature.
It's excellent, does will we've more videos ?
Hi, Is it possible to reuse test cases ?
Very convoluted when you are really trying to do real work. There is a lot of overhead with this product but it's the 'best' around for the price at the moment.
Can you elaborate on the kind of overhead you mentioned?
You're right. JUst tried in Jira Cloud completely not clear what I need to do and how to add a Test
In Test Summary page, I see Total Unscheduled is 182. What is that and how can I bring down the no to 0?
Hello Team;
Do you have a video demo on JIRA CLOUD?
@zephyr how to automate this updating the executions? Basedon jira ids?
How to get the folder id?
Can automatic cases be made from complete test?
Did you get a solution?
Can I clone a batch of test cases in one go? (I usually copy relevant rows from the spreadsheets)
No, you can’t clone a batch of test cases in one go.
Hello,
When I want to create a new test case or add a test on the Cycle Summary page, I always get this warning on every page:
"The Zephyr Test issue type must be added to the issue type scheme to use Zephyr in Project Cloud Development. An issue type scheme determines which issue types will be available to a project or set of projects." but I have already made the "Test" issue type settings.
Hello where can I download ZBOT from the JiraCloud/ZephirCloud?
This is a very old presentation, Jira looks nothing like that anymore
😂🤣😆🥲😊😂😇🥰😋😚😌😉😅😂🥲🥲😊😇😆😆😘🐎🩷⛹️😇🦺🛷🟩🟩1️⃣😃😄😆😁🏒🛷☠️🙃😊😉😗😚
Are you really think that we need a music background in tech review?
This is an awful demo. The guy goes way too fast to follow.