When teams test across different platforms, it can be difficult to collaborate and get a complete picture of application quality. To address this challenge, we’re happy to introduce Unified Reporting, now available in early access.
Unified Reporting consolidates your browser test results from cloud, local, and Playwright runs into a single location in the mabl app, so you can identify trends, enhance collaboration, and get a more holistic view of the quality of your app.
Viewing results across local, Playwright, and cloud
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.
Try it out
With Unified Reporting, you can publish results from local and Playwright runs to the mabl app.
Publish results from local runs
Unified Reporting is only supported for local runs triggered in the mabl CLI. Before you try it out, make sure to update your mabl CLI to version 2.61.11 or later:
npm install -g @mablhq/mabl-cli
To publish results to the mabl app, add the --reporter mabl option to the mabl tests run command. Local test output includes step names and outcomes of each step.
For more effective filtering of your local results in the mabl app, we recommend including the application and environment in your command:
mabl tests run \
--id [test-id] \
--environment-id [env-id] \
--application-id [app-id] \
--reporter mabl
You can also use the --from-plan-id option to publish local plan run output to your workspace:
mabl tests run \
--from-plan-id [plan-id] \
--environment-id [env-id] \
--application-id [app-id] \
--reporter mabl
Using --from-plan-id
Because the --from-plan-id option does not apply advanced plan configurations or parallel execution, we recommend creating designated plans for local runs that only contain a single stage of browser tests.
Publish results from Playwright runs
To publish results from Playwright runs to the mabl app, install and configure the @mablhq/playwright-reporter package. See the article on viewing Playwright tests in mabl for more detailed instructions. Playwright test output includes step names, logs, outcomes of each step, and a screenshot of the final state.
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.
Learn more
To learn more about how Unified Reporting works, check out the docs.
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.