When testing is spread across multiple platforms, it’s hard to get a comprehensive view on application quality. Unified Reporting addresses this challenge by providing a shared platform for your team to review and discuss results from mabl cloud, mabl local, and Playwright, giving you a more holistic view of application quality across all execution environments.
To implement Unified Reporting in your workspace, you need to make some small changes to publish results from local and Playwright test runs. This article explains how to do that.
Early access
Unified Reporting is available for all users to try out during the early access period. Prior to general availability, changes to this feature may be made without notice. Access and pricing for this capability may also change upon general availability.
Local results
Local results include step descriptions and results.
Unified Reporting is only supported for local runs triggered in the mabl CLI. To publish local run results to the mabl app, use the --reporter option with the argument mabl:
mabl tests run \
--id [test-id] \
--environment-id [env-id] \
--application-id [app-id] \
--reporter mabl
Associate local runs with a plan
To publish local results to a specific mabl plan, you can combine the --from-plan-id and --reporter options.
mabl tests run \
--from-plan-id [plan-id] \
--environment-id [env-id] \
--application-id [app-id] \
--reporter mabl
Local runs use the plan as a grouping mechanism and do not apply advanced plan configurations, such as parallel execution, stages, browser settings, and shared variables. Due to these differences, we recommend creating designated plans for local runs that only contain a single stage of browser tests.
Playwright results
Playwright runs include step descriptions, logs, and results and a screenshot of the final state of the test.
To publish Playwright results to mabl, install and configure the @mablhq/playwright-reporter package. See the doc on viewing Playwright tests in mabl for step-by-step instructions.
Configure a Playwright plan
Similar to publishing local runs with the --from-plan-id option, you can also add a planName option to the Playwright reporter configuration. Unlike local runs, which publish results to existing plans, Playwright runs publish results to a new plan that uses the plan name you configured in Playwright.
Limitations
- Only browser tests are currently supported for Unified Reporting.
- Playwright and local test runs do not track performance data or contribute to accessibility results.
- GenAI Test Failure Summaries are not supported for local and Playwright runs.