...
- Browse to your GitHub Repository's Actions tab, and select the new workflow for the list on the left side panel
- Click on Run workflow, override the defaults or provide values for the empty inputs if necessary (optional, useful if you want to change the VM Image, or Ansible version to test on, etc.)
- Scroll to the bottom of the screen an confirm by clicking on Run workflow
- Await for the run to complete to gain access to the report summary. If
If the test is successful you shall see are report directly in the UI, such as the following:
On the other hand, if the test deployment fails, you can check the report to understand if the problem is specific to the Item or the underlying VM provisioning, or dig deeper on run logs for details, or inspect the artifacts if available. This should allow you to pin point the reason of the failure without the need to run tests on your local environment.
| Note |
|---|
Common issues we observe in practice includemissing or misformatted SSH key within the GitHub Action Secrets, incompatible Ansible-Python-Linux versions, or sporadic timeouts due to VM ssh connection taking longer than expected. |
Conclusion
In five steps and with a few clicks you now have a simple way to make tests not only easy to trigger but also to reproduce.
...