Reviewing test results

From troubleshooting failures to monitoring for regressions, mabl offers a range of tools to review and understand what’s happening in your app. For failed test, plan, and deployment event runs, start with conversational results analysis. As you chat with the mabl agent to investigate the failure, you can pull in supporting diagnostics and export the results of your investigation as a custom PDF report.

This article provides an overview of the diagnostic tools, dashboards, and integrations you can use to understand and act on results from your mabl tests, including links to more detailed articles for further reading:

• Understand output
• Resolve issues
• Review trends
• Share results

Understand output

The Results section of the app organizes mabl results by test, by plan, and by deployment event. Open a specific run to review details, from high-level information like environment and status to step-level details.

If you want to review multiple runs simultaneous, open virtual tabs to allow for easier switching between different test runs.

For more details on test output, check out the articles on understanding output in mabl help.

Resolve issues

When failures occur, start with conversational results analysis. The mabl agent reviews the failure automatically, answers targeted follow-up questions, and compiles supporting evidence, including screenshots, step logs, network logs, and comparisons to previous runs, into a shareable PDF report.

For more targeted guidance on specific issues, the troubleshooting section in mabl help includes articles on diagnosing common failures, so you can spend less time debugging, iterate faster, and minimize the impact of bugs on the end user experience.

Review trends

As you build coverage and execute more plans, mabl starts aggregating metrics across tests. By understanding these trends, you can prevent regressions, optimize performance, and ultimately deliver a more stable and reliable product.

To get started with reviewing trends, check out the following dashboards and features:

• Coverage dashboard - filter tests by application, environment, and more to understand the overall quality of your test suite. Filter data on pages to identify areas of your app that lack coverage.
• Insights - review insights to monitor for changes in your application, such as auto-heals, increases in load time, and visual changes
• Accessibility dashboard - review accessibility issues across your tests
• Performance metrics - monitor the performance of your app over time

Share results

As you learn more about your app, it’s important to keep other members of your team informed. By sharing results with the wider team, you can build a shared understanding of application quality and make more informed decisions as a group.

To achieve these goals, consider the following options:

• Copy the URL from a specific test output page to share a direct link with other members in your workspace
• Integrate mabl with Jira - attach mabl test results to your tickets for improved traceability and context
• Set up Slack or Teams - send notifications of activity from your mabl workspace, such as failures, insights, and comments directly to the channel of your choice to speed up the issue triage process
• Export output from a specific test run, including PDFs or other test run artifacts
• Set up email notifications for results from plans
• Use reporting API endpoints to set up custom reporting to an internal database
• Export results to BigQuery for further analysis