Feature Requests & Ideas

To remove the dependency of Javascript, for counting similar kinda elements, we should be able to store the count of elements in some variable apart from asserting while using 'All Elements' Find Type under 'Find Elements',

As a QA, I sometime need to move steps, but it's never clear if the step will be moved before or after the one that is being highlighted while hovering it. It happens quite often that it's moving after when I need it before and vice versa. I would...

As a QA, I sometime need to move many steps together and keep the existing order. I would need to use the checkboxes "multi-selector" or a "hold shift select-many" to drag a bunch of step together.

In the mabl trainer it becomes difficult to see when I'm starting to test a specific part of my application and when I move onto the next area, example: Go to donations Enter donation amount Add in payment details Complete payment To be...

As a test author, when inserting an existing (named) snippet to a journey, I want to see its name in the step description (e.g. 'Run "wait_until_logged_in" snippet', instead of current 'Evaluate custom javascript snippet step'), so that later I ca...

As a test author, I want the option to enclose a set of steps/flows in a 'for' loop iterating over provided array of values or numeric range, so that I have a single source of truth for the repeated logic (therefore one place to make changes).

As a test author, I want the option of variables used in a flow to be passed to it as parameters, so that I can use the same flow with different input multiple times without having to declare/mutate the input variables in a previous steps (and pol...

Echo steps is the only way to comment steps in a journey. It would be easier to read what at test is doing if the echo steps is formated in boldface in the trainer and outside the trainer (read mode).

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