We're thrilled to announce that enabling a Segment integration with mabl is now easier then ever. As a reminder, mabl supports integrating to Segment in order to leverage real user data when calculating test coverage. This makes it easier then ever to focus your testing efforts on the things that matter most to your user base. See our blog on using Segment data to measure test coverage to learn more about the philosophy behind this feature.
The dashboard now has a "total coverage" metric card, a percentage calculated based on the number of pages covered by tests vs. total pages. Covered pages are those hit by trained journey in the last two weeks. Total pages are based on everything mabl has observed in the previous two week period from trained journeys, the free link crawler, and real usage data from the Segment integration, if configured.
Trying to test emails with dynamic subject lines? Record your email step as you normally do, then edit your email find criteria to use variables in the exact subject pattern.
It is now possible to define variables at the environment level. These environment variables will be automatically injected into every journey when running in that environment.
You can now find more information about your deployments in the mabl app when supplying the revision and custom properties fields.
We have recently exposed the version history for your mabl tests and flows. Now we are adding the ability to revert your test to a previous version.
A few updates have been made to provide a better experience triaging issues with network requests in mabl tests.
With the latest version of the mabl Trainer (2.10.14) you can now create assertions based on the target elements of existing steps. Under the step menu you'll find an "Assert on element" option which will allow you to configure an assertion on the target element of that step. When done you'll see a new assertion step inserted at the cursor location in the mabl Trainer.