Accidental Test Execution - Zephyr Essential Cloud
We have a question regarding Test Executions in Zephyr Essential Cloud. We accidentally created a new test execution of a test case that have a lot of steps and a lot of test results reported for them. Can the new Test Execution be deleted? Can previous execution results be restored or reused? What is the recommended way to re-run a test while preserving the history and results from previous executions? Is the Iteration feature intended for this use case?
Test execution by Tester widget: no link to navigate to list of tests assigned to Testers
Hello- Testers were used to be able to click on the link under Total column to navigate to the list of tests assigned to them to execute. After upgrading to Zephyr Essential there is no link for them to click in this widget. Please give us instruction of how to resolve this issue. Thanks
Add a new Test Cases into Newly created Test Cycle via API
Hello all, I would like to know how should I add a new test cases into created Test Cycle. In short I already created a test cycle through API, now I want to add a new test cases into the cycle. Note that the whole project is new so no test are present. This is what I want to do. I have several API tests in my Java project. Before the run I create the test cycle (which is working fine), after the creation I execute those API tests and after that I would like to create the text case into the previously created test cycle and send the status (pass or fail). I am getting the API endpoints from the following site: https://zfjcloud.docs.apiary.io/#reference/execution/add-tests-to-folder/create-execution Is it possible in that way? Is there an option to do that? How can I create these test cases in the test cycle? PS: I use Postman for now Thanks for the tips
Server CPU usage increases to 90-95% when a specific script is executed (usually 10%)
Hello, First of all, we are operating JIRA DC - Zephyr Sq8.0.0.80009607 When a user executes some automation scripts, the CPU increases by more than 90%.(usually 10%) We have not received the exact automation steps from the user yet, but we can obtain them if necessary. However, regardless of the consistency of the script, it seems that there is something strange about affecting the CPU of the installation server. I would like to ask if there are any bug reports already shared regarding this (Ex) It occurs when a specific command is called frequently).
Intermittent Performance Issues
What is everyone doing to fix intermittent performance issues in Zephyr Squad? My team regularly runs into issues when we are using the system heavily (i.e. during testing phases of projects) - so we can go a few weeks without using it but then we'll be in it heavily for anywhere from 2 weeks to 2 months. My testing team is small - only 6 people - and yet, every time we need the system the most, it has issues with slowness. There are times when executing a step will take up to 2 minutes to refresh. On longer test cases, that means we are spending a lot of time just waiting for the page to refresh so we can move on to the next step. Sometimes, the page is so slow it won't load at all. It never happens to everyone at the same time. I will get a couple users reporting issues and then about the time the issues stop for those users, it starts for the others. We do all the standard troubleshooting steps: clear browser cache, clear zephyr cache, clear zephyr permission cache, check for updates - none, reindex project metadata, reindex project executions (this takes anywhere from 2-5 hours so we lose time when we have to do this), switching to a different browser (mostly Chrome or Edge but Firefox has also been used) - and nothing resolves it. Eventually, the users give up and they'll come back the next day or 2 days later and all of a sudden it will work fine. We end up losing 2+ days of testing every project because of this. This has been an ongoing battle for years. I used to raise tickets regularly for this and either: 1, by the time someone got back to me the issue had resolved itself (with no rhyme or reason and no action taken). 2, the support person wouldn't read the details of my issue so I'd get shuffled around for weeks on end with nobody able to fix the problem because of language barriers. 3, I'd be told "the upcoming release will help resolve these issues" but those upcoming releases come out and get installed and it's no better. Needless to say, I don't even bother raising tickets anymore. At this point, we are shopping for other tools but moving is going to be a pain as we have a lot of history that has to migrate so we'd much rather get this working well. If there is a solution for this or if others know how to fix it as it happens, I'd love to know how!
Execution steps sporadically loading very slowly
Hello, dear SmartBear Community! We have a sporadic issue with Zephyr Squad for Jira Cloud. When it happens, we see a spinner instead of the test steps in the Test Execution (see attachment). The test steps in the corresponding Jira ticket are opened quickly at the same time, so the issue only affects Test Executions. The browser DevTools shows a specific slow endpoint - the one that loads execution details: https://prod-play.zephyr4jiracloud.com/connect/public/rest/api/1.0/execution/8cfb1aa5-... This does not happen consistently, but when it does, it usually lasts for a long time and affects all our QA team members. I.e. today none of the executions could be loaded for 3 hours (!). This makes the work of the QA engineers so much slower than it could be as most of the time during test execution is spent on waiting for Zephyr Squad. We filed a support ticket at the beginning of January. The response from the support team that we received 6 days ago (mid-February) was that a development ticket had been raised. There was no further update yet. We still continue to see the issue quite often. I would say that it has become worse since our support ticket in January as now we have days like today - when even page refreshes do not help. Does anyone else experience this issue? If you experienced and solved it, we would be grateful if you could share your solution. P.S. Dear SmartBear team, could you please help? We have been your loyal customers for 4 years now, and we used to recommend your products to our colleagues.
Required Execution fields when using Automation API
Hi, currently using the Zephyr Squad Server automation API to create and execute tests in bulk. Currently, I cannot find a way to configure the test execution created by the automation. We require either a comment or an attachment for every test execution as test evidence, but the execution created by the automation does not set these fields. Is there a way to either: Set default values for execution fields when creating an automation task Bulk update the comment field for a list of executions A possible solution now would be to pull all executions for the test cycle and update each execution one at a time, but our test suite is too large for this. Thanks in advanceIs there any way to import/upload test plan/test execution?
I am wondering if there are a way to upload not only Tests but to set thought upload in which Release/Test Cycle/Folder to place Tests for execution? We have ~300 TCs which are planned for execution for ~7 releases that have multiple cycles and folders. It's really time consuming to create all test plan tree and put cases there manually. How it can be optimized?
After migrating to cloud test executions are not under test cycle
Hello, Recently we are migrating from server to cloud with Zephyr squad, however we came across a strange situation. Below is the test case screenshot where we are able to see the test execution in Jan 2023 Malaysia Test cycle, however we are unable to see the same test executions in cycle summary under test cycle, however if we change the status of the test execution in test case it was automatically reflecting under test cycle. We need to see the test executions under test cycles as it was showing in on on-prem before migration. I have provided all the screenshots. please let us know your inputs
