When debugging a failing journey, the trainer will provide helpful information about what caused the journey to fail.
This allows you to better understand what changes to make in the journey to return it to a passing state.
Additionally, the failure summary provides instant navigation to the failing step, further simplifying the debug process.
Customer security is a serious matter @ mabl. We’re constantly taking steps to ensure customer data is protected, such as the addition of new per customer journey output isolation and encryption.
It is now possible to jump to any step in your journey without stepping through the journey with arrow keys.
It is now possible to specify multiple environment-URL pairs in a plan
It's common in test automation to create an exemplar test that you then parameterize to run across a wide selection of data permutations. This approach is known by many names, including parameterized tests, data-driven tests, or table-driven tests. You can now do this with mabl, making it easier to cover your whole range of app behaviors.
We recently released a new version of the trainer that allows steps to be added or edited regardless of the current trainer mode. Prior to v0.3.4.2, some steps such as assertions and finds could not be captured unless the trainer was in "Live" recording mode. We recommended that users always turn on recording before editing steps. This is no longer necessary.
Filterable deployments history is now available by status in a chart and a table.
It is now possible to specify multiple browsers in a single plan. To do so, edit a plan and add a second browser under the Browsers section: