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. CheersZephyr broken after latest Jira update
Hi, We recently updated to Jira 11.1.1 and Zephyr 11.3.0-jira10. This broke our Zephyr plug in. This is the error message we're getting: We've let custom support know about the issue but the estimate we were given for a fix would be sometime in 2026. What we would like to try now is to export our test cases from the Jira DB. Does anybody know if this is possible or how feasible this would be? Thanks!Creating issues within Zephyr scale
Hello ! Does anyone in here have a quick or smart solution when creating bug issues in Jira from Zephyr scale test run to get all the information like steps, test data (if possible) expected result and actual result copied over from the test case to the created Jira bug?
