...
- Approach 1 allows triggering TestComplete projects directly from Zephyr StandaloneEnterprise, which then parses the generated JUnit XML file to update the test case execution results.
- Approach 2 involves using the TestComplete Jenkins plugin, which needs to be setup and triggered separately. Then a Vortex Folder Watcher job is created in Zephyr Standalone Enterprise to watch for and parse the generated JUnit XML file.
...
| Approach | Pros | Cons |
|---|---|---|
| 1 - Triggering TestComplete Directly |
|
|
| 2 - Leveraging TestComplete Jenkins Plugin |
|
|
Triggering TestComplete directly from Zephyr
...
Enterprise
Overview for this Approach
...
- Install TestComplete and create a BAT file to trigger the desired project
- Install and configure zBot on the same machine as TestComplete
- Setup an Automation job in Zephyr StandaloneEnterprise
Step 1 - Install and Configure TestComplete
...
ZBot is an agent for Zephyr Standalone Enterprise that runs on the same machine as the target test automation tool, and communicates with Zephyr Standalone Enterprise to receive jobs and post results. You may read more about it here: ZBot Overview
...
Make sure the Zbot is working properly by opening Zephyr Standalone Enterprise and checking that the ZBot is available under the drop down menu.
...
Now, once the Jenkins build is triggered/run, the Vortex Folder Watcher job will check the specified results folder containing the JUnit XML file. Upon finding a new file, the results are parsed and consumed by Zephyr StandaloneEnterprise.
| Tip |
|---|
Don’t forget to specify the XML path as an additional command line argument. This will help to produce the JUnit report file, which the Vortex Folder Watcher will use. You might want to setup some post build actions for cleanup, such as deleting temporary files generated by the automation run. If doing this, clean out the Folder Watcher location too so when a new run happens, the folder will have a new file to parse. |
...