Skip to main content
Common questions about TestDino setup, streaming, API keys, test runs, integrations, and billing.

​
Getting Started

TestDino is a Playwright test reporting and management platform with MCP support. Add @testdino/playwright to your config, set TESTDINO_TOKEN, and run npx playwright test. Results stream during the run and link to branches and PRs.Full walkthrough: Getting Started.
  1. Create an organization and project
  2. Create an API key
  3. Install @testdino/playwright and add it to your Playwright config
  4. Set TESTDINO_TOKEN and run npx playwright test
See Getting Started and Generate API Keys.
No. Add @testdino/playwright to the reporter array and set TESTDINO_TOKEN. No custom annotations or framework changes required.
The reporter streams results and, when Playwright produces them, traces, videos, and screenshots. Control capture with use.trace, use.video, and use.screenshot in Playwright config. Setup: Node.js CLI.

​
Setup and Configuration

Playwright reporters cover a single run. TestDino adds cross-run analytics, error grouping, Git and PR context, integrations, and historical stability. Product overview: Overview.
JavaScript and TypeScript via @testdino/playwright. TestDino is Playwright-only.
Install @testdino/playwright, add it to the reporter array, set TESTDINO_TOKEN, and run npx playwright test. Or run npx tdpw test -t "$TESTDINO_TOKEN" --server-url https://reporter.testdino.com without editing config.Learn more in Getting Started and the Node.js CLI reference.
Yes. Each package streams with its own TESTDINO_TOKEN. Use separate TestDino projects for isolated analytics, or one project for unified reporting.
Yes. TestDino reads results from the run, not source code. For GitHub PR comments and checks, install the TestDino app on the repo where tests run.
No. The dashboard, streaming, and integrations work without MCP. MCP is for querying live data from Cursor, Claude, or ChatGPT. See MCP Overview.

​
API Keys and Authentication

Create keys in Project Settings → API Keys. Copy the secret once and store it as TESTDINO_TOKEN. Full steps: Generate API Keys.
  1. Create a new key in Project Settings → API Keys
  2. Update CI secrets with the new key
  3. Run tests once to confirm streaming
  4. Delete the old key
Confirm TESTDINO_TOKEN (streaming) or a td_pat_ PAT (Public API / MCP), network access, and the correct project. For run IDs, confirm the run exists in that project. Symptom fixes: Troubleshooting.

​
Test Runs and Results

Store the key as a secret named TESTDINO_TOKEN and expose it to the test step. Provider guides: CI Setup.
Check TESTDINO_TOKEN, that @testdino/playwright is in the reporter array, that the token matches the project, and CI logs for TestDino errors. Run npx tdpw test --debug for streaming logs. Full checklist: Troubleshooting.
Glossary: Glossary.
Failed, flaky, and skipped tests grouped by cause, plus detailed analysis with filters. See Run Summary.
Open a failed or flaky test from Run Summary, or use the Trace tab on Test Case Details. Guide: Trace Viewer.
Traces are interactive (actions, network, console, DOM). Videos are screen recordings. Use video for a quick look; use the trace for debugging. See Visual Evidence.
Yes. Filter on Test Runs and group by message on Errors.
Confirm GitHub is connected, the run includes commit SHA metadata, and an open PR exists for the branch. See GitHub integration and Troubleshooting.

​
Flakiness and Test Health

Within a run: fail then pass on retry. Across runs: inconsistent outcomes without code changes. Stability is (Passed ÷ Total Runs) × 100. Root causes: Timing, Environment, Network, Assertion, or Other. Guide: Flaky Test Detection.
Test Case History shows stability %, last status tiles, and an execution history table scoped to the current branch.

​
Integrations

CI/CD (GitHub, GitLab, Azure DevOps, TeamCity), issue tracking (Jira, Linear, Asana, monday), and Slack. Full list: Integrations.
Install the TestDino GitHub App, then configure comments and CI checks in GitHub settings.
Pass rate, mandatory tags, flaky handling, and environment overrides. Configure these in GitHub Status Checks.
A mandatory-tag test failed, flaky handling is Strict, or an environment override is stricter. See GitHub Status Checks.
Connect the integration in Project Settings, open a failed test case, and use Raise Bug or Raise Issue. Guides: Jira, Linear.

​
Environment Mapping and Branch Management

It maps Git branches to environments (Production, Staging, Dev) so runs, Slack channels, and CI checks group correctly. Configure under Project Settings → Branch Mapping. Guide: Environment Mapping.
TestDino reads the branch from git metadata and applies the matching pattern. Pattern rules: Environment Mapping.
The run has no environment label and may drop out of environment filters. It still appears in the unfiltered Test Runs list. Add a matching pattern or catch-all. See Best practices.

​
Organizations and Projects

An organization holds team, users, billing, and settings. A project is one suite or app with its own runs, keys, and integrations. Hierarchy: Organization → Projects → Test Runs. See Organization Overview and Project Overview.
Open Users & Roles, invite by email, and assign a role.
Owner, Administrator, Member, Billing Manager, and Viewer. Permission matrix: Users & Roles.

​
Billing and Pricing

Plans are based on test executions and user or project limits. Usage is monthly; retries count. Track usage under Billing & Usage. See Pricing and Billing.
One test case run. Skipped tests are excluded. Retries count separately. Artifacts do not affect the count.
Usage resets on your billing cycle date. Overage, if applicable, appears on the next invoice. Upgrade if you hit limits regularly. See Billing.
Access continues until the current period ends. The org moves to the Community plan with Community limits.
Open Manage Billing → View All Plans, select a plan, and confirm. Upgrades usually apply immediately; downgrades at period end. See Manage Billing.

​
Security and Privacy

Yes. SOC 2 Type 2, ISO 27001, and GDPR. See Security & Compliance, or email support@testdino.com for audit reports or a signed DPA.
TLS 1.2+ in transit and AES-256 at rest. See Encryption.
No. Providers are under terms that prohibit training on customer content. Disable AI per project if needed. See AI data handling.

Troubleshooting

Token, streaming, CI, and API fixes

Glossary

TestDino and Playwright terms

Discord

Community questions and updates

Email

support@testdino.com