You can now browse your app's test coverage in mabl to identify gaps and quickly find which journeys test each page. mabl provides three measures to understand your level of existing coverage for a page - number of journeys, steps, and assertions - and two measures to identify pages that may need to be tested or more thoroughly tested - number of other pages linking to it and its depth, i.e., number of links followed from the app's starting page necessary to reach it.
The recent addition of plan stages offers a lot of new and unique ways to orchestrate your test runs. Thanks to your feedback, you now have even more control over sequential stages with the ability to add an additional override option that will tell mabl to always run all sequential tests within a stage if one of those tests happens to fail. This override setting is available in the Stage options when editing a plan.
The mabl Trainer (v. 2.17.19) now has additional save options.
The mabl Trainer (2.7.14) now supports adding conditional steps and assertions against variables. The new Variable option should now appear in the list of conditions for the IF statement. You can now perform different steps depending on the value of certain variables.
Editing your recorded journeys just got easier! mabl Trainer v2.7.11 brings to you the ability to edit a click step or an input step. Look for the "Edit" option in the action menu that appears when you mouse over a step.
mabl now supports double-clicks in your journeys. As a custom find action, enter the CSS or XPath query to the page element and select Double-click from the action menu.
Users can now choose to clear site cookies in the mabl Trainer at the beginning of a training session. You'll now see the option to "Clear cookies matching current URL" above the "OK, train me!" button. Clicking this will clear the cookies matching the URL under test and perform a fresh navigation to the page.
The mabl Trainer (2.7.1) now supports adding conditional steps inside Journeys where IF, ELSE, and END steps are available to run groups of steps or flows conditionally. Under the "More actions" menu of the trainer you'll find the "Add conditional" option where you can begin inserting conditional steps. Conditionals can include any number of steps or flows and can also be used within a reusable flow. Any steps not executed during a Journey run due to a conditional will show up in the Journey output logs as a greyed out step with the indication it was skipped.
No one's perfect. We all makes mistakes, both people and, believe it or not, software. What do you want to do when you make a mistake? Undo it! And when you make a mistake thinking something was a mistake and want to undo your undo? Redo it!