Feature Requests & Ideas

After talking to mabl support, I would like to get an way to stop the execution engine from accepting windows.alert() and windows.confirm() objects at times.. We use this as a way to warn the user they are doing an action. There many instances o...

The screenshots provided are nice but many times they can be hard to understand as what happened in the test. A video recording of the test would be great in diagnosing the issues. Having the ability to set it to record always, record on failure a...

Please see if it is possible to define how many number of scenarios we wish to run for a particular run.Example- We have a test case with data-table containing 10 rows for different scenarios. What if i wish to execute only 2 in a particular test ...

At this moment it is possible to create branches, add changes to the branches, run and verify the changes and merge back to the master. It would be great to extend this versioning functionality a bit by making it possible to pull all (or a selecti...

I would like to be able to spun up containers that do the testing with certain options enabled. Specifically I would like to be able to have the container to use certain plugins like Dynamsoft Service. If we could manage which plugins got installe...

Currently, We are only able to check the sending address of one email sending address at a time. I would like Mabl email to allow any address I send to open up and assert to the email. The step reads Open the email sent from. I would like to be a...

This would be similar to how users can currently override the browsers used within stage options (screen shot attached). When planning test journeys, I would like the ability override the credentials used by a plan for specific stages. We are cu...

While large test runs are usually intentional, sometimes they are the result of an unintentional plan configuration. A simple UI prompt like "Are you sure you want to execute 200 test runs?", when a plan will execute more than 100 runs, would be a...

When an automatically triggered plan fails, in our App there usually appear regression problems with the state of the user. Which means I have to manually log in and reset the user to its default. As a user QA Tester, I would like to have an optio...

Instead of 1-24 hours for test trigger repetition, I need a way to run it in longer intervals. How about just making the input flexible, so that I can use any given number rather than a dropdown. His way user could still use 1-24 hours but also 48...