Gaffer vs TestDino: Two Bets on Test Reporting

Gaffer and TestDino both host and analyze CI test reports, and they bet on different things. TestDino goes deep on Playwright: inline trace, DOM, and network debugging, a built-in test-case management layer, and an agent-writable MCP server. Gaffer stays framework-agnostic and prices on storage instead of executions or seats. The clearest split is the bill. TestDino’s tiers gate on a monthly execution quota and a hard user cap (1 user on Free, 3 on Pro, 30 on Team), while Gaffer bills on stored bytes with unlimited users on every tier. A 35-person team running roughly 100,000 Playwright executions a month clears TestDino’s Team tier on two axes at once, the 40,000-execution quota and the 30-seat cap. On Gaffer’s $49/month Team plan users are never capped and executions are not counted. The bill moves only if retained reports pass 50 GB, at $0.50/GB/month, and more runs mean more stored bytes.

What Gaffer and TestDino Actually Are

TestDino is a Playwright-first test reporting and analytics platform. It ingests Playwright output and adds inline debugging (trace, DOM snapshots, network logs), root-cause failure categorization, test-case management, and an MCP server that coding agents can both read from and write to. The full feature reference is in TestDino’s docs.

Gaffer hosts and analyzes test reports from many frameworks. It ingests JUnit XML, CTRF, Jest and Vitest JSON, native Playwright JSON, and TRX/.NET, plus four coverage formats, then provides flaky detection, pass-rate trends, and failure clustering with no setup beyond the upload step. Clusters the model can place with at least medium confidence also get an AI root-cause category. It is a reporting and analytics surface, not a test-management tool.

Where TestDino Is Stronger

If your stack is Playwright and you want depth over breadth, TestDino has real advantages Gaffer does not match:

• Playwright-native inline debugging: trace, DOM snapshots, and network logs attached to each failure.
• Write-capable MCP: its public MCP server (testdino-hq/testdino-mcp) exposes 58 tools, including mutations like create_manual_test_case and create_release, so a coding agent can manage test artifacts directly.
• Built-in test-case management: suites, cycles, and imports from TestRail or CSV.
• Failed-only reruns and flakiness merge-gates: rerun only the failures, and block merges on a flaky signal.
• Published compliance posture: TestDino publicly claims SOC 2 Type II and ISO 27001 certification and GDPR compliance on its security page. Gaffer claims no certifications, which is a real gap for teams with a security-review checklist.

Where Gaffer Is Stronger

Gaffer’s advantages are pricing shape and framework breadth, plus a smaller surface to adopt.

• Storage-based pricing with unlimited users: no per-tier execution quota and no seat cap. Everyone on the team can have an account on any tier, including Free.
• Multi-framework reporting: one dashboard for JUnit XML, CTRF, Jest, Vitest, native Playwright JSON, and TRX/.NET, which transitively covers pytest, Go, Cypress, and anything that emits JUnit XML or CTRF. See multiple test frameworks.
• Coverage tracking from any stack: LCOV, Cobertura, JaCoCo and Clover parsed and trended in the same view as pass rate. TestDino lists a code coverage view too, without naming formats.
• No test-management layer to adopt: Gaffer hosts reports and runs analytics. There is nothing to configure beyond a CI upload step.

Pricing: Execution Quotas vs Metered Storage

The two products meter different things. TestDino charges a monthly subscription, gates each tier on an execution quota and a hard user cap, and bills overage on executions. Gaffer charges a monthly subscription, bills overage only on stored bytes, and never caps users.

TestDino counts each test once per browser or Playwright project: a single test run across three browsers counts as three executions, while retries in the same run do not count again. Cross-browser matrices consume the quota quickly. Gaffer counts nothing per-execution. It bills on stored bytes, with $0.50/GB/month overage on Pro and Team, and puts no cap on users on any tier including Free.

Which is cheaper depends on the shape of your workload. A small Playwright-only team may fit comfortably inside TestDino’s Free or Pro tier. A CI-heavy team, or one past 30 people, usually pays less on Gaffer if its retained reports stay small: headcount does not change the Gaffer bill and executions are not counted, but more runs mean more stored bytes, billed at $0.50/GB/month past the plan’s included storage. Above its quota, TestDino blocks new results until the cycle resets, you upgrade, or you add executions at $3 per 1,000 on Pro and Team.

Assume 100,000 executions a month, made up of 2,000 runs at 50 executions each, from a team smaller than the one above, within TestDino’s 30-seat cap. At 90-day retention, Gaffer keeps 6,000 reports.

