Feature Requests & Ideas

Currently we're able to trigger builds on certain days of a week or every 0-24 hours. As a user, I'd like to be able to trigger builds every x number of days, or on a monthly schedule.

As a mabl user, I want to reduce time investigating failed tests because they are flaky for the reasons of variable loading times and responses due to network or traffic or other factors like mabl unable to locate the element intermittently or fai...

I have scenario to test 4 links on UI, on clicked it is navigating to the details as per the click on same page. If there is an issue with one link the test is failing and remaining links are unchecked. To overcome this issue if we can use excepti...

As a tester I would like to be able to set each stage of my test to run with a different device. For example, I would like the stages 1, 3 and 5 to all run on desktop while stages 2 and 4 run on mobile. or It seems intuitive to me to not set the d...

I would like to add another column to the plan results window(to the below screen)

In testplans we are able to select multiple environments for a testplan to run against. Rarely do we actually want to run against both at the same time, this has caused us to create plans that are duplicates with only one selectedie"Smoke - prepro...

We are developing a system that uses maps and would like to run tests specifying latitude and longitude.

We would like to be able to specify a data table scenario to run when sending a data-driven test to the cloud execution. Also, would be a good option to have when sending the execution to the local run or in the trainer, when debugging.

As a tester, I want ability to use variable values created in one test to another, when executing test plan with data tables.

To identify accesses from mabl on the server side, I would like to be able to set a unique ID, such as test_run_id, in the HTTP header.