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 advance
Is 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
`status` param ignored when creating execution via API
We're adding integration to Zephyr Squad via API. According to the documentation for the `create_execution` endpoint, we should be able to pass the parameter `status`, as an Object and set it to whatever value we want. We wanted to have this attribute set to "WIP". However, this parameter is simply ignored. These are the bodies of the request that were tested: '{"status":{"id":3},"projectId":10000,"issueId":10050,"versionId":-1,"cycleId":-1}' # supposed to be the right one '{"status":{"name":"WIP"},"projectId":10000,"issueId":10050,"versionId":-1,"cycleId":-1}' '{"status":{"name":"WIP","id":3},"projectId":10000,"issueId":10050,"versionId":-1,"cycleId":-1}' '{"status":3,"projectId":10000,"issueId":10050,"versionId":-1,"cycleId":-1}' '{"status":{"id":1},"projectId":10000,"issueId":10050,"versionId":-1,"cycleId":-1}' Neither of the above worked and each time in response we were getting an execution with the status "UNEXECUTED": ... "status":{"name":"UNEXECUTED","id":-1... Is there something we can do to make it work? Temporarily we'll be using a second call to update the created execution on the `update_execution` endpoint.
JIRA Test case execution
Hi Team, I need to integrate JIRA zephyr squad with my application. I want to automate the process of test case execution and cycle execution. Can you please guide me, how to do that? I have tried something and posted on the Zephyr Squad community link is given below https://community.developer.atlassian.com/t/zephyr-squad-cloud-rest-api-integration-is-not-working-for-me/74639/2 Please give me step by step approach to do it. Thanks, AkhtarNeed a dashboard widget that shows Test step status's
Need a dashboard widget that shows Test step status's. Zephyr Scale has a widget called Test Execution Results that shows the individual steps added to an test issue. We want to be able to report on this information and include it in our dashboards. Can this widget be added to Zephyr Squad?
Edit Test Case button always displayed on Test Execution panel
I’m executing a lengthy test script and I’m updating it at the same time. I find myself regularly pressing the Top button to access the Edit Test Case button, making then saving an edit, and then having to scroll back to the individual steps. I suggest making this button easier access by having it always visible on the interface.