Gaffer meters storage, so report size decides which row you land in. Measure your own before trusting either one. The 2 MB figure has evidence behind it: a real Gaffer customer with 7 projects uploads more than 1,100 reports a week on Pro, which is more than 4,700 retained reports inside 10 GB at 30-day retention, or under about 2.2 MB per report, with $0 overage. Those are JUnit XML reports. The 50 MB figure is an illustrative assumption for HTML reports with traces.

Pricing Comparison

TestDino figures are from testdino.com/pricing, checked 2026-11-05.

An execution on TestDino is one test in one browser or Playwright project, so cross-browser runs multiply against the quota. Gaffer’s bill moves only with stored bytes.

Feature Comparison

Both MCP servers are real. TestDino’s is write-capable so an agent can create test cases and releases. Gaffer’s is code-mode analytics: 16 read functions and one write, upload_test_results, which adds new results. There are no test-case or release mutations, a deliberate choice that matches Gaffer not being a test-management tool: query your results, do not manage test cases from the editor.

When to Use TestDino

TestDino is the better fit if:

• Your suite is Playwright and you want inline trace, DOM, and network debugging on every failure.
• You want a coding agent that can write test artifacts (manual test cases, releases) through MCP, beyond reading metrics.
• You need built-in test-case management: suites, cycles, and imports from TestRail or CSV.
• Failed-only reruns and flakiness merge-gates are part of your CI workflow.
• Your security review needs a vendor that publishes SOC 2 Type II and ISO 27001 claims.
• Your team is small enough to sit inside the 1 / 3 / 30 user caps and the per-tier execution quota.

When to Use Gaffer

Teams shopping for a TestDino alternative usually hit one of two walls first: the seat cap or the execution quota. Gaffer is the better fit if:

• You run more than one test framework and want them in a single dashboard.
• Your team is at or past 30 people, or growing, and a seat cap is the binding constraint.
• Your CI produces high execution volume (cross-browser matrices, frequent runs) and you would rather watch stored bytes than an execution quota.
• You want LCOV, Cobertura, JaCoCo or Clover coverage trended next to pass rate for the same upload.
• You want a plain hosted-report and analytics surface with no test-management layer to adopt.
• You want MCP analytics for agentic CI where the only thing an agent can write is a new upload of test results.

Using Both

You can run both without a migration. Standard report formats are portable, so a common split is to upload Playwright output to TestDino for deep, inline debugging and send JUnit XML or CTRF to Gaffer for multi-framework hosting and analytics. Neither side requires a big-bang cutover, and JUnit XML and CTRF are first-class inputs on Gaffer, so the integration work is one more upload step in CI.

FAQ

Is Gaffer or TestDino cheaper?

It depends on the shape of your workload. TestDino gates each tier on a monthly execution quota and a hard user cap (1 user on Free, 3 on Pro, 30 on Team), while Gaffer bills on storage with unlimited users. A CI-heavy team, or one larger than 30 people, usually pays less on Gaffer if its retained reports stay small: headcount does not change the Gaffer bill and executions are not counted, but more runs mean more stored bytes, billed at $0.50/GB/month past the plan’s included storage. A small Playwright-only team may fit inside TestDino’s free or Pro tier.

Does Gaffer support Playwright?

Yes. Gaffer ingests native Playwright JSON, and also Jest, Vitest, pytest, Go, Cypress, and .NET through JUnit XML, CTRF, and native JSON formats, plus coverage formats. TestDino is Playwright-first; its only other documented reporter is for TesterArmy’s e2e framework.

Does Gaffer have test-case management?

No, by design. Gaffer hosts and analyzes test results; it is not a test-management tool and has no suites, cycles, or manual test plans. TestDino includes test-case management with suites, cycles, and imports from TestRail or CSV.

Is TestDino only for Playwright?

TestDino is Playwright-first; its only other documented reporter is for TesterArmy’s e2e framework, and its docs say not to use it for Cypress, Jest or other frameworks. Its inline trace, DOM, and network debugging are built on Playwright’s own artifacts. If you run multiple frameworks and want them in one dashboard, Gaffer’s multi-framework ingestion is the better fit.

Can I use both Gaffer and TestDino?

Yes. Standard report formats are portable, so a team can upload Playwright output to TestDino for deep debugging and send JUnit XML or CTRF to Gaffer for multi-framework hosting and analytics. There is no big-bang migration required in either direction.

Other Comparisons

Evaluating more tools? See how Gaffer compares to Currents.dev, Allure, ReportPortal, and Codecov Test Analytics. For a wider view, see 10 test reporting tools compared.

Try It

Gaffer’s free tier includes 500 MB storage, 7-day retention, and unlimited users. Enough to measure your own report size before trusting the table above.