Exporting test run artifacts

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:

• Export from the mabl app
• Export from the mabl CLI
• Export from the mabl API

These options are available for browser tests executed 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:

1. Click on …(More actions) > Export test run artifacts.
2. 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
3. Click Export to download the file.

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, artifacts can include:

• Screenshot
• Step trace (Chrome and Edge only)
• DOM snapshot
• HTTP archive (HAR)
• Console logs (Chrome only)
• Accessibility check results

From the mabl CLI

To export browser test run artifacts from the mabl CLI, use the mabl test-runs export command. The following artifact types are available for export:

To export specific artifact types, use the --types flag:

mabl test-runs export {run-id} --types variables

You can specify multiple types in a single command:

mabl test-runs export {run-id} --types screenshots variables

Or export all available artifact types at once:

mabl test-runs export {run-id} --types all

For the latest, most up-to-date list of available export types, see the mabl CLI command reference.

From the mabl API

To export browser test run artifacts from the mabl API, use the “run artifacts” endpoints in the reporting API:

1. Create a test run artifact export endpoint for a specific test run ID. The POST request returns an export ID ending in -ex.
2. Use the export ID to get the test run artifact export. The mabl API returns a URL where you can access a zip file containing the export.

The following artifact types are available for export via the API:

For full request and response details, see the create test run artifact export API reference.