This article explains how to troubleshoot test coverage metrics as reported by the browser coverage dashboard: Coverage > Browser tests.
The browser coverage dashboard calculates overall test coverage of your web apps and breaks down coverage by page. By reviewing page coverage metrics, you can identify areas in your application that lack test coverage.
If the browser coverage dashboard shows no data or data that you believe to be incorrect for a specific web application, take the following steps to troubleshoot:
- Ensure the link crawler is turned on
- Make sure the link crawler is visiting links
- Check the exclusions list
- Check the page groups
Ensure the link crawler is turned on
The browser coverage dashboard uses the output of link crawler tests to calculate test coverage in your web application. If the browser coverage dashboard shows no data for a web application, make sure the link crawler test for that application is turned on. If the link crawler test for the application has not run in the past 14 days, mabl cannot calculate test coverage.
Make sure the link crawler is visiting links
If the total number of pages for the application seems incorrect, make sure the link crawler is visiting links. If the link crawler test is not visiting any links in your application, mabl cannot accurately calculate test coverage.
For more information on troubleshooting link crawler tests that aren't visiting links, see our articles on link crawler settings and link crawler FAQs.
Check the exclusions list
If it seems like some paths are missing from the browser coverage dashboard, check the exclusions list. Make sure the exclusions list in the browser coverage dashboard does not exclude the paths you are testing.
Exclusions apply to all applications in the workspace.
Check the page groups
The Application pages table uses URL clustering to group pages together. If the table groups together pages incorrectly, check the configured page groups for your application.
Manually configuring page groups
Grouping pages together
Use a wildcard [*] specify a directory that you want to group into one page.
For example, the path settings/*/usage groups together settings/abc/usage and settings/123/usage into one page. It does not group together paths that don't match the pattern, such as settings/123 or settings/123/xyz/usage
Ungrouping different pages
If URL clustering has automatically grouped together pages that are different from each other, enter a specific path to "ungroup" any page that matches that path. For example, if you add settings/edit/usage to the configured page groups, mabl counts any URL whose path matches this pattern as a separate page.
Limitation
If there are two or more applications in your workspace that use the same app.url, mabl assigns all URLs and pages to one of the applications. The remaining applications show no test coverage in the browser coverage dashboard.