Automation Jobs
Last updated
Last updated
In Beta & Early Access
Testmo now allows you to launch test automation jobs in your CI/CD pipelines directly from Testmo. Read more below, or sign up for beta access here:
Upon the completion of the beta program, we plan to announce the general availability for automation launching, which will then be available for all customers on our Testmo Enterprise plan. If you’re not sure which plan your Testmo account is on or want to learn more about Testmo Enterprise, please feel free to contact our team!
Many teams execute their automated tests as part of their GitHub Actions or GitLab CI/CD pipelines. With automation launching, Testmo makes it easy to trigger automated test jobs in those pipelines at any time, directly from the Testmo UI.
In addition to the documentation on this page, we’ve also prepared some guides & resources on how to use Testmo Automation Launching with specific targets. You can learn more here:
The steps to set up automation launching are similar for both GitHub Actions & GitLab CI/CD. You can simply follow the steps below:
Configure the desired integration(s) in the Testmo Admin > Integrations area. Both GitHub and GitLab require secured integrations as automation launching targets, and each tool differs slightly in how the integration is configured. Learn more about how to set up the GitHub and GitLab integrations in our documentation area.
In the Testmo Admin > Automation area, add the automation job you want to launch from Testmo as a target. Again, the specifics for configuring a GitHub Target and a GitLab Target are slightly different and you can find full details of how to configure them as automation launching targets in our documentation area. Note that the target configuration relies on a working GitHub or GitLab integration, meaning step 1 above is a prerequisite.
Once the target has been successfully added, automation jobs can be launched from the Jobs view in your Testmo project. Simply navigate to the Jobs view, add a new job, or duplicate an existing historic job against the target(s) you previously created.
Note: To use automation launching, you must already have set up workflows or pipelines in your CI/CD tool.
The automation launching workflow assumes test execution occurs in the context of a GitHub or GitLab CI/CD pipeline. In our documentation we assume the Testmo CLI tool is also being used to submit test results to Testmo once the tests have completed, though this isn’t strictly necessary. However, since the automation launching feature provides testers with complete control over when and how test automation is executed, ensuring test results are reported to Testmo ensures a unified view of testing outcomes can be made visible to testers for real time tracking and progress reporting.
Automation targets are the foundation of automation jobs. Automation targets give you a way to specify pipelines, branches, or tags that you would like to be able to trigger ahead of time. While setting up automation targets, you can also include unique parameters, inputs, or variables to trigger pipelines for particular environments, datasets, etc.
As mentioned in the configuration steps above, GitHub and GitLab configuration specifics have a few differentiating features which are called out in the linked documentation, but are comprised of the following building blocks:
The target name - a unique identifier for the automation job to be launched, on the Jobs view
The target Connection - the CI/CD platform to be used for the job
The target settings - the project or repository identifier, workflow & any additional references required (in the case of GitHub)
The target inputs (for GitHub) or variables (for GitLab) - used to supply additional parameters to the job target. See below for more information.
Automation parameters (references in GitHub, variables in GitLab) may be used to supply additional information to the target when triggering a job in Testmo.
The parameter to be used should be specified in the target configuration, either as an input for Github, or as a variable for Gitlab. Once the target is configured, the parameter will be passed to the automation job once the job is triggered via the jobs view. You can learn more about the specific configurations for each platform here:
