Today we are thrilled to announce the general release of an exciting new feature in Testmo: automation launching. With automation launching, you can kick off test automation runs in your GitHub Actions or GitLab CI/CD pipelines at any time, directly from the Testmo UI.
Want to try automation launching but don’t have access to Testmo Enterprise yet? Click here to request a free Testmo Enterprise trial today →
Before this release, teams could easily configure their CI/CD pipelines to run automated tests and report results into Testmo. Reporting automation results to Testmo gives you the power to easily share the results with your whole team and unify the management of your team’s entire suite of manual, exploratory, and automated tests. However, the process of triggering those pipelines had to be done separately through GitHub or GitLab, often relying on input and availability from the development or DevOps team.
With automation launching, you no longer need to switch between tools to trigger automated test pipelines. Now, you can launch test automation runs at any time, right from the Testmo UI. This makes it easy to manage automation job launching and reporting entirely within Testmo, streamlining QA workflows and giving QA more control over test automation.
This initial release of automation launching is designed to give teams flexibility with the kinds of automation triggers you can configure to launch your automated tests from Testmo. The process of setting up your triggers, or “jobs”, is straightforward (note that you will need Site Admin permissions to configure automation launching in your Testmo instance):
1. Configure Your GitHub Actions workflows or GitLab CI/CD pipelines: If you haven’t already, ensure you have set up a CI/CD pipeline to run your automated tests and report the results to Testmo via the Testmo CLI. This setup remains the same as before. Need help? Refer to our detailed guides for GitHub Actions or GitLab CI/CD.
Note: If you have previously set up the Testmo integration with GitHub Issues, you may need to update the permissions for the Testmo App in GitHub to enable automation launching functionality. For more information, see our automation launching FAQs.
2. Connect Testmo to your CI/CD pipelines and set up Automation Targets: First, navigate to the Integrations page in your Testmo admin console to authenticate your Testmo instance with your GitHub Actions or GitLab CI/CD account. Then go to the Admin > Automation page to configure automation targets (specific workflows or pipelines you would like to be able trigger from Testmo). You can specify details like branches and tags and also include additional parameters for your pipeline trigger like variables and inputs.
3. Launch and track: Once everything is set up, launch your pipelines by queueing automation jobs from the Jobs area of your Testmo project, and then view the results as they are reported back into Testmo for tracking and analysis.
For full instructions, check out our in-depth guides on triggering GitHub Actions and GitLab CI/CD pipelines from Testmo.
Note: you can still use the Testmo CLI to report on your test automation in Testmo without enabling automation launching. For more about Testmo’s automation reporting, see the automation overview article in our documentation!
Automation launching is 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!
We’re committed to making your testing experience as seamless as possible, and this new feature is just the beginning! As always, we are eager to hear your feedback and ideas for future enhancements.
