How to import Jira cascade field values using Zephyr Test Importer
Hello, I am looking for suggestion on how to prepare the Excel file for Jira cascade field values when using the Zephyr Test Importer. For example, I have a Jira custom cascade field "Test Type". Option 1 = UAT Test. Option 2 = Master In Jira csv import, I would prepare the data as "UAT Test -> Master" for the custom cascade field. But in Zephyr test importer, this format didn't work. Only Option 1 was imported successfully. Option 2 was blank. Thanks, Sara
Option for Folder creation for Test Cases
We use Zephyr Squad on cloud at my organisation. The UI at my organisation has no option to create folders for test cases. I started a trial version of Zephyr Squad. The UI on the trial version provides a test case folder creation option. The UI on the trial looks much different and better. Both are on cloud and have the same Zephyr version 1.3.25-AC. I've attached screenshots from both. Is there a way I can get the trial version experience (i.e Create folders under test case etc.) on my organisation instance? Is there a setting that determines the UI experience?
is it possible to automate on creation test cycles and folder under Tests>Execute Tests.
I have a requirement that in our project where we need to create folders Under Tests>Execute test>Test cycles/Folders section.Every time I need to create some set of folders and Add test cases individually.Is there a way this can be automated and reduce manual work.All I need is to create few folders and add more than 50 test cases Via search filter for each folder.Can we run an ad-hoc still?
I'm sitting here, we have started adding test cases and created iterations, and things are looking great. 1st iteration done, loving Zephyr and we reviewed and discussed new tests for next release. But, When I create a new test case, I want to be able to add the test case to an "Ad-Hoc" iteration, but without going to and creating something called "Ad-Hoc" first, how would people normally do that?
"Internal Server Error" 500 code on using Save and Execute API
I have been getting an "Internal Server Error" (500 code) whenever I'm trying to use the save and execute API ( https://prod-vortexapi.zephyr4jiracloud.com/api/v1/automation/job/saveAndExecute) to upload the test execution reports. Here is an example of my request header and body: Request Header: { accessKey:{{accessKey}} jwt:{{JWT_Token}} secretKey:{{secretKey}} accountID:{{accountId}} } Request Body: { jobName:New Task jobDescription:New Task Desc automationFramework:Cucumber versionName:Unscheduled cycleName:AtestCycle createNewCycle:true appendDateTimeInCycleName:false folderName:Windows createNewFolder:false appendDateTimeInFolderName:false assigneeUser:{{accountId}} mandatoryFields:'{\"components\":[{\"label\":\"my component\",\"value\":\"my component\",\"content\":\"my component\"}],{\"reporter\":{\"label\":\"Jaya Kushwaha\",\"name\":\"Jaya Kushwaha\",\"id\":\"{{accountId}}\"}} automationVia:Upload projectKey:CC assigneeDisplayName:Jaya Kushwaha cycleStartDate:01/11/23 cycleEndDate:01/11/23 } Making this API call would result in the creation of the job on the U.I. but it is neither able to upload the cucumber report nor create the test cycle.
Updated Zephyr Squad Cloud version (01-11-23) for existing Cloud users
Hi everyone, I am trying to find out when the new version of Zephyr Squad Cloud (including the folder structure update) will be made available for existing Cloud users. In a blogpost from Smartbear on november 1st it is mentioned that the new Zephyr Squad Cloud version has already been made available for new Cloud users but not yet for existing users. Do we have an indication of when this will be available for existing users? Thank you!
Inconsistent Behavior between JIRA Test Automation UI and Zephyr Squad's Test Automation API
Hello, I am attempting to use the Zephyr Squad Test Automation API to upload test executions to the appropriate test cycles. Unfortunately, I have seen some pretty finicky behavior from the API itself. To clarify, we are using the Zephyr JIRA integration - Zephyr Squad. To begin, I sanity checked that my test result files were compliantwith formatting standards by uploading them manually via the Test Automation UI in JIRA. Plenty of test automation tasks were executed successfully, but with some specific workflows needing to be met. For cucumber formatted JSONs, it was necessary to use theCreate and Executebutton to get these testresults to upload successfully - in a single step. Uploading test execution results would fail If I wanted to break up the creation and execution of the Test Automation task into two steps. For example, I was able to create the automation task with the same file from the previous workflow by first choosing theCreateoption, but when I chose toExecutethe task, the task wouldhang withIn Progressstatus. I'd like to point out that none of the test result files or Task configurations had changed between these two workflows. With JUNIT xml formatted test results, the issues above were not encountered. So I thought, "hmmm, perhaps it is better to use the JUNIT xml format to upload test results." After deciding that we can move forward with JUNIT xml formatted test reports, I attempted to try out the Zephyr Squad Test Automation API via Postman. I was able to successfullycreate Test Automation Tasks via this API endpoint :https://prod-vortexapi.zephyr4jiracloud.com/api/v1/automation/job/create. However, I was unable to successfully execute the newly created Test Automation Task via this endpoint:https://prod-vortexapi.zephyr4jiracloud.com/api/v1/automation/job/execute. When hitting the latter endpoint with the appropriatejobId, I receive an Internal Server Error. However, if I provide a non-existentjobIdwith the payload, I do receive a response, indicating that the payload contains the correct contents and that the endpoint is indeed hit. I then attempted to execute the newly created Test Automation job via the JIRA UI instead - to see if I had any luck. Weirdly enough, the Test Automation job that was created (not executed) through the API was not able to execute and instead gave me this unexpected error: Considering I was unable to successfully execute the job via the API call in the first place (see Internal Server Error), I should not be encountering this error message. Additionally, the status for this job remains asUNEXECUTED. Can you please point me to what the root cause of these issues may be? This is pretty inconsistent behavior. Thanks
