Pricing and Plans
TestDino Pricing
Explore TestDino pricing plans. Get transparent costs for playwright test reporting & analytics to help QA teams boost speed and reliability.
Free Plan
For individuals and hobby projects
5,000 executions/mo
Free, forever
- 1 team member
- 1 project
- 14-day data retention
- 21-day artifact retention
- AI classification
- GitHub integration
Pro Plan
For dev teams shipping
10,000 executions/mo
Everything in Free Plan, plus:
- 3 team members
- 3 projects
- 60-day data retention
- 10 GB attachment storage
- GitHub & GitLab integration
- Slack notifications
Team Plan
Engineering teams at scale
Everything in Pro Plan, plus:
- 30 team members
- 5 projects
- 365-day data retention
- 50 GB attachment storage
- Quality gates & CI checks
- Scheduled PDF reports
Enterprise
For large-scale operations
Custom volume
Everything in Team Plan, plus:
- Unlimited members
- Unlimited projects
- Custom retention
- Unlimited storage
- SSO & audit logs
- Dedicated support
Pricing calculator
Estimate your price
Enter your suite size and CI runs. We multiply them into total test results per month and recommend a plan as you type.
Run npx playwright test --list to count the tests in your suite.
Check your CI provider for how many times the suite runs each month.
One test result is one test case run. A single test across 3 browsers counts as 3 results, and each retry counts again.
Total test results per month
100 tests × 100 CI runs
Recommended plan
Includes 10,000 test results/mo. Save 20% with annual billing.
Start 14-day trialReduce test volume and save costs:
- Fail fast: stop a run on the first failure so broken builds don't burn test results.
- Re-run only the failed or flaky tests, not the whole suite.
- Tag high-risk tests and run them first to catch regressions before a full pass.
Pricing questions? Read the FAQ, the docs, or contact us.
Compare features across plans
Explore TestDino pricing and compare plans to find the best fit for your testing workflow. Review features, limits, and team options to choose the right plan.
Features20% FLAT OFF | Enterprise Custom | |||
|---|---|---|---|---|
| Test executions per month | 5,000 | 10,000 | 40,000 | Custom |
| Team members | 1 | 3 | 30 | Unlimited |
| Projects | 1 | 3 | 5 | Unlimited |
| Data retention | 14 days | 60 days | 365 days | Custom |
| Artifact retention | 21 days | 21 days | 21 days | Custom |
| Test case attachment storage | Not included | 10 GB | 50 GB | Unlimited |
| Custom Playwright reporter | ||||
| Screenshot capture | ||||
| Video recording storage | ||||
| Trace viewer integration | ||||
| Multi-browser results | ||||
| Sharding support | ||||
| Real-time result streaming | ||||
| Run history & trends | 14 days | 60 days | 365 days | Custom |
| Custom dashboards | ||||
| Environment tagging | ||||
| Stack trace viewer | ||||
| Error grouping | ||||
| DOM snapshot viewer | ||||
| Console log capture | ||||
| Network request logs | ||||
| Visual diff comparison | ||||
| AI failure classification | ||||
| AI-generated fix suggestions | ||||
| Failure pattern recognition | ||||
| Custom AI classification rules | ||||
| Flaky test detection | ||||
| Stability score per test | ||||
| Re-run only the failed tests | ||||
| Flake subcategorization | ||||
| Quarantine recommendations | ||||
| Pass/fail rate tracking | ||||
| Test duration trends | ||||
| CI cost tracking | ||||
| Custom metrics & KPIs | ||||
| Scheduled PDF reports | ||||
| CI/CD provider support | ||||
| Quality gates on PRs | ||||
| Branch-level configuration | ||||
| GitHub integration | ||||
| GitLab integration | ||||
| PR comment summaries | ||||
| Commit-linked results | ||||
| Manual test cases & suites | ||||
| Manual runs | ||||
| Exploratory sessions | ||||
| Releases | ||||
| Import & Export test cases | ||||
| Custom statuses & fields | ||||
| Manual test artifacts | 10 GB | 50 GB | Custom | |
| Slack App | ||||
| Slack Webhook | ||||
| Jira | ||||
| Jira Forge App | ||||
| Linear | ||||
| Asana | ||||
| monday | ||||
| Azure DevOps | ||||
| OpenClaw Bot | ||||
| n8n | ||||
| MCP Server for AI agents (Local & Remote) | ||||
| REST API | ||||
| Email alerts | ||||
| Slack notifications | ||||
| Microsoft Teams and other chat apps | ||||
| Custom notification templates and event triggers | ||||
| Webhook support | ||||
| SSO (OIDC) | ||||
| Audit logs | ||||
| Bring your own storage bucket | ||||
| Role-based access control | ||||
| SOC 2 Compliance | ||||
| Community Discord | ||||
| Email support | ||||
| Priority support | ||||
| Dedicated account manager | ||||
| Custom onboarding | ||||
Why teams choose TestDino
Built for Playwright teams who need clarity, speed, and confidence in every release.
80% Faster Fixes
AI surfaces why a test failed immediately – so you get ~2 more coding days each sprint.
Get Zero Flaky
No more false alarms – trust your pipeline and keep momentum unbroken.
2x Release Speed
Collaborative features and integrations that scale with your team.
Teams love what we built
See why developers choose TestDino to ship faster and debug smarter
We were on the default Playwright reporter, and it was tedious to dig through; half a day gone just triaging failures. The TestDino MCP changed that for us. I now run through the failures in minutes instead of devoting half a day to it, and pulling the latest runs straight through the MCP sped up bug triage drastically. AI failure classification and Slack reports do the rest. It's saved us weeks.
To triage failures, down from half a day
Saved across the team
Migrating to TestDino from Currents was an easy decision. The features are stronger, the cost is lower, and the interface makes debugging far less painful. Flaky test detection and AI failure classification have simplified debugging and reduced our CI costs by cutting down reruns and noisy failures.
Reduction in CI costs
Less time triaging failures
Over 30 flaky tests and no structured way to track them, just CI artifacts and morning guesswork. TestDino's "Most Flaky Tests" feature broke this pattern. We can see failure trends now and pull up video recordings of exactly what went wrong. The TestDino MCP server is the magic piece on top, I ask my Claude agent about a failure and it pulls full context from TestDino without switching tabs. We went from 30-something flaky tests down to 3 or 4.
Fewer flaky test reruns
Faster failure triage
What teams say on G2
Verified reviews from QA and engineering teams running Playwright in production.
AI-powered Playwright reporting for analyzing test failures
Analyzing failed Playwright runs in CI used to eat up a lot of our time. TestDino solved that with a centralized dashboard that pulls in screenshots, logs, and failure trends in one place. What's been most useful is the automatic grouping of failures, since instead of checking each failing test individually, we can immediately see patterns and likely causes. It's made triaging failures, and identifying which tests are simply flaky, dramatically faster.
Lead Software Engineer
Clear visibility into slow and flaky Playwright tests
We inherited an existing test suite without much context on how it was built, and TestDino gave us a real way to take ownership of it. It shows us clearly which tests are the slowest, the flakiest, and the ones failing most often, which has been essential for knowing where to focus our effort. It's given us the visibility to understand the current state of the code and steadily improve its reliability.
Senior QA Engineer at Penpot by Kaleidos
Comprehensive dashboard for QA automation
I monitor everything my tests do, from the full list of tests to detailed error screenshots. The GitHub integration is smooth, so commit hashes, CI runs, and HTML reports open straight from the dashboard. I use TestDino almost every day, and it has improved the quality of our automation code.
Lead QA Automation Engineer
Easy and effective test visualization
Before TestDino, we were manually digging through raw reports to catch flaky and failing tests, and it took a lot of time. Now everything is stored and analyzed automatically, with no extra setup layers needed. The installation itself was simple, and it's made spotting flaky tests a much faster, cleaner process for our team.
Test Automation Team Lead
Effortless reporting with insightful analytics
TestDino gives us a clean dashboard and reporting setup that's genuinely easy to work with, packed with useful analytics. It's effectively replaced what used to be a custom Power BI dashboard for us, while being far simpler to set up and maintain. The platform makes it easy to centralize and visualize results, so tracking trends and understanding failures no longer takes extra effort.
QA Automation Engineer
Clear test results and faster debugging
Reviewing our Playwright test results used to mean sifting through raw output to figure out what actually broke. TestDino changed that by giving us a clear, structured view of every run. Failed tests are easy to spot right away, and debugging that used to take real effort now moves a lot faster.
Automation Engineer
FAQs
Each individual test case (spec) that runs counts as one execution. If you run 50 tests across 3 browsers, that's 150 executions. Retries also count as separate executions.