Feature Requests & Ideas

As a user, I want to have the ability to lock or checkout flows so that other user will not be able to overwrite the flow the I am updating. I have several instances where the latest update in the flow was overwritten by other users since the...

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

As QA, I want to be able filter the list of journeys, so that I can easily see what we have missed or duplicate on the journeys we have created. Right now we have 288 journeys, it's kind of hard to filter which journeys doesn't have labels or desc...

It would be great if I could reuse a flow, but change the variable without effecting the other tests using this flow. The variables should be test specific, but flows should be universal. I know this can easily be resolved using data tables, ...

I have read the documentation but it seams like scheduled plans always run the master test. I will like to schedule a plan to run a manitained test in a branch every day. This is useful during a sprint where the tests will be run on different vers...

As a Mabl test writer I want to be able to loop more than 100 times So that I can wait for a API response that may take up to 8 hours to respond.

We want to implement a SDLC that includes per-branch deploys to AWS where each developer's branch is deployed to a unique instance that can be tested in isolation. In this use case we will have a URL like this:`https://[branch-name].[main-applica...