In the journey run output page, the selections related to visual changes are now grouped together to improve viewing on smaller resolutions. The
Side-by-side tabs along with the
Highlighting options dropdown are now grouped together inside the
Screenshot tab selection when there are visual changes for the step.
We recently gave users a way to supply custom step descriptions in the mabl Trainer and now we've made it even easier to edit them. Users can now double click any step description text and edit it directly in the step list view. This latest improvement can be found in trainer version 2.11.18.
Have you ever wanted to test a call to our Deployment Events API without actually executing any plans? You can now perform a preview (dry run) of a Deployment Event API call to see what plans would have executed, without actually running them. You can use this to quickly fine-tune your configuration and test your integration.
You can now view all the variables used in a journey in the trainer. The options in the Variables dropdown have been modified slightly, and there is now a new
View option. Clicking on this option opens up a new window that displays all of the variables in the journey.
You can now use custom prefixes with mabl Mailbox email addresses. Tagging your mabl Mailbox email addresses with a custom prefix can help you easily mark and differentiate addresses on your backend systems. (e.g. querying for results containing the chosen string in your own databases).
mabl now supports a native integration with GitHub Actions 2.0. Using the run mabl tests action, you can easily integrate mabl into your CI/CD workflow. The run mabl tests action has support for setting a new visual baseline, overriding the set of browsers to test and more.
We're excited to announce the release of the mabl GitHub app.
You can now select plan labels when creating a build step in the mabl Jenkins plugin. After adding your API key, the Plan Labels field will populate with all plan labels in your workspace. You can select multiple labels using the standard