Skip to main content
TestDino bills based on monthly test executions. This page covers how usage is measured, how billing cycles work, and how to evaluate which plan fits your team.

Quick Reference

TopicDescription
How Usage Is MeasuredWhat counts as a test execution
Choosing the Right PlanEstimate usage and pick a plan
Billing CyclesMonthly, annual, and trial billing
What Happens at the LimitBehavior when executions run out
Upgrading and DowngradingChanging plans mid-cycle
CancellationEnding your subscription
Invoices and PaymentPayment methods and invoice access
FAQCommon billing questions

How Usage Is Measured

TestDino meters usage by test executions. One test execution is one test case (test() or it() block) that runs and reports a result to TestDino via the reporter.
  • Each test that runs and reports a result (pass, fail, or flaky)
  • A flaky test counts as one execution regardless of how many retries it took
  • Reruns of the same test within a single run count as one execution

Example

A test suite with 200 test cases. 5 tests are skipped. 3 tests are flaky and each retried 3 times.
Executions counted: 195 (200 total - 5 skipped)
Retries: not counted separately
Attachments: not counted
The 3 flaky tests each count as 1 execution, not 3.

Choosing the Right Plan

Estimate your monthly executions:
Monthly executions = (number of test cases) x (CI runs per month)
ScenarioTestsCI FrequencyMonthly ExecutionsRecommended Plan
Solo developer1002x/day6,000Professional
Small team3003x/day27,000Team
Growing team5004x/day60,000Team
Large team1,000+5x/day150,000+Enterprise

Plan limits at a glance

Community (Free)ProfessionalTeamEnterprise
Monthly priceFree$49/mo$99/moCustom
Annual priceFree$39/mo, billed yearly$79/mo, billed yearlyCustom
Monthly executions5,00025,00075,000Unlimited
Team members1530Unlimited
Projects135Unlimited
Data retention14 days60 days365 daysCustom
Artifact storage1 GB5 GB10 GBUnlimited
Annual plans save approximately 20% compared to monthly billing.

Billing Cycles

Subscriptions renew on the same date each month. Usage resets at the start of each billing period.

What Happens at the Limit

When your organization reaches the monthly execution limit:
1

Test submissions blocked

New test results are blocked for the remainder of the billing period.
2

Existing data stays accessible

Dashboards, reports, and historical test data remain available.
3

Usage notifications

Email notifications are sent at 50%, 75%, 90%, and 100% usage thresholds.
To continue submitting tests, upgrade to a higher plan. The upgrade takes effect immediately.

Upgrading and Downgrading

Upgrade at any time from Billing & Usage > Change Plan.
  • The new plan takes effect immediately
  • Usage limits and feature access update instantly
  • If upgrading from a trial, the trial ends and billing begins
Plan order: Community (Free) > Professional > Team > Enterprise

Cancellation

Cancel your subscription from Billing & Usage > Cancel Subscription.
  • Cancellation can be immediate or at end of billing period
  • The organization reverts to the free Community plan after cancellation
  • To resume service after cancellation, start a new subscription

Invoices and Payment

Payment methods

TestDino processes payments through Razorpay. Accepted methods:
Method
Credit and debit cardsVisa, Mastercard, RuPay
Net bankingAll major banks
UPIGoogle Pay, PhonePe, etc.
Digital walletsSupported wallets via Razorpay
Bank transferDirect bank transfer
No card data is stored by TestDino.

Invoices

Access all invoices from Billing & Usage > Invoices. Each invoice shows the plan, billing period, amount, and payment status.

Billing contacts

Configure who receives billing notifications in Billing & Usage > Billing Emails. Notifications include payment confirmations, failure alerts, invoice receipts, and usage threshold alerts.
Billing notifications are separate from operational notifications. Operational notifications (test failures, alerts) are sent to members with Admin role by default.

FAQ

Multiply your test count by the number of CI runs per month. For example, 300 tests running 3 times per day is 27,000 executions/month, which fits the Team plan (75,000 limit).
No. A flaky test counts as one execution regardless of retry attempts. Retries within the same run do not add to the count.
No. Attachment volume does not affect execution count. Artifact storage is tracked separately and included in your plan.
New artifacts are rejected when storage is full. Existing artifacts remain accessible. Storage is freed automatically when data expires per your plan’s retention period.
Yes. Upgrades take effect immediately with updated limits. Downgrades take effect at the end of the current billing period.
The Community plan includes flaky test detection, quality metrics, failure categorization, and a dashboard summary. It does not include AI insights, PR features, Slack/Jira integrations, or team management.
Contact support@testdino.com to switch billing cycles. Changes take effect at the end of the current billing period.
TestDino retries the payment automatically. If the payment remains unpaid past the due date, the subscription is marked past due. Resolve payment issues in Billing & Usage to restore service.
Yes. Contact support@testdino.com to pause your subscription. Features are inactive while paused. Resume at any time.
Organization owners and members with the org_billing role can access billing settings and manage subscriptions.
Monitor usage, limits, invoices, and retention.