Feature Requests & Ideas

As a customer of mabl I would like our solutions to trigger and view the results of mabl plan runs via Azure DevOps. Similar to how existing integrations made for Jenkins and Bamboo uses this. Link: https://docs.microsoft.com/en-us/azure/devops/e...

As a test engineer I want to be able to reuse variables I have created in previous journeys in the journey i am currently recording in order to avoid duplication of work and speed up test creation Example use case While recording a journey, i crea...

Allowing the use of only starting a second journey once the previous has completed would make testing our app immensely easier.

Currently, mabl allows for the ability to curl the API to kick-off a Journey with a given label. It would be great if optional parameters were recognized (sent with the curl body), e.g. a git commit SHA. For dev-ops purposes this is ideal to track...

As a QA manager, I would like to be able to reuse a Flow multiple times inside a Journey, so that we can easily navigate back and forth between app URLs.

We are planning to automate our application with mabl. However as we progress with the test coverage, I am assuming the number of javascript snippets wil increase with time. So when I want to reuse any javascript snippet, it will be difficult for ...

As a test engineer i want to the mabl trainer that appears in the dev console to be spread across the screen and fill all available space so the steps are easier to read and the buttons are always visible. Also if the console is open the trainer s...

When writing software with code the standard practice is to comment as much as possible.The mabl Trainer does a great job at explaining 'what' it's doing (e.g. assert "search" of current URL contains "Test"). But we would like the ability to add c...

I would like journeys to be stored in a version control system. When making changes it logs which user made the change with data/time. Then having the full history of changes with what was changed. With the ability to roll back to an earlier version.

As a user, I would like to trigger an API call as part of my journey run. Some users have expressed interest in making API calls as part of their journeys in order to trigger events within their applications, set values for variables used elsewhe...