Set Environment When Uploading Test Execution Result to Zephyr
We are using Zephyr Test Managment and Automation for Jira Cloud. We were able to setup a test execution via Gitlab CI and upload the result to Zephyr via https://api.zephyrscale.smartbear.com/v2/automations/executions/custom. But one thing that we can't figure out is to set the environment where we did the execution. We've tried passing "environment", "environmentId", "environmentName", etc. But none of them works. Zephyr doesn't seem to recognize them. We can't seem to find any documentation about it as well. Here's what we tried so far: { "version": 1, "executions": [ { "source": "My Request", "result": "Failed", "testCase": { "name": "API response has status 200", "key": "TESTKEY-T123123", "environment": 3814706, "environmentId": 3814706, "environmentName": "QA" } } ] } And here's what we're always seeing in Zephyr: Can anyone shed some light as to how we can make it work?
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. ThanksInfinite spinner for Test Cases view when editing a Test Cycle
After getting a generic error for saving current state of the Test Cycle sometimes I'm getting an infinite spinner on the Test Cases tab and nothing can resolve it - tried to close the tab, browser, tried to logout and re-login to Jira - the spinner is still present on Test Cases view of the Test Cycle Zephyr Scale on Jira Cloud
BDD - Gherkin Script - Unexpected error "Line should start with one of the following keywords:"
From today's morning, our team got a couple of errors in the previously valid BDD test cases. In all cases, the error message is the same: Line should start with one of the following keywords: Given, When, Then, And, But, *, or #. Interestingly, we have many similar tests for different endpoints, but errors appeared only in a few of them. Also, there are no new release notes on the Zephyr Scale, so what happened, and when will it be fixed?Using Zephyr Scale and Python/Robot Automation
My company is using Zephyr Scale within Jira for manual testing. About a year ago, we started using Python/Robot Framework for automation. I'm trying to figure out how to integrate the two. When creating our manual tests, on the Details page, there's a dropdown that says "Automatable" which I set to Yes but there's no other indication of how to use this field. Any suggestions?
Test Executions - No Test Cycle, how to edit / delete?
I'm using Zephyr Scale Cloud, and have found that if I start a new execution from the Jira Story ticket that's linked to the Test Case, then it's essentially created as an Adhoc execution, not associated with any Test Cycle. Is there any way to update the executions, so that they can be linked with an existing Test Cycle? Or at least be able to delete any executions that were accidentally started.
no permission
Please I am new into Software Testing and I am having a challenge using Zephyr scale. Although I am still using the trial version but its really frustrating and hindering my learning process. Seems my permission is restricted, I cant create test cases, even the one I managed to create, I cant save the test script. Please kindly help!
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.
