Use a flow more than once in a journey

Posted by Tamara Yu about a year ago

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.

Plan stages

Posted by James Baldassari about a year ago

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.

Edit test steps within the mabl app

Posted by Tamara Yu about a year ago

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!

More Step Details in the mabl Trainer

Posted by Michael Bartucca about a year ago

Steps in the mabl Trainer (v. 2.2.75) can now be expanded to show additional information on the element when available. Simply hover over the step to show the step toolbar and look for the + icon which will appear when there is more information to display. Here you'll see additional details about the element interacted with during the step execution such as XPath, element ID, name, and more. You will also be able to see variable information for the step as well. mabl will continually update this information as tests are run in the mabl cloud.

Improved zoom for screenshots

Posted by Ryan Jones about a year ago

Add/Remove Auto Login Flow from the Trainer

Posted by Michael Bartucca about a year ago

Gone are the days of forgetting whether you added an auto login flow to a journey or not while training and editing. With version 2.2.65 of the mabl Trainer you can now view, add, and remove the auto login flow while training. Simply insert the "mabl Auto Login Flow" just as you would any other flow and you'll see it as a step in the journey.

Dive into test output with Visual Explorer

Posted by Joseph Lust about a year ago

Sifting through your rich test run outputs just got a lot easier!
You can now search all your test run outputs in one place with the Visual Explorer.

Test DataTable Associations

Posted by Andrew Mendelsohn about a year ago

Datatables are now associated directly with the tests that run with them. In the past, datatables were associated with tests as parameters within a plan. Now this association is directly with the test. By default, a test will run once for each scenario (row) in each datatable with which it's associated. You can still override this behavior using the DataTable or Ignore DataTables parameters in a Plan.

Bookmarking flow, test, and plan view filters

Posted by Simon Choy about a year ago

The filters for flows, tests, and plans are always displayed now. The filter settings are also saved as part of the URL now, so users can bookmark these pages with the filters applied and load the bookmarked page with the filters reapplied automatically.

See visual changes earlier

Posted by Sergei ML about a year ago

Easily detect visual changes without having to wait for mabl to create a visual model of your application. While mabl is training the visual change model, we will show all the visual diffs with respect to the previous run. So if there are any changes between runs, they will be highlighted.
You will not see insights for visual changes while mabl is learning. If you want to generate such insights based on a static baseline, you can use the Deployment Events API (Set as fixed baseline for visual change models)