Import/export from one JIRA project to another one (XML): Attachments links aren't exported
When I export JIRA Zephyr Scale test cases from one JIRA project to another one via XML file manually, attachments (files) aren't exported via XML file(neither added for particular step or added to Attachments tab). At the same time, if test case included images added to text fields (steps, etc.), they are exported as S3 links and displayed after importing to another project. Can it be improved? Thank you in advance!
Email notification when I assign test cases to my team
I need team members to get an email notification when test cases are assigned (or re-assigned) to them for execution. I know it isn't a feature currently in Zephyr Scale, but it is a feature I desperately need. This is particularly important as we ran several UATs across the year, involving several people in distributed location. The most efficient way to assign a test to the is for the action to trigger an email notification This is a feature that SmartBear needs to look into, because a lot of competitor applications can do it. My teams have recently moved to Zephyr Scale, from Azure DevOps, where such a feature was available.Missing/Incomplete API Integrations
Hi, Maybe I have just missed something, but as far as I can tell the following is missing from the Scale Cloud API which is making it's usage a bit... challenging. You can only fetch test case versions, cannot create new ones Cannot create Parameters for Test Scripts Cannot fetch Custom Field definitions Paginated requests don't support basic searching (Bit pointless without it...) Can't search for test cases which have no parent folder Can't update Owner/Priority after creation (Could just be my integration being incorrect) There could be more, but could anyone tell me if I am losing my mind, or maybe just looking at old documentation? https://support.smartbear.com/zephyr-scale-cloud/api-docs/#section/Introduction Maybe if there is more missing you'd want to add it to this thread and I'll do a big support ticket. Thanks
Test Execution Limits in Zephyr Scale
We've recently moved to Zephyr Scale and whilst the features and functionality are as expected, what is a surprise is the low levels of execution limits. So low in fact that we're almost thinking we've bought the wrong product or our use case is not what ZS is intended for. We are a small team (<10) who run all our CI/CD workflows through GitHub Actions (however, the same issue would occur with other orchestration tools such as Jenkins/Bamboo). Per CI/CD best practices, we run our unit tests (via Pytest) and integration/acceptance tests (via ZS) on every commit to our GitHub repos (i.e. multiple times per day). Multiplied across even a small development team, this will quickly reach hundreds, if not thousands of test runs per month. We're now aware, after purchase, of the test execution limits. My question is, the limits so low (100 default on the 11+ user Jira tier or 600 with Zephyr Scale Automate) that we think we're misunderstanding the product entirely. I have a support case open with Smartbear asking similar, but we wanted to sanity check our assumptions and see if the community is seeing similar limitations? Any help appreciated.
Why does the roadmap hardly change?
Hi folks, For most of 2023 the Zephyr Cloud roadmap has remained static. Well, certainly the 'planned' and 'in progress' categories has remained the same for ages, with the only items in them being 'data residency'. Can anyone from Smartbear confirm or deny if this roadmap is an accurate reflection of what the actual dev team are working on? (I'm not asking for the details, just some sort of indication that there are actually more improvements in the internal pipeline, planned). The reason I ask is that certainly the impression this gives is that the product is going to remain static for a long time and that none of the many good, and useful, ideas 'under consideration' are going to materialise any time soon. I think this erodes confidence in the long-term viability of the tool. I'd love to see some of those ideas move forward 🙂 Many thanks.
Test Case calling a Test Case with Parameters
I tried searching around for similar questions but didn't have any luck, so forgive me if this has been answered before. I have a test case with 2 steps. We'll call this TEST-T10. T10's very first step has a parameter that can be set. This is fine and works as expected. The problem is when I create another test case that calls upon TEST-T10 and then call a test case that calls upon that test case, I cannot set the parameter for T10's first step. This is pretty crucial to our how we're using Zephyr Scale, as many of the test cases we plan to create will use calls to test cases with simple parameters. Example: TEST-T10 has a parameter that is set in step 1. TEST-T11 calls TEST-T10, and you can set the parameters there. A final test, TEST-T12, calls TEST-T11 and thus I cannot set parameters for TEST-T10. Is there a setting I missed or a button I'm missing?
