Executing Automated Test Cases
Starting October 11, 2024 (Zephyr Enterprise 8.2), the Zephyr Enterprise documentation moved from its current location on Atlassian to a dedicated, standalone Zephyr Enterprise documentation page. Please see: Executing Automated Test Cases | Zephyr Enterprise Documentation
In Zephyr, you can trigger automation for your existing test cases by using a Script Automation job you created in Vortex. To do that:
1. Download and run ZBot.
2. Create a Script Automation job.
3. Open your test case and select the Automated Script check box in the Automation section:
The Automation section of test cases now doesn’t contain the fields it had in previous versions (Name, ID, Path). If you have data in those fields, during the upgrade, Zephyr will automatically create custom fields for that data and will migrate the content.
4. Go to Test Planning and create a new cycle for your test case.
5. Go to Test Execution, select your test case in the list and click E:
6. In the subsequent dialog, select the Vortex job you have created and specify the script to be used for automation in the Script Triggering field:
In the dialog, you can also update the parameters you specified when creating the job. In this case, the changes will apply only to the current execution.
7. Choose the status your test case will have during the execution and click Run. The following dialog will pop up:
Now if you open the test case and expand the execution history, you will see that execution status has changed to WIP (work in progress). After the execution is completed, the test case status will be updated in accordance with the data received from the test automation tool:
See Also
Zephyr Test Automation
Zephyr Vortex
Script Automation
Suite Automation
Folder Watcher
ZBot Overview
Â
Starting Release 8.2, Zephyr Enterprise documentation is moving from its current location on Atlassian to a dedicated, standalone Zephyr Enterprise Documentation page. https://support.smartbear.com/zephyr-enterprise/docs/en/welcome-to-zephyr-enterprise.html