Evaluation Tokens
Learn how Evaluation Tokens work in Verex and how they're used to estimate and run your automated tests.
What Are Evaluation Tokens?
Evaluation Tokens are the standard unit of measurement for test execution in Verex. Each token represents the cost of evaluating a standard browser-based test step. This makes test execution predictable and scalable regardless of test complexity.
Tokens are consumed whenever a test is run—either individually or as part of a suite. The more complex or longer the test, the more tokens it may require.
Why Use Tokens?
- Uniform Pricing: Tokens abstract away test complexity, making cost predictable across different types of tests.
- Flexible Allocation: Use your tokens however you like—across simple or complex end-to-end browser tests.
- Predictable Budgeting: Know how many tests you can run each month based on your plan’s token allocation.
Estimating Token Usage
While we can’t determine the exact number of tokens required before a test begins, here’s a general guide:
| Test Type | Estimated Tokens |
|---|---|
| Simple test | ~4 tokens |
| Average complexity | ~7 tokens |
| Complex workflow | ~10+ tokens |
Actual usage may vary depending on your app’s structure and the number of steps in your test.
Plan-Based Allocation
Every paid Verex plan comes with a set number of Evaluation Tokens that reset monthly. The Free plan includes a one-time credit upon signup, which lets you try out test execution before upgrading.
Only the first organization created under an account will receive this one-time credit. Any additional organizations must upgrade to a paid plan to access tokens.
To view plan details and token allocations, visit our Pricing page.
When Are Tokens Consumed?
- Tokens are consumed once a test begins running.
- Each test run always consumes at least 1 token, even if the test is stopped immediately.
- Evaluation Tokens are non-refundable for partially completed runs.