With trainer version 0.3.1.12 and later, you can now see and delete the hovers that were captured when you had them enabled during training.
In the past, we suppressed the display of hovers because they tend to significantly outnumber trained steps and there was nothing you could do about it. Now that you can delete steps, it makes sense to give you a way to see and delete them, as they are the biggest source of unexplained delays during test execution.
You can now have more control over your playback in the trainer. Now when you are in playback mode, each step after the current location has a "Play through here" icon that let's you run the steps up to and including that step.
You now have controls to edit and retrain your tests in more places, including restoration of the previously announced but later removed test output location.
You asked, mabl answered. mabl's browser test traffic now originates from a static set of IP addresses so you can add a firewall rule and expose your non-public testing or production sites to mabl.
You can now terminate the latest running plan execution. Just click on the spinning Run button, and mabl will interrupt any journey that is still in progress.
This feature requires mabl Trainer version 0.3.0.0.
You can confirm your current Trainer version by right-clicking on the trainer icon in Chrome and clicking "manage extensions". To trigger a manual update from that screen, enabled "Developer mode" and click "Update extensions now".
You can now select a plan execution status to filter cards on the dashboard! This can be useful for filtering down to only the plans that are currently failing, or currently running.
You can now filter tests and plans on their respective pages. Just click the filter button and start typing in the column you want to filter!
Mabl now supports find last and find first as additional options when using xpath or css selectors to find a matching element. As opposed to find any, which will select any element on the page, find first and find last guarantee mabl will select the first or last element on the page. The selection criteria and actions supported are the same as find any.
You trained a test, saved it, and something went wrong. What do you do next?