Overview
The Credit Consumption page is your billing dashboard that shows how many credits your organization uses for automated testing. Think of credits as the "currency" you spend when running tests - each test step costs a small amount, and this page helps you track and understand your usage patterns.
Prerequisites
You must have Admin role permissions in your organization.
Step-by-Step: How to check credit consumption
Open the Organizations Settings Menu
In the sidebar navigation, locate and click on the Organizations Settings option to access all the organizations settings.
Open the Subscription Menu
In the sidebar navigation, locate and click on the Subscription option to access credit consumption.
Navigate to Usage
Within the Subscription section, click on Usage.
Summary Cards (Top Metrics)
Metric | Description | Calculation |
| Total credits used during the current billing period | SUM(credits) for current billing period |
| Usage delta | ((Current - Previous) / Previous) × 100 |
| Total credits allocated per plan | Free Trial: 100 |
| Proportion of credits used relative to total allocated credits | (Period Credits Used / Total plan credits) × 100 |
| Avg. credit cost of a test (last 30 runs) | AVG(credits) over last 30 test runs |
Event types
Test Case Created — Generating the initial test case steps will create a credit consumption with Test Case Created event type.
Chat — Using Thunders AI to update test case steps or getting a suggestion will generate credit consumption with Chat event type.
Queued Run — Queuing test cases will generate credit consumption with Queued Run event type.
Debug Run — Running a test case in debug mode will generate credit consumption with Debug Run event type. The consumed credits for each action are shown when hovering on the action duration.
CI Run — Queuing test cases using the API will generate credit consumption with CI Run event type.
How credits are consumed
The following table shows the consumed credit in the different categories.
Category | Description | Credit Consumption |
Standard Actions | Most browser interactions (clicks, inputs, navigations, assertions, etc.) | 0.01 credit per action |
Multi-Action Steps | If a single step includes multiple actions (e.g., "Click and wait for navigation"), each action is billed separately. | Billed per action |
Visual Comparison Actions | When Thunders performs a visual or pixel-based comparison. | x10 multiplier |
Accessibility Actions | When a test is executed using the Accessibility Persona: actions that generate an accessibility report are billed at x10, while all other actions within the same test are billed normally. | x10 multiplier |
Discovery Steps | Thunders may explore your application automatically and generate sub-actions. Only the sub-actions are billed, not the discovery step itself. | Billed per sub-action |
Test Plan Generation | When you generate a Test Plan from a PRD, feature spec, or description. | 1 credit per Test Plan |
Average Credits/Test =
(SUM of credits for last 30 test runs) / 30Change vs Last Period =
((current - previous) / previous) * 100
Example
Test using Accessibility Persona:
5 standard actions → 5 × 0.01 = 0.05
1 visual comparison → 1 × 0.01 × 10 = 0.10
1 accessibility action that generates a report → 1 × 0.01 × 10 = 0.10
Total = 0.05 + 0.10 + 0.10 = 0.25 credits
Authenticated Profiles and scheduled runs
Two more things draw on your credits.
Authenticated Profiles are a billable entity, and appear in your consumption breakdown under that name. A Profile is charged whether it was recorded by hand or captured during a Test Run.
Scheduled runs consume credits exactly as runs a person starts do. It is worth checking this page after the first week of a new Schedule, because a rule that fires Hourly costs roughly twenty four times what the same Test Set costs once a day.