...
Zephyr allows kicking off or launching of automation scripts on remote target machines. For this to happen, testcases must have been marked as Automated and details about the automation script must have been added to that testcase in the Test Repository process. It is also required to have a remote agent - ZBot - installed on the target machine in order to launch the automated script on that remote machine.
...
Automation testcases can be executed by clicking on the "E" button that shows up for a testcase that has been marked Automated. A single test script can be executed or a batch of them can executed at one time.
...
Executing Multiple Automation Scripts
Multiple testcases can be selected in the Test Execution tool and then clicking on the Execute Multiple button. Upon doing that, the following window is displayed with the batch of test scripts added to it. They can be re-ordered by selecting them and using the Move up and down arrows.
...
...
Executing Single Automation Scripts
On selecting a single automation script to run, the following window is presented. Here the Path field can be modified (just in case it was entered incorrectly in the Test Repository or needs to be changed for other reasons). Changes made to this path here will not be written back to the original testcase.
...
...
Updating Automation Execution Results
Automation test scripts can be kicked off singly or in a batch as described above. Based on the type of script written, automation execution can be over in seconds or could days to complete. Either way, once the automation is complete, results can be updated into Zephyr in one of two ways.
1. Manually update or promote results
This is a good option to employ in the initial stages of Automation. If your automation scripts are prone to being disrupted by external factors (environment, data, unstable code etc.), you will have a lot more failures (potential false-positives or false-negatives). If you were to automatically update these results, they might not represent the true state of your execution. Remember, once results are updated in Zephyr, metrics are automatically calculated and this information is pushed out to gadgets. So, in these scenarios, its best to watch and complete your automation execution and when you are comfortable with the results, manually update the status of that execution.
2. Automatically update results
When you are comfortable with the state of your automation execution and confident in its ability to run without being disrupted by external factors (environment, data, unstable code etc.), automatically updating results is a great option. This can be done via the execution utility available in ZBots that use a webservices API call to update the results in Zephyr. Please refer to that section for more details.
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
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: https://support.smartbear.com/zephyr-enterprise/docs/en/zephyr-enterprise/zephyr-user-guide/test-execution/executing-automated-test-cases.html |
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:
...
| Info |
|---|
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.
| Expand | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
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