What's Changing

What to do after the TestDino update: sign in again, create a new API key, and switch to the @testdino/playwright package.

TestDino has been updated. Your test run history, dashboards, and analytics all carried over. Nothing is lost.

Your API keys and personal access tokens stopped working, and the old tdpw upload commands are removed. Follow the steps below to get running again.

What you need to do

Follow these 4 steps in order once the update is done.

1. Sign in again

   If you were signed out, open app.testdino.com and sign back in. Your password and single sign-on still work.

2. Create a new API key

   Your old API keys stopped working. Create a new one:

   1. Open your project and go to Project Settings → API Keys.
   2. Click New → API Key, name it, and click Create.
   3. Copy the key and save it. It is shown only once.
   4. Delete your old API keys.

   A personal access token (PAT) is optional. Create one only if you use the public API or MCP: open User Settings → Personal Access Tokens → Generate new token, name it, select the organizations and projects it may reach, then create it.

   Full walkthrough: Generate API Keys and the API Quickstart.

3. Install the new package and add it to your config

   Install @testdino/playwright. It streams test results live as a run executes.

   npm install @testdino/playwright
   

   The old tdpw package is deprecated. Replace it with @testdino/playwright.

   Add TestDino to the reporter array in your Playwright config. This is the only entry TestDino needs. Other reporters (html, list) are optional and yours to keep.

   playwright.config.ts

   import { defineConfig } from '@playwright/test';
   
   export default defineConfig({
     reporter: [
       ['@testdino/playwright', {
         token: process.env.TESTDINO_TOKEN,
         serverUrl: "https://reporter.testdino.com",
       }],
     ],
   });
   

   Set your new token and run your tests. No upload step is needed.

   export TESTDINO_TOKEN="your-new-api-key"
   npx playwright test
   

   Prefer not to edit your config?

   Skip the reporter step above and run tdpw test instead. Same result, no config change. Pass your token with -t, or set TESTDINO_TOKEN first and omit it.

   npx tdpw test -t "your-new-api-key" --server-url https://reporter.testdino.com
   

   It wraps npx playwright test, so any Playwright flag passes through, for example npx tdpw test -t "your-new-api-key" --project=chromium --shard=1/3.

4. Update your CI

   Replace the old token in your CI secrets with the new API key, under the name TESTDINO_TOKEN. Keep @testdino/playwright in your Playwright config and run npx playwright test in the pipeline. Until the new token is in place, test runs fail with an authentication error.

   - name: Run Playwright tests with TestDino
     env:
       TESTDINO_TOKEN: ${{ secrets.TESTDINO_TOKEN }}
     run: npx playwright test
   

Full setup and every CLI flag is in the Node.js CLI guide.

SSO admins

If your organization uses single sign-on, org owners and admins have 2 extra steps.

1. Re-enter your identity provider secret

   Go to Settings → Single Sign-On and enter the secret again.

2. Allow the new IP address

   Support sends you a new IP address. Add it to your identity provider’s allowlist when they tell you to.

What’s new

Feature	What it does
Real-time streaming	Test results appear live as a run executes, with no upload step.
Custom dashboards	Build project and organization dashboards around your metrics.
Redesigned interface	Updated navigation and layouts across the product.
Shard-level views	See per-shard breakdowns for sharded runs.
Anomaly detection	Flags unusual behavior at the test run level.
Expanded MCP tools	33 MCP tools now cover audits, error grouping, and issue-tracker integrations. See the MCP Tools Reference.

Get help

Something not working after the update? Email [e-mail].

Generate API Keys

Create and manage API keys for the CLI and CI

API Quickstart

Create a personal access token for the API

Support

Contact the team for help