This article explains how to troubleshoot test coverage metrics as reported by the page coverage dashboard: Coverage > Page.
If the page coverage dashboard shows no data or data that you believe to be incorrect for a specific 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 page coverage dashboard uses the output of link crawler tests to calculate test coverage in your application. If the page coverage dashboard shows no data for an 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.
Check the exclusions list
If it seems like some paths are missing from the page coverage dashboard, check the exclusions list. Make sure the exclusions list in the page 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/123/usage into one page. It does not group together paths that don't match the pattern, such as
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.
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 page coverage dashboard.