For a high-level overview of usage in your workspace, including consumption of cloud runs and test authoring activity, check out the usage page: Settings > Usage. This article explains key concepts for reviewing the usage page.
mabl Core plans only
This article outlines the usage page for organizations that purchased a mabl Core plan. If your organization purchased a legacy pricing plan (startup, growth, or enterprise), the usage page shows separate charts with cumulative and predicted usage by each test type, which may include browser, API, accessibility, and performance.
If your team works in multiple workspaces, you can request access to a company dashboard to review usage across all workspaces in your account.
Credits
Credits are the unit of measurement for all tests executed in the cloud. The usage page shows the total number of credits used compared to the total number of allocated credits for your workspace.
Local and CI runs do not consume credits.
Test run to credit conversion
Different types of tests consume a different amount of credits. Refer to the following table for more details:
| Type of run | Credits consumed |
|---|---|
| Browser cloud run - desktop or mobile web | 1 credit |
| 1.5 credits with GenAI Assertions | |
| Mobile cloud run | 5 credits |
| 5.5 credits with GenAI Assertions | |
| API cloud run | 0.1 credit |
| Performance run* | 1 credit per concurrent user for 15 minutes of API load |
| 2 credits per concurrent user for 15 minutes of browser load | |
| Visual test run | 1 credit |
| Playwright runs with GenAI Assertions** | 0.5 credits for every 6 GenAI Assertions |
*To determine the number of credits consumed for a performance test run, multiply the number of billable VUH shown on the test output page by 4. Billable VUH represents the total number of billable virtual user hours (VUH), billed in 15 minutes.
**GenAI Assertions executed in Playwright consume mabl credits at a rate of 0.5 credits per 6 GenAI Assertions. Credit consumption is calculated on a daily basis and rounded up to the nearest half credit.
Mobile cloud training doesn't consume credits
Although mobile cloud training sessions use cloud resources, the are not test executions and do not consume credits.
Workspace users
The usage page tracks test authoring activity by user and organizes users into two groups:
- Automators: users with at least 30 test authoring activities during a given month.
- Participants: all other users added to your mabl account with 0-29 test authoring activities for the month.
Test authoring activities
Test authoring activities include the following:
- Creating a new test
- Saving a new version of an existing test
- Duplicating a test
- Deleting a test
- Restoring a deleted test from the activity feed
Test authoring activities do not include any changes to the following:
- Test metadata, including name, description, labels, device settings, DataTables, shared variables, and test case IDs
- Applications
- Environments
- Credentials
- Branches
- File uploads
- Flows
- Plans
- Snippets
- Permanent email addresses
- DataTables
Allocating users
The usage page also shows the number of automators and participants allocated to the account. For example, this workspace is part of an account that is allocated nine automators and 45 participants.
Measuring workspace user activity
In mabl, you can invite an unlimited number of users to your workspace. Exceeding the allocated number of users does not prevent you from inviting new users.
Similarly, if your workspace exceeds the total number of allocated automators for your account, mabl will not prevent participants from becoming automators over the course of the month.
If you expect that your workspace will have significantly more users than listed for your account, we recommend reaching out to your mabl customer success manager (CSM) on next steps.
Usage measurement
Depending on the type of contract that your company purchased, credits are allocated on an annual or monthly basis. You can find your account's usage measurement and contract duration in the Workspace users section.
Unused credits at the end of the configured billing period do not roll over to the next period.