Feature Requests & Ideas

There should be a separate pane on left side where user can see all elements. It should display all the elements created for that application and also has an option for user to add and edit elements locators. It would make a lot easier instead of ...

Currently, user can only create test with Mabl trainer which is not always convenient and fast. Quite often, it is easier to write test steps manually with actions and providing element locators.

User should be able to use data/variables from data tables in flows Currently, I see user can use variables from data tables in tests only. It can't be used in flows which doesn't make sense as flows are also sub-tests in itself where it makes mor...

When editing JavaScript snippet, it's not possible to notice errors now. (both syntax error and runtime error) It could be great if we can be notified of such error. For example, highlighting syntax error on editor, or displaying runtime error on ...

When some major changes that impacts many tests are deployed, especially for agile projects where Front changes are frequent. Then some additional flows may need to be added to the impacted tests. The user have to add flows to the every test one b...

As a QA Engineer, I would like to be able to provide a binary file input for the request body of an API test step so that I can validate that our APIs can work with files as expected.

As seen in the attached screenshot, a dev or QA has to input a string like 'yes/no' or 'true/false' or '0,1'. to override the default. It would be great if we had a boolean selector as a possible override. That way if the 'managed parameter' is as...

In order to quickly create and maintain multiple scenarios(datatable) tests, it would be great to have a way to manage (add, edit and remove), but also to switch in between the different scenarios records while in the trainer (creating or maintain...

User should be able to edit journey on all browsers (not just Chrome)Mabl trainer works with Chrome and not with other browsers.This restricts the user from editing his/her tests on non chrome browsers (example - Safari, Firefox)

When selecting an element in the trainer I want mabl to use the data-test attribute of the element (or child element) if it exists so that I can be explicit about the element I am expecting to interact with