All data deleted after upgrading to v8.0 via Jira/Atlassian
After upgrading "Zephyr - Test Management and Automation for Jira" via Jira/Atlassian all of our data has been deleted from Zephyr - tests cases, cycles everything The app showed as disabled, but after re-enabling nothing was brought back. I tried using links that I had saved elsewhere, but these cannot find the test case etc. I tried adding a new test case to see if this made anything happen, but again no luck. Any ideas on how to get this back?Test Execution Scorecard ( mystery)
Has anyone see this before and know what the issue might be? The 'Test Execution scorecard by test cycle' has started to shift each test cycle row left by one column. So the name of the test cycle is dropped and the figures are all one column out? we have not made any changes to jira / zephyr and issues seems to be limited to a project Thanks in advance for any insights on resolving this issue
Zephyr - Test Steps and Expected Steps are missing after importing tests to jira from excel sheet
Hi Team, After new update of zephyr I can see while importing tests from Excel sheet we observed that tests steps and Expected Steps are not showing, even for older tests also steps are missing. Please help on this how to resolve it.
Zephyr + Reflect - Unknown Error on connect
Hello. When I am trying to start my zephyr test case, and I'm using reflect tunnel to be able to utilize my vpn connection, I get an unknown error popup. When I check the tunnel's dashboard, it shows successfully connected, so not sure why zephyr can't make the connection.
Best Practice for Test Data within Modularized Test Cases?
Hello, my team would like to use test case modularization as outlined here: https://smartbear.com/blog/scale-your-test-management-in-jira/ Our situation: JIRA with Zephyr Scale 1 project (for 1 application) > 30 regression test cases typical test case length differs from 50 to 200 steps depending various same or similar test steps across multiple test cases that vary only regarding test data all test cases are user tests mirroring the typical user's journey in the application We started by creating modular test cases that each deal with one specific form within the application. These modules contain only the test steps and not the test data. The test data should be provided in the main test case that calls upon the respective module. However, there is no option to supply the imported test steps with additional test data within the main test case. Which approach / best practice would you recommend? Best regards, A.
Zephyr Scale Component In Issue Created
Hello ! So my boss wanted to know if it is possible for better tracability if it is possible to show the Component that we put on the test case for it to show up if an issue is created. Like if its possible to show up as shown in the picture "QMS-E37672 Base Functionalities" But instead it would be something like "QMS-E37672 - COMPONENT NAME - Base Functionalities" Or something like that, he would like to get a clearer overview of where the bug is located without extra clicks, only solution ive come up with is to change that into the name.Harmandeep Singh Kandhari-Clarification on Test Case Versioning & Execution Mapping in Zephyr Scale
Hello Community, I am Harmandeep Singh Kandhari and currently using Zephyr Scale for Jira and need clarification regarding test case versioning and execution mapping. How does Zephyr Scale manage different versions of a test case when linked to multiple test cycles? Additionally, if a test case is updated, will previous execution results remain unaffected? Please advise best practices. Regards Harmandeep Singh KandhariSchema is missed for the "file" field for the '/automations/executions/custom' endpoint.
Hi all, Can anyone please point me to the schema for the "file" field for the '/automations/executions/custom' endpoint? https://support.smartbear.com/zephyr-scale-cloud/api-docs/#tag/Automations/operation/createCustomExecutions
Dynamic expected results field for test reuseability
Dear Community, I’ve recently started working on optimizing our test strategy, and one area that stood out was improving test reusability. We already utilize the capability to link test cases across different projects at the test cycle level, but this introduces a challenge I’m currently facing: all the original expected results are also linked to the new projects. At the test case level, I’m trying to separate test execution from test evaluation. The idea is that for newer projects, I could simply define new evaluation criteria for an existing reusable test case. However, in practice, this means copying existing test cases from Project A to Project B just to adjust the expected results field, which defeats the whole purpose of reusability. My question: Is there any way to achieve this separation in Zephyr today, or could this be considered for a future feature? Ideally, I’d like to keep a single test case and dynamically apply different expected results or requirement sets per project without duplicating the test case. I'm using Zephyr Scale Cloud. Your thoughts are appreciated. Cheers
