Feature Requests & Ideas

Tests failures go directly into Jira without any manual input

I have one test that is currently set up to run against three different environments (QA, UAT, Production) When this test runs I would like the results to be posted in different slack channels based on the environment it is run in. So post the res...

As a QA Engineer I would like to be able to integrate mabl with TeamCity so that we can run mabl tests on deployment event in TeamCity.

As a User I want to have mabl results in a format that our Testing Management Tool can import https://qmetrysupport.atlassian.net/wiki/spaces/QTMP/overview Supported Automation Frameworks: Cucumber TestNG JUnit QAS HP UFT

As a user, I want to be able to see who executed a cloud run in my slack notification, so I can know if it's a scheduled run or if someone in my organization kicked off that test.

From the "Assertions Failed" page in mabl, would like to be able to create a work item in Azure DevOps so that we can easily import mabl logs, fix bugs, and keep track of bug-related stats in Azure DevOps. This would be similar to the "Jira issue ...

As an engineer In order to save time and journey executions I should be able to rerun failed tests from github checks Scenario: Rerun a failed test because of poor test design Given I have a mabl journey that was poorly designed And this journey i...

When Jenkins run fails, devs have no info about the failed test (only that it failed). To help them, mabl should send link to failed run to Jenkins, so they could find some info about the failed test.

We're documenting flows in our JIRA and would like to link the mabl flows to our JIRA tickets for them, similar to how we can link Tests/Plans/Runs to JIRA already.

When a ticket is already created for a bug found by the test suite, I would like to be able to link the ticket to the test run. Currently I can only create a new JIRA