Whether you need to track test run results for compliance purposes or share results with your team for further troubleshooting, mabl offers a few different methods to export run artifacts for browser tests:
These options are available for browser tests that are run in the mabl cloud. For more information on the differences between local, CI, and cloud runs, see the test execution overview article.
From the mabl app
In the mabl app, you can export test run artifacts for all steps or for specific steps.
All steps
To export test run artifacts for all steps:
- Click on …(More actions) > Export test run artifacts.
- Select the artifacts you would like to export. Artifacts available for export include:
- Console logs (Chrome only)
- DOM snapshots
- HAR logs
- Screenshots
- Step traces (Chrome and Edge only)
- Xray JSON
- Click Export to download the file.
Exporting test run artifacts from the test output page
Specific steps
To export run artifacts for a specific step, click on the ACTIONS dropdown and select the type of data you’d like to export. Depending on the step, step-level artifacts can include:
- Screenshot
- Step trace (Chrome and Edge only)
- DOM snapshot
- HTTP archive (HAR)
- Console logs (Chrome only)
- Accessibility check results
Exporting step-level artifacts
From the mabl CLI
To export browser test run artifacts from the mabl CLI, use the mabl test-runs export command. See the article on exporting run artifacts from the CLI for more details.
From the mabl API
To export browser test run artifacts from the mabl API, use the “run artifacts” endpoints in the reporting API:
- Send a POST request to the create test run artifact endpoint for a specific test run ID. The POST request returns an export ID ending in
-ex. - Send a GET request to the get test run artifact export endpoint with the export ID. The mabl API returns a URL where you can access a zip file containing the export.