We've made a few changes to the test details page to make it easier to use.
New to mabl is the test timeline, a feature that helps you easily identify specific steps and portions of your app that run slower than others. Optimize your tests and plans to run even faster. Zoom in to see more detail using the scroll wheel; drag left and right to pan while zoomed.
Assertion steps will now scroll to the target element (if there is one). The reason for the change is twofold:
Do you use the mabl Slack integration to notify specific channels when tests fail? Would you like mabl to mention certain users (such as yourself) in those messages so that they are alerted in Slack?
We're happy to announce that you can now filter the plan run history on your plan details page by status.
Coverage reports are now available on the coverage page under "Page reports". It's easier to see which pages have the most users and complexity and how much coverage they have (or lack), compared to the number of journeys covering each page. This may better inform which pages need the most attention from a testing perspective.
A little while ago, we introduced the application and environment summary tab under the "Configure" page in the mabl app. This tab allows you to manage your applications, environments, and the URLs that you're testing all in one place.
The mabl Coverage page will now report test coverage in terms of common pages of your application. We use a technique called "url-clustering" to group dynamic URLs of pages, giving you more accurate and readable coverage data on how mabl is testing your apps.
Building on the retry-on-failure feature for plans, there is now a new option that will cause only the failed tests to be retried when a plan goes from passing to failing. The new setting can be accessed after enabling "Automatically retry on failure" in the plan settings.
Now you can create assertions and IF conditions against template strings. Most notably, template strings can include references to variables.