Feature Requests & Ideas

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.

As a test engineer, I want to be able to record keyboard combinations. This would allow me to test such functionality in our product.

As a test engineer I want to be able to reuse variables I have created in previous journeys in the journey i am currently recording in order to avoid duplication of work and speed up test creation Example use case While recording a journey, i crea...

As a QA manager, I would like to be able to reuse a Flow multiple times inside a Journey, so that we can easily navigate back and forth between app URLs.

As a test engineer i want to the mabl trainer that appears in the dev console to be spread across the screen and fill all available space so the steps are easier to read and the buttons are always visible. Also if the console is open the trainer s...

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...

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...

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

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...