Other Tools
Testmo works with any test automation tool, framework and platform to implement test automation management. We've designed Testmo so it's easy to integrate all your existing tools and quickly submit your automated test results. And it doesn't matter whether you execute your tests as part of your CI/CD pipeline or build system or whether you launch your tests manually, any workflow works with Testmo.
The following lists provide an overview with links to various test automation tools and how to configure and use them to generate the needed JUnit XML report files that Testmo (and many other tools) use to report test automation results. Also see below for examples on how to use the result files to submit test automation results to Testmo.

Unit testing frameworks

Tool
Platform
Report XML files
NUnit
.NET and C#
Docs
xUnit
.NET and C#
Docs
Catch
C/C++
Docs
C++
Docs
JUnit
Java
Docs
TestNG
Java
Docs
Mocha
JavaScript
Docs
Jest
JavaScript
Docs
Jasmine
JavaScript
Docs
PHPUnit
PHP
Docs
Python
Docs
pytest
Python
Docs
minitest
Ruby
Docs
RSpect
Ruby
Docs
Got another tool idea for our list? Let us know so we can add it.

Browser, API & UI testing

Tool
Platform
Report XML files
Cypress
JavaScript
Docs
Katalon
Any platform
Docs
Many platforms
Docs
Postman
Any platform
Docs
Selenium
Any platform
Docs
SoapUI
Any platform
Docs
Any platform
Docs
Any platform
Docs
Testim
Any platform
Docs
JavaScript
Docs
Got another tool idea for our list? Let us know so we can add it.

Testmo test automation integration

See our complete test automation documentation
The following section provides a quick overview on submitting your test automation results to Testmo. We have more extensive documentation available to learn more about Testmo's test automation integration, CI/CD build systems and our CLI tool.
The approach to integrate automated tests with Testmo is always the same, regardless of the tool or framework you use. It's easy to submit your test results to Testmo:
  1. 1.
    You execute your automated tests, either manually from the command line, with your tool's interface or integrated with your CI/CD pipeline.
  2. 2.
    You configure your test automation tool or framework to write the test results to a file using the JUnit XML format. This format has become the de facto standard to exchange test results between testing tools and CI systems, so practically any testing tool and framework supports this format directly or indirectly. See the above links on how to generate result files with many testing tools.
  3. 3.
    You then use the Testmo CLI tool to submit your test runs to Testmo, including all test results, testing times, additional fields. Everything is handled automatically for you, there's no need to create test cases or suites manually first.
That's it! It usually only takes a few minutes to get started and send your first automated test results to Testmo.

Quickstart: Sending test automation results

In this section we will look at a concrete example on sending automated test results to Testmo. We will use the Testmo CLI tool for this, as it's the easiest way to send test results to Testmo.
To get started with the Testmo CLI, you can simply install the @testmo/testmo-cli NPM package. You do not need to use NPM, JavaScript or NodeJS for any other parts of your project. Our Testmo CLI tool works with any platform. Once you have installed the package, you can simply use the testmo tool from the command line. The following example shows how to install the CLI as a global tool on your system:
1
$ npm install -g @testmo/testmo-cli
2
$ testmo -h
3
4
Usage: testmo [options] [command]
5
[...]
Copied!
Most systems and environments such as CI/CD containers should already be prepared to run npm and install packages. If your system is missing NPM/NodeJS, just follow their guide on how to install these tools.
Once you have installed the testmo tool, you can use it to submit your test automation results to your Testmo instance.
To submit your test results, you simply run your test automation tool with the option to export a result log in the standard JUnit XML file format. This file format is also used by many CI/CD tools and test reporting systems, so practically any test automation tool and framework supports this file format. Also see the above links on how to configure many testing tools to generate such XML files.
After you have run your test automation tool and have generated the XML files, you use the testmo command to submit your results. You can simply pass one or multiple XML files and the tool automatically scans and detects all test results.
1
$ TESTMO_TOKEN=******** testmo automation:run:submit \
2
--instance https://<your-name>.testmo.net \
3
--project-id 1 \
4
--name "New test run" \
5
--source "backend-unit" \
6
--results reports/*.xml
Copied!
You need an API key for your Testmo user (or for a separate API user) to authenticate and submit your test results. Learn more about generating API keys. Our CLI tool also supports launching your test automation tool directly to capture the console output, record exit codes and measure test times. See the full Testmo CLI documentation for more examples and use cases.