Feature Requests & Ideas

I would like to be able to see all of evaluated parameters. This way I can find out if it was the assertion or the setup of the variable that failed without having to run debugger in the javascript.

When writing software with code the standard practice is to comment as much as possible.The mabl Trainer does a great job at explaining 'what' it's doing (e.g. assert "search" of current URL contains "Test"). But we would like the ability to add c...

I would like the ability to play back individual flows to test them in isolation and ensure they work correctly. The option for this could be when hovering over the 'Start flow' item.

I would like to be able to do an Else If statement. It would make it easier instead of having use nested If statements to check multiple items in my test case.

It would be nice if the trainer had the ability to duplicate a step instead of needing to record the step again.

While adding steps through click and record is key to Mabl and a feature I love, I would also like the ability to manually add steps. For instance manually adding a step to Go To a specific URL etc.

The trainer can’t currently assert a path containing a query string (e.g. test.com/search?page=1).

As a user, I would like to trigger an API call as part of my journey run. Some users have expressed interest in making API calls as part of their journeys in order to trigger events within their applications, set values for variables used elsewhe...

Generating all upper- or lowercase random strings is necessary when the application under test transforms the random input to lower or uppercase. Without this ability, it is impossible to assert against the mixed-case variable later in the the jou...

It seems the mabl variables now do not allow duplicate names, which we think is a good feature. It can make the variable names more clear in every journey. However, it may lead to another problem. We have many test senarios which we need to verify...