Every team has failure patterns that are specific to their application: a login failure, a data issue, a test account that's out of state. Until now, you had to map those into one of mabl's default failure reasons, where a precise problem like an expired credential disappeared into a broad bucket like "Environment issue." Now you can create your own custom failure reasons that match how your team actually thinks about failures.
Custom failure reasons make it easier to:
- Identify patterns: distinguish an expired credential from an unstable staging server from a third-party outage, instead of lumping them together.
- Eliminate noise: separate known, expected failures from actionable regressions so they stop skewing your pass rate.
- Report in your own language: track failure trends using the terms your stakeholders already understand
Try it out
A workspace can have up to 50 custom failure reasons. Workspace owners can manage them in Configuration > Failure reasons in the mabl app:
- Create new custom failure reasons - add a display name, an optional description that gives your team context, and, when Advanced AI is enabled, agent guidelines that tell the mabl agent when to assign the reason automatically. See Write agent guidelines for custom failure reasons for how to write effective ones.
- Rename failure reasons - change the display name at any time, and historical references update automatically.
- Disable failure reasons - if you want to discontinue a specific failure reason, disable it to hide it from the failure reason picker while preserving the data already classified with it.
mabl's default failure reasons remain available and can't be renamed or deleted.
Mix of default and custom failure reasons on the coverage dashboard
Once tests are assigned with a custom failure reason, they're available everywhere your failure data already lives, including on the results page, the coverage overview dashboard chart, CSV exports, test run summaries from the mabl API, and in the _run_categorization BigQuery export table.
Learn more
To learn more about classifying failures, see failure reasons.