The mabl API now includes endpoints for reviewing test execution activity at the workspace and account level! Use these new endpoints in your custom reporting workflows to provide more visibility into how your team is testing in mabl:
- Get test run count
- Get execution seconds
- Get max test run concurrency
- Building ROI dashboards with this data
Before you start
Test activity endpoints require a company-scoped "Reporting" API key. Account admins can create one from the company dashboard:
Open the API key tab from the left navigation and create a "Reporting" API key.
To support the account-level endpoints, we've also added a new way to obtain account IDs from the account dashboard. The account dropdown is accessible from the Value, Quality, Engagement, and Billing tabs:
Get test run count
Retrieve the total number of test runs and their statuses - passed and failed/terminated - for a workspace or an account, sorted into daily, weekly, or monthly buckets:
Use this endpoint to track your team's test activity over time, and monitor the reliability of tests by calculating the pass rate. Add an optional group_by filter to compare test runs and results across different applications and plans, or scope the results to a specific app, plan, or workspace.
Get execution seconds
Retrieve the total execution time by day, week, or month for a workspace or account, sorted into daily, weekly, or monthly buckets:
Use this endpoint to understand test run duration across applications, plans, and test types. For example, include the optional group_by filter to get execution time by plan to surface long-running test suites that contribute to bottlenecks in your CI workflow.
Execution time is measured from the moment a run starts execution to the moment it completes. It does not include time spent in a queued status waiting for a runner.
Get max test run concurrency
Get the daily maximum number of simultaneously executing test runs in a workspace or account, along with the workspace's configured test run concurrency limit:
Use this endpoint to monitor how close your workspace is to its concurrency limit. Analyze the max test run concurrency alongside the total daily test run count to determine whether tests are running more or less continuously throughout the day or hitting your development pipeline in large, discrete bursts.
Building ROI dashboards with this data
If you are routing this API data into a business intelligence (BI) tool like Tableau, Microsoft Power BI, Domo, or Looker Studio, you can use these common formulas to translate raw test activity into clear business and financial value:
1. Manual hours reclaimed
Quantify how much manual QA effort your team avoided through automation.
Formula: (total test run count * average manual test minutes) / 60
2. Cost per test run
Prove to finance teams how automation drives down the marginal cost of QA as deployment frequency scales.
Formula: total mabl subscription cost / total test run count
3. Parallelization efficiency multiplier
Demonstrate how effectively your team is using concurrent testing capacity to accelerate developer feedback loops without increasing total pipeline run time.
Formula: (total test run count * average execution seconds) / actual pipeline run time