Get Started with TestDino

Set up TestDino in 2 minutes. Configure Playwright reporters, generate an API key, and upload your first test report with traces and screenshots.

TestDino collects Playwright test results and displays them in dashboards with traces, screenshots, logs, and trends.

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

CopiedCopy promptOpen in Cursor

Quick Reference

Step	What to do
Configure reporters	Add JSON and HTML reporters to playwright.config.js
Run and upload	Run tests, then upload with the CLI
Add to CI	Upload after every test run in CI

How Upload Works

1. Configure Playwright to output JSON and HTML reports.
2. Run your tests.
3. Upload the report directory to TestDino using the CLI.

Configure and Upload

1. Follow the in-app setup guide

   After creating a project, TestDino shows a CLI setup guide with your API token pre-filled.

   
2. 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.

3. Run Tests & Upload

   Node.js

   # 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="$TESTDINO_TOKEN" --upload-html
   

   Skip --upload-html if you didn’t configure the HTML reporter.

   Python

   # 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="$TESTDINO_TOKEN" --upload-full-json
   

   Skip --upload-full-json if you didn’t configure HTML. Use --upload-images or --upload-videos as needed.

4. 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.

Add to CI

Add the upload step after your test execution step.

GitHub Actions - Node.js

.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 Actions - Python

.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

Explore what TestDino tracks once your first report is uploaded.

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