2025/07/21 - Results analysis now available from the mabl API

Ever wish you could get more insight on failed runs from the mabl API? Now you can! We’re happy to share that results analysis is now available for failed tests and plan runs via mabl’s reporting API! Previously, if you wanted to generate a failure analysis, you had to open the output page for a failed test or plan run in the mabl app. Now, mabl automatically generates a failure analysis when a test or plan fails. 

To support users with custom reporting workflows, we included failure analyses in the following API endpoints:

• Get test run summary
• Get plan run summary

Teams can use this information to enhance their existing reporting workflows and give their organization more visibility into why tests or plans failed.

Check it out

When you make a call to the test run or plan run summary endpoint, look for the "failure_analysis" object in the response. Included in the failure analysis is a "headline", "summary", and "failure_category_id" . 

Here’s an example:

"failure_analysis": {
  "headline": "The test failed because the \"Input\" link was not found on the page.",
  "summary": "The test failed because the link to \"https://storage.googleapis.com/public-dev-test-lab/input/index.html\" was not found on the page. Looking at the failing step's logs, the test is on \"https://sandbox.mabl.com/\" while it is trying to click on the \"Input\" link. There may have been an issue navigating to the starting URL specified in the test configuration, or the application may have experienced a regression in which the \"Input\" link is no longer present on the page. I suggest reviewing the value of the variable \"app.url\" to ensure that it is set correctly.",
  "failure_category_id": "regression"
}