DavidL
StaffJoined 5 years ago
User Profile
Staff
User Widgets
Contributions
Re: Cadence for feature request reviews?
Hi! Regarding technical consultation, it is not a service Smartbear provides today. I would encourage you to leverage our API to sync your script located in Git with Zephyr Scale. Using this API, you can create test cases, update scripts, link test entities to Jira requirements, and finally upload your results from the pipeline. Regarding the feature request, it is a continuous effort. However, we have hundreds of ideas in our backlog, and obviously, we cannot deliver each. The ideas in the public portal have a significant number of supporters and we have not even started them yet. So it will take time to cover the ones that are not yet in this roadmap.325Views1like0CommentsRe: If squad suits a lot of projects
Hi! To be honest, you would need to ask yourself additional questions to make a decision between Squad and Scale. Do you have a big library of test cases, do you need to organize them in folders? The same question goes for your test cycles. Do you need to reuse test cases, or parameterize them? If most of the answers are yes, you should go for Scale even if you do not need cross-project capabilities. Finally, note that Scale will not impact your Jira instance if you have a lot of test cases because Scale is not using a Jira issue to represent test cases.470Views1like0CommentsHow to submit a feature request?
Hi! We love to hear what you have to say about Zephyr Scale, especially improvements that can make the app work better for you. That’s why we created a public area to collect these ideas and share our own with you. Click on this link to access the Zephyr Scale roadmap. We encourage you to vote, comment on existing ideas, or create new ones. Our product management team conducts regular reviews of ideas. The displayed ideas are those we identified as the most important and possible to develop. After you created a new idea, you won’t see it in the roadmap. The product team will review it and possibly map it with other existing ideas. We consider every idea you send to us. First, we consolidate them internally. Then we include them on the roadmap if we find they have potential. Thank you! The Zephyr product teamRe: Create a JQL Query that mimics "Issues reported during testing" gadget
What about using the impactsTestResult() function to return any jira issues linked to a test execution or one of the execution steps? You won't be able to filter by test cycle except if you additionally link your test cycle to the issue.551Views0likes0CommentsRe: Problems integrating RobotFramework and Zephyr Scale
In Insomnia, can you try to add a Query parameter which would be named autoCreateTestCases. The value needs to be set to true. That should solve your issue and you can see the results in Scale. You mentioned you added test case keys to your robot tests. Do you have a test case key for each of your tests or some of your tests do not have a corresponding test case key? If you want to use the curl command, you probably need to escape some characters in the URL. https://api.zephyrscale.smartbear.com/v2/automations/executions/junit\?projectKey\="CORE"\&autoCreateTestCases\=true or you could try to use the URL like this (between double quotes) "https://api.zephyrscale.smartbear.com/v2/automations/executions/junit?projectKey=CORE&autoCreateTestCases=true"1.1KViews0likes0Comments