Get Started

Upload your first Playwright run to TestDino

Set up TestDino in minutes. Access test traces, screenshots, logs, and trends in one centralized hub. Fix CI failures faster and reduce flaky test reruns.

How it works

TestDino integrates seamlessly with your existing Playwright tests:

1. Run your tests - Execute Playwright tests in your CI/CD pipeline as usual
2. Upload results - Automatically send test results to TestDino using our CLI or native CI integrations
3. Analyze and improve - Use dashboards, visual evidence, and AI-powered insights to triage failures and track quality trends

Setup steps

1. Create a Project

   When first signing in to TestDino, you are prompted to create a new organization and a project. You can change their names and settings at any time.

   

   Enter a Project Name and an optional Description. Paid plans include configurable test execution limits in Test Limits.

2. Generate an API Key

   

   • Generate API key with an appropriate name for this project.
   • Copy the key when shown. It is required for uploads and is only revealed once.
   • Select Continue.

   Treat the key as a secret. Store it in your CI’s secret store if you plan to upload from CI.

3. Configure Local Setup

   Update your Playwright configuration to emit JSON (required) and optionally HTML (for asset upload).

   playwright.config.js

   // Add this in playwright.config.js or playwright.config.ts
   reporter: [
     // Mandatory reporter for JSON results
     ['json', { outputFile: './playwright-report/report.json' }],
     // Optional, enables native HTML upload
     ['html', { outputDir: './playwright-report' }],
   ]
   

   • Keep the output paths consistent; the uploader expects the folder that contains report.json (for example, ./playwright-report).
   • Tick the confirmation box in the wizard, then select Continue.
4. Choose Your CI/CD Provider (Optional)

   Select your CI/CD platform for automated test reporting. This is an optional integration.

   For GitHub Actions Configuration:

   Node.js

   .github/workflows/test.yml

   - name: Install TestDino CLI
     run: npm install tdpw
   
   - name: TestDino Reporter
     run: |
       npx tdpw upload path/to/report/directory --token="${{secrets.TESTDINO_TOKEN}}" --upload-html
   

   Add these steps to your GitHub Actions workflow file (e.g., .github/workflows/test.yml) after your test execution step.

   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 \
         --playwright-json=test-results/report.json \
         --html=test-results/index.html \
         --self-contained-html
   
   - name: TestDino Reporter
     if: always()
     run: testdino upload ./test-results --token="${{secrets.TESTDINO_TOKEN}}" --upload-full-json
   
5. Upload Your First Test Run

   Copy this ready-to-run upload command for your project.

   Node.js

   Typical local flow:

   1. Install the TestDino CLI (first time only):

      npm install tdpw
      

   2. Run your tests:

      npx playwright test
      

   3. Upload the report folder:

      npx tdpw upload path/to/report/directory --token="<API_KEY>" --upload-html
      

   4. If you skipped HTML, omit --upload-html.

   Python

   Typical local flow:

   1. Install required plugins (first time only):

      pip install pytest-playwright-json pytest-html testdino
      

   2. Run your tests with JSON and HTML reports:

      pytest \
        --playwright-json=test-results/report.json \
        --html=test-results/index.html \
        --self-contained-html
      

   3. Upload the report folder:

      testdino upload ./test-results --token="<API_KEY>" --upload-full-json
      

   4. If you skipped HTML, omit --upload-full-json and use --upload-images --upload-videos as needed.

   To exit, select Complete Setup.

6. Verify Your First Run

   • Open Test Runs in your project.
   • Confirm the new run is listed with pass/fail counts and duration.
   • Open the test run to review errors and test case details for screenshots (if HTML was uploaded), and see AI insights.

   If you spot gaps or have ideas to improve the page, email [e-mail]. Your input helps us prioritize fixes and features.

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