We've made what's happening in the trainer more apparent. The cursor is now more visible and interactive.
You now have the option to change the size of the mabl Trainer to one of 3 different sizes in the latest release (2.10.47). There is a new menu in the upper right corner of the mabl Trainer where you'll be able to choose the new medium, and large size trainer views. This menu is also a convenient place to access other trainer options from as well.
Starting today, you'll be able to re-run a failed plan directly from an integrated Slack channel. See Integrating Mabl With Slack for instructions on how to connect your mabl workspace to Slack.
We have added the ability to share variables generated in a test run with following test runs in the same plan run! You can generate variables in one test run, and reuse them in test runs that are scheduled at a later point (sequential in the same stage or a following stage). There is now a toggle on the edit test modal to enable this feature for a particular test.
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.