Duplicate paths are now combined across environments

The mabl coverage page now combines the same path, such as /workspaces, across hostnames and environments. This means that this /workspaces page will no longer be duplicated for each environment that you're testing in the cloud, such as app.myapp.com, dev.myapp.com, or qa.myapp.com.

As a result, your coverage metrics will now be more accurate and closely tied to the pages you're actually testing, rather than the specific environments they're being tested on. This is especially helpful if you're using our Segment integration, which reports on real user data for each page. For example, your tests may exist at an earlier stage in your development cycle than your production environment users are interacting with. Now, all that data for the same page will be in a single place. Plus, you won't need to hunt through multiple versions of the same page to find which environment your tests exist on.

🚧

Why has my mabl coverage percentage changed?

With the above improvement, the way coverage is calculated has also changed slightly. A single path across multiple environments, such as /workspaces, would previously count as a single page for each environment. This meant that you could have far different coverage being reported than what was truly being tested. Now, that page path will only count once regardless of the number of environments you're testing on. As a result, if your application has multiple environments that are being tested with many unique pages, you may see your coverage metrics increase or decrease. Note: If you only have one environment that you test on, you probably won't notice any change.

If you're interested in learning more about what coverage is and how to measure it, visit our coverage docs to learn more.