WebdriverIO
Last updated
Last updated
Testmo works with any test automation tool, including the popular WebdriverIO JavaScript-based browser and mobile test automation framework. This quickstart guide provides an overview of how to report WebdriverIO test automation results to Testmo to get started with WebdriverIO test management.
Recommended: Using WebdriverIO with Mocha
WebdriverIO also supports Mocha as its unit testing framework. This is recommended, as this supports more features using Mocha's JUnit reporter (including custom fields, outputs & attachments). You can learn more in our Mocha documentation.
WebdriverIO comes with full support for generating JUnit-style XML files, which has become a standard format to exchange test results between tools. You just need to install the official @wdio/junit-reporter package and enable the reporter in your WebdriverIO config.
This will run your WebdriverIO 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 WebdriverIO documentation.
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:
We can now send the WebdriverIO 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):
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 WebdriverIO 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 WebdriverIO (testmo then starts and waits for WebdriverIO 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 WebdriverIO exit code
Testmo also supports additional custom fields for test runs, threads and tests. You can learn more here:
If you would like to submit additional fields with your WebdriverIO tests, we recommend using WebdriverIO with Mocha and then see our instructions on using custom fields with Mocha. Testmo supports many automation field types including strings, links, rich HTML, steps and attachment links.
Now that you are familiar with submitting your WebdriverIO test results to Testmo, you might also find the following additional examples, topics and references useful for more advanced workflows.
