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.
- Credit consumption
- Workspace users - automators vs. participants
- Usage measurement - monthly or annual
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
All workspaces are allocated a certain amount of credits for running tests. The usage page in the mabl app - Settings > Usage - displays the total number of credits used along with the total number allocated for your workspace.
Calculating credit consumption
Credit consumption in mabl is a reflection of the amount of resources a test run consumes. The following table defines how many credits are consumed for different test types:
| Type of run | Credits consumed |
|---|---|
| Local mabl runs | 0 credits |
| mabl runs in your CI environment | 0 credits |
| Browser cloud run - desktop or mobile web |
Without GenAI Assertions: 1 credit With GenAI Assertions: 1.5 credits |
| Mobile cloud run |
Without GenAI Assertions: 5 credits With GenAI Assertions: 5.5 credits |
| API cloud run | 0.1 credit |
| Visual test run | 1 credit |
| Performance run |
Credit consumption is based on duration, which is rounded up to the nearest 15-minute increment:
To determine the number of credits consumed, 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 minute increments. |
| Local Playwright runs |
Without GenAI Assertions: 0 credits With GenAI Assertions: 0.5 credits for every 6 GenAI Assertions. Credit consumption is calculated on a daily basis and rounded up to the nearest half-credit increment. |
Mobile cloud training doesn't consume credits
Although mobile cloud training sessions use cloud resources, they 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.
Workspace users indicates the total number of automators and participants allocated at the account level. This allocation represents the agreed-upon scope of usage defined in your current subscription. For each user, test authoring activities are aggregated across all the workspaces they belong to. For example, if a user does 24 test authoring activities in one workspace and 12 in another workspace, the user is counted as an automator.
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
Tracking and allocating users
The status of workspace users as automators and participants is defined and tracked on a monthly basis based on test authoring activities. These roles are fluid. While some users may maintain a consistent level of test authoring activities from month to month, other users may switch between automator and participant depending on their monthly workload.
For example, this workspace is part of an account that is allocated nine automators and 45 participants. In this particular month, there are six automators and 20 participants. The next month, all users will start out as participants and, when a user performs 30 or more test authoring activities for that month, they become an automator.
Measuring workspace user activity
Exceeding the allocated number of users does not prevent you from inviting new users. You can invite an unlimited number of users to your workspace. 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) to discuss aligning your current allocation with your expected usage patterns.
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.