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!
The mabl image explorer now supports filtering on partial URLs as well as date ranges. This means you can easily filter down to a specific pages at any given point in time in your recent history, making it much easier to identify when visual regressions were introduced.
Two new random string macros have been added to the trainer in version 2.4.0:
The Bamboo plugin version 0.0.9 adds label support for creating deployments. Now you can restrict your plans that get kicked off by selecting labels from a multi-select box during configuration.
With version 2.3.7 of the mabl trainer you can now highlight elements in the page on demand and during replay of mabl steps. To highlight one on demand simply hover over a step, click the new highlight element icon, and the trainer will search for element in the current page and temporarily highlight it if found.
We are happy to announce that, starting with Trainer v2.3.6, you can use a flow more than once in a journey. Edits made to a flow are synchronized across all occurrences, as shown in this example where we use the same flow to perform two searches.
Journeys can now be grouped into stages for greater control over how they will run within the plan. Each stage can specify whether the journeys in that stage should run sequentially or in parallel. Subsequent stages will not begin execution until all previous stages have completed, so dependencies between journeys can be modeled by placing them in different stages. A stage can also be marked as always run which means that it should be executed even if a failure occurs in a previous stage, enabling patterns such as set up / test / tear down. See plan stages for more information.
We often hear from users that sometimes they just want to make a quick change to their test without leaving the mabl app. That is now possible with Trainer version 2.3.3. There are two ways to start editing a test: Quick Edit and Launch Trainer. In Quick Edit mode, the Trainer pops into the mabl app. You can edit almost everything, as long as it does not require interaction with the app under test. Replay is also disabled for the same reason. But you can delete steps, edit assertions, add waits, reorder steps, create flows, and so much more. Happy testing!