Links

Playwright

Testmo works with any test automation tool, including the popular Playwright cross-platform end-to-end testing framework. This quickstart guide provides an overview of how to report Playwright test automation results to Testmo to get started with Playwright test management.

Run Playwright & generate XML file

Playwright comes with full support for generating JUnit-style XML files, which has become a standard format to exchange test results between tools. Simply set the junit reporter in your Playwright config and configure the filename and recommended settings:
playwright.config.ts
import type { PlaywrightTestConfig } from '@playwright/test';
const config: PlaywrightTestConfig = {
reporter: [['junit', {
outputFile: 'results/test-results.xml',
embedAnnotationsAsProperties: true
}]],
};
export default config;
$ npx playwright test
This will run your Playwright tests and automatically write all test results to an XML file in the results directory. You can learn more about configuring the JUnit reporter in the Playwright documentation.

Submit test results to Testmo

To submit your test results to Testmo, you simply use our cross-platform testmo CLI tool. The CLI tool is distributed as an NPM package and is easy to install on any system. Simply install our official @testmo/testmo-cli NPM package:
$ npm install -g @testmo/testmo-cli
$ testmo -h
Usage: testmo [options] [command]
[...]
We can now send the Playwright test results to Testmo. To do this, make sure to generate an API key in Testmo from your profile page. The API key is used to authenticate with Testmo to send the results. We can then use the testmo CLI tool so submit our results (note that we first set the TESTMO_TOKEN variable, which the tool expects):
Full example
Single line
Windows
$ export TESTMO_TOKEN=********
$ testmo automation:run:submit \
--instance https://<your-name>.testmo.net \
--project-id 1 \
--name 'Playwright test run' \
--source 'frontend' \
--results results/*.xml
If you run this example on a single command line, make sure to remove the backspaces:
$ export TESTMO_TOKEN=********
$ testmo automation:run:submit --instance https://<your-name>.testmo.net --project-id 1 --name 'Playwright test run' --source 'frontend' --results results/*.xml
On Windows, the command line uses a slightly different syntax to set a variable:
> set TESTMO_TOKEN=********
> testmo automation:run:submit --instance https://<your-name>.testmo.net --project-id 1 --name 'Playwright test run' --source 'frontend' --results results/*.xml
See command output
That's it! 🎉 This will automatically analyze the XML result file, create a new test run in Testmo, submit all tests & results and mark the run as completed. There's no need to manually create any tests, map tests or IDs or build any custom API code. Everything is handled automatically for you.

Bonus: Launch Playwright with Testmo CLI

In the above example, we first launched Playwright to generate the XML file and then used our CLI tool to submit the results in a second step. As an improvement to the above example, we can ask our CLI tool to launch Playwright (testmo then starts and waits for Playwright to finish). This has the following additional benefits:
a) Capture full console output and send it to Testmo b) Accurately measure test times c) Record the Playwright exit code
Launch Playwright with CLI tool

Bonus: Custom fields

Testmo also supports additional custom fields for test runs and tests. Additional fields for entire test runs (such as the current version hash or a link to your CI pipeline) can be specified from the command line. Use Playwright's custom annotations to add additional properties to the XML file for individual tests (make sure to also enable the embedAnnotationsAsProperties option in the Playwright JUnit reporter config, see above). Testmo will automatically read these properties from the XML file and submit these as fields to Testmo.
Add custom fields with Playwright

More resources & references

Now that you are familiar with submitting your Playwright test results to Testmo, you might also find the following additional examples, topics and references useful for more advanced workflows.