Feature Requests & Ideas

We use mabl for some RPA/automation cases when we don't have APIs for a web application. We would like the ability to access a file downloaded by mabl via API so we can integrate with it as part of a larger workflow automation. Example: mabl logs ...

Request Add the ability to inject a variable into a test's environment directly via the CLI and Runner. Example Set the user name and password that I looked up from a DB. mabl tests run --id someTestId --vars username='foo' --vars password='bar' o...

To create api test from terminal instead of browser test Suggestion example: $mabl tests create <url> <test name> --api

When adding an API step, you can click Send and get the response. When you set it to looking at the JSON body, it would be great if clicking on an element of that body auto filled in the path. For example, if my response body was "body": [ { "noti...

When adding an API step, I often end up using various variables I've created in the test. I'd like an easy way to see available variables when I'm writing it. Auto complete any time you write "{{@" would also make sense.

There is a mabl test-runs export command in the CLI, but it does not export failed steps, etc., so it can only be used to download screenshots. The test results can be downloaded in PDF format, but I want to download the same information using the...

Some of our API testing requires generating variables from outside a flow (early on in a mabl plan), then passing them into an API test and regular test later on in the plan. The problem is if we need to adjust trained mabl steps in a regular mabl...

As a owner of multiples workspace within a company, I want to get all users in a workspace using the CLI or API, So that I can automatically maintain an users/mailing list of all mabl users within my company instead of doing it manually. Actually,...

As a mabl cli user I would like to get the test case ID's of the executed tests in the response. We integrated mabl into our CI/CD pipeline with the option to run cloud runs or a few local runs. We have also added a test rail integration to this. ...

Example: mabl test duplicate <test> --rename <string> --addToPlan <plan-id> I'd like to the ability to automate the process of creating a template, duplicating the test, and editing the duplicated test, and attaching it to a plan...