Importing test cases via CSV that utilize call-to-test
Hello! I wanted to know if it is possible to import a mass amount of test cases via .csv file, which also use the call-to-test functionality (so that each of the imported test cases are referencing another set of steps/test cases). Is this possible? It doesn't seem to be when using the import wizard, but maybe there is another way? Thanks!
accessing images
Hello, How can I programmatically access an image stored on your cloud? I need to process your XML export which contains links to images. e.g. https://cloudfront.tm4j.smartbear.com/tenant/abc/project/123/xyz.png Do you have an API for this? Something like a simple get request (authorized with an api token). What I’ve tried so far, is a Get request with a cookie called ‘jwt’ set (the value is taken from the session when I log into Attlassian). But this is not long term solution. I saw a similar question here, but with no replieshttps://community.smartbear.com/t5/Zephyr-Scale-Questions/Is-there-API-to-download-attachments-from-test-amp-steps/m-p/260153 Thanks!
Add an attachment to test execution via API
Hi I saw that previously there was a discussion regarding it. to attach test artifacts to an execution. Is it possible to upload attachment to test execution via API? | SmartBear Community Is there any news on this matter? is it possible? or is there any workaround?
Publish cucumber test results to an existing test cycle
The automation executions cucumber API(v2/automations/executions/cucumber) always generates a new test cycle. Is there any way to upload the cucumber test result to an existing cycle rather than creating a new one? We are trying to create one test cycle/sprint and can have many test executions.
CSV fails to import Custom Step Fields
Hello everyone I am currently trying to import a Helix ALM export (.xml) to Zephyr using a script. The resulting .csv file is correctly formatted and double checked using csvlint. The problem is the following: I have added custom text fields in the Test Steps section (Step-note, Comment) and these simply get replaced with empty cells or get lost after/during the import, while all other fields are accepted as normal (Name, scope, objective, description, custom boolean fields, custom integer fields, non-step custom text fields, steps, expected result). I tried it with single-line fields and multi-line. This is purely conjecture but it's as if it deletes any fields that are not by default part of the Test Execution script, since Comment and Step-note can be added afterward and they appear as normal when the test is reloaded. Anyone have any idea where the issue could be?Test execn. outside Test Cycles _HELP
Hi all Is it possible to restrict users from executing Test cases outside Test cycle , we want to limit Test execution within Test cycle only . Please share any knowledge , hopefully there is a solution other than asking users :). When Test cases are executed within Test cycle it's allows for better report results > What are your thoughts Thanks in advance for your kind help - Let me pre-empt an answer cheekily "no there is no such options available but if you add it as a suggestion someone at Smart Bear may pick it up at some point in the future :) "
Changes to Zephyr Scale Test Cases
As well as the view changing in Zephyr Scale, when multiple steps are added at once to a test case via the plus sign on the previous step, it is impossible to type in the Step description box beyond the first step, unless all steps are deleted and added once more one by one. Also, when initially clicking on Step description box after the first step added is entered and filled in,Step has to be clicked twice as it enters an autosave mode and deselects the box. Also, it is not immediately apparent how to switch step order as the arrows are greyed out unless the step order number is hovered over specifically. The last is a matter of personal preference, but the other issues seem to be genuine bugs. Attached below is a video depicting what I'm experiencing. Thank you, A flummoxed QA
