Last updated
Last updated
Testmo works with any test automation tool, including the popular 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 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:
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.
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
Testmo also supports additional custom fields for test runs, threads and tests. You can learn more here:
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.
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 .
To submit your test results to Testmo, you simply use our cross-platform 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:
We can now send the Playwright test results to Testmo. To do this, make sure to 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):
Also learn more and see other examples in the full .
To include additional fields for tests, use Playwright's . Make sure to enable the embedAnnotationsAsProperties
option in the Playwright JUnit reporter config as in the above config example. Testmo will automatically read these properties from the XML file and submit these as fields to Testmo. Testmo including strings, links, rich HTML, steps and attachment links.
You can learn more about Playwright's custom annotations in their . And you can learn more about supported by Testmo.