Insights

Mabl generates insights when it notices significant changes in the behavior of your application. You can explore these changes on the Insights page.

There are two main ways to use the Insights page:

1. Determine the current state of your application - monitor specific insights, such as visual changes, auto-heals, and JavaScript errors, on a regular basis to check for anomalies.
2. Identify when something changed in your application - determine when a particular change occurred, such as when a test auto-healed or when the page load time increased significantly.

📘

Slack and Teams integrations

If you use Slack or Microsoft Teams, you can configure mabl to notify you when new insights are available.

You can set up the Slack and Teams integrations to only notify you for specific types of insights, so you can focus on what's more important for your team.

Use the filters on the Insights page to explore insights by type, application, and environment. Click on the title of an insight card to view the details.

Read on to learn more about insight types and how to archive insights.

Insight types

Auto-healed a test

When a test runs in a plan, if there is not a strong match to what mabl knows about the expected element, mabl attempts to auto-heal the step. If the test passes, mabl generates an auto-heal insight.

Mabl does not generate an auto-heal insight, and does not record the auto-heal, if the step auto-heals in an ad hoc test run or if the test run fails.

Broken link insights

Mabl generates three types of insights while visiting linked pages in Link Crawler tests and visual smoke tests:

• Links broken: the link crawler test encountered broken links not found on the previous run
• Links fixed: the link crawler test encountered fewer broken links compared to the previous run
• Links working: the link crawler test encountered no broken links

Deployment integration working

Mabl generates this insight the first time that you trigger a deployment event in a new environment.

First run of plan started

Mabl generates this insight the first time that you successfully save and initiate a run for a new plan.

First test trained

This insight is generated the first time that you successfully save a new test.

JavaScript error insights

These insights are generated when mabl detects a change in client-side JavaScript exceptions during the execution of any test.

• JavaScript error: mabl encountered new client-side JavaScript exceptions during the execution of any test
• JavaScript fixed: mabl encountered fewer client-side JavaScript exceptions compared to the previous test run.
• JavaScript working: mabl encountered no client-side JavaScript exceptions in a test run after encountering JavaScript errors in the previous test run.

Login insights

For tests that use an auto-login flow, mabl generates the following insights:

• Login broken: An auto-login flow fails after passing in a previous plan run.
• Login successful: An auto-login flow passes after failing in a previous plan run.

Oauth integration activated

The insight appears when you set up an integration that involves Oauth token exchange, which includes the Slack and Segment integrations.

Page load insights

Mabl generates page load insights for the default visit home page and link crawler tests:

• Page load broken: mabl could not successfully load the application URL for the visit home page test.
• Page load successful: mabl successfully loaded the application URL for the first time, or for the first time after previously failing.
• Page load time high: the time to run the visit home page test was significantly longer than the time predicted based on past observations of run time.
• Page load time low: the time to run the visit home page test was significantly shorter than the time predicted based on the past observations of run time.
• Page load time normal: the time to run the visit home page test returned to the normal range.

Plan insights

Mabl generates two types of insights to inform you of changes in plan status:

• Plan failing: a plan fails after a previous passing run
• Plan passing: a plan passes after a previous failing run

Test run time insights

Mabl generates insights on test run time when tests run as part of a plan:

• Test run time high: the test run time was significantly longer than the time predicted based on past observations of run time
• Test run time low: the test run time was significantly shorter than the time predicted based on past observations of run time
• Test run time normal: the test run time returned to the normal range.

Visual changes

Mabl generates visual change insights when it detects a step with a visual change in visual smoke tests or in browser tests where visual change learning is enabled.

Archiving insights

If you already reviewed a set of insights and want to prevent the Insights from appearing in future results, click on the Archive all button.

Archived insights are not permanently deleted and may be accessed by setting the State filter to "Archived."

📘

Note

Archiving insights does not affect the insight metrics that appear at the top of the Insights page. Those metrics are calculated as follows:

• Test coverage: total test coverage averaged across all applications in the workspace
• Auto-heals: total auto-heals in the workspace, up to 100
• Visual changes: total number of steps with visual changes, up to 100
• Broken links: the number of broken links in the most recent link crawler run
• JavaScript errors: the number of steps with JavaScript errors in the most recent link crawler run