Get Started with TestDino

TestDino collects Playwright test results and organizes them into dashboards with traces, screenshots, logs, and trends.

Use this pre-built prompt to set up TestDino faster.

Open in Cursor

How It Works

Configure Playwright to output JSON and HTML reports
Run your tests
Upload the report to TestDino using the CLI

Setup

Follow the in-app setup guide

After creating a project, TestDino shows a CLI setup guide with your API token pre-filled. Follow the steps to install the CLI, configure reporters, and upload your first report. TestDino in-app CLI setup guide showing install, token, reporter config, and upload steps

TestDino in-app CLI setup guide showing install, token, reporter config, and upload steps

Configure Playwright Reporters

Add JSON and HTML reporters to your Playwright config:

playwright.config.js

reporter: [
  ['html', { outputDir: './playwright-report' }],
  ['json', { outputFile: './playwright-report/report.json' }],
]

The HTML reporter must be listed before the JSON reporter. Playwright’s HTML reporter clears its output directory on each run, so placing it first ensures report.json is not deleted.

Run Tests & Upload

Node.js
Python

# Install the TestDino CLI (first time only)
npm install tdpw

# Run your tests
npx playwright test

# Upload results to TestDino
npx tdpw upload ./playwright-report --token="<API_KEY>" --upload-html

Omit --upload-html if you did not configure the HTML reporter.

# Install dependencies (first time only)
pip install pytest-playwright-json pytest-html testdino

# Run your tests
pytest \
  --playwright-json=test-results/report.json \
  --html=test-results/index.html \
  --self-contained-html

# Upload results to TestDino
testdino upload ./test-results --token="<API_KEY>" --upload-full-json

Omit --upload-full-json if you skipped HTML. Use --upload-images or --upload-videos as needed.

Verify in Dashboard

Open Test Runs in your project. Confirm the run appears with pass/fail counts, duration, screenshots (if HTML was uploaded), and AI insights.

CI/CD Integration

Add these steps to your workflow after your test execution step.

GitHub Actions - Node.js
GitHub Actions - Python

.github/workflows/test.yml

- name: Install TestDino CLI
  run: npm install tdpw

- name: Upload to TestDino
  if: always()
  run: npx tdpw upload ./playwright-report --token="${{secrets.TESTDINO_TOKEN}}" --upload-html

.github/workflows/test.yml

- name: Install dependencies
  run: |
    pip install pytest pytest-playwright pytest-playwright-json pytest-html testdino
    playwright install chromium --with-deps

- name: Run tests
  run: |
    pytest \
      --html=test-results/index.html \
      --self-contained-html \
      --playwright-json=test-results/report.json

- name: Upload to TestDino
  if: always()
  run: testdino upload ./test-results --token="${{secrets.TESTDINO_TOKEN}}" --upload-full-json

Next Steps

Branch Mapping

Configure branch mapping for your project

Pull Requests

View test results linked to pull requests

Analytics

Explore test analytics and insights

Users & Roles

Manage organization members and permissions

Getting Started

AI

Guides

Platform

Resources

How It Works

Setup

CI/CD Integration

Next Steps

Branch Mapping

Pull Requests

Analytics

Users & Roles

Getting Started

AI

Guides

Platform

Resources

​How It Works

​Setup

​CI/CD Integration

​Next Steps

Branch Mapping

Pull Requests

Analytics

Users & Roles

How It Works

Setup

CI/CD Integration

Next Steps