Nightwatch
A guide for generating Trunk-compatible test reports for Nightwatch
Last updated
A guide for generating Trunk-compatible test reports for Nightwatch
Last updated
You can automatically detect and manage flaky tests in your Nightwatch projects by integrating with Trunk. This document explains how to configure Nightwatch to output JUnit XML reports that can be uploaded to Trunk for analysis.
By the end of this guide, you should achieve the following before proceeding to the to configure your CI provider.
After correctly generating reports following the above steps, you'll be ready to move on to the next steps to .
Nightwatch will automatically report test results in multiple formats. You can configure the output location by updating the nightwatch.conf.cjs config file.
You can also specify output at runtime with the command line option --output <OUTPUT_FOLDER>:
Nightwatch outputs multiple reports for each test suite under the specified output folder.
If you configured your output folder to be under ./test-reports, the JUnit XML files will be found under ./test-reports/**. You can upload multiple JUnit reports by using a glob like ./test-reports/**/*.xml.
Duplicate Uploads
When using globs, it's important to clean up old test reports between test runs. If your glob path contains old JUnit files, uploading old test results can cause tests to be mislabeled.
You need to disable automatic retries if you previously enabled them. Retries compromise the accurate detection of flaky tests.
Nightwatch doesn't implement any form of automatic retry for failed or flaky tests by default. If you have a custom implementation of retries, remember to disable them.
Before modifying your CI jobs to automatically upload test results to Trunk, try uploading a single test run manually.
You make an upload to Trunk using the following command:
Configure your CI to upload test runs to Trunk. Find the guides for your CI framework below:
You can validate your test reports using the . If you don't have it installed already, you can install and run the validate command like this:
This will not upload anything to Trunk. To improve detection accuracy, you should address all errors and warnings before proceeding to the next steps.
