CircleCI TestDino CLI Setup - TestDino Documentation

What you’ll learn

How to upload Playwright results from CircleCI using the tdpw CLI
How to configure sharded test runs with merged reporting

Upload Playwright test results to TestDino using the tdpw CLI directly in your CircleCI config.

Prerequisites

Before setting up, ensure you have:

A TestDino account with a project created
A TestDino API key (Generate API Keys)
TestDino Example Repository for sample tests and ready-to-use CI configs
A CircleCI account with access to your repository
Playwright configured with JSON and HTML reporters in playwright.config.js:

playwright.config.js

// ...existing config

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

Set Up Your API Key

Open your project in CircleCI
Go to Project Settings → Environment Variables
Click Add Environment Variable
Set the name to TESTDINO_TOKEN
Paste your TestDino API key as the value
Save the variable

WarningNever commit your API key directly in config files. Always use environment variables.

Basic Config

.circleci/config.yml — Basic config

.circleci/config.yml

version: 2.1

jobs:
  test:
    docker:
      - image: mcr.microsoft.com/playwright:v1.59.1-noble
    working_directory: ~/project
    environment:
      CI: "true"
    steps:
      - checkout
      - run:
          name: Install dependencies
          command: npm ci
      - run:
          name: Run Playwright tests
          command: npx playwright test
      - run:
          name: Upload results to TestDino
          command: npx tdpw upload ./playwright-report --token="$TESTDINO_TOKEN"
          when: always

workflows:
  test-and-upload:
    jobs:
      - test

TipThe when: always flag ensures the upload runs even if tests fail.

Upload Options

Flag	Description	Default
`--environment <value>`	Target environment tag (staging, production, qa)	unknown
`--tag <values>`	Comma-separated run tags for categorization (max 5)	None
`--upload-images`	Upload image attachments	false
`--upload-videos`	Upload video attachments	false
`--upload-html`	Upload HTML reports	false
`--upload-traces`	Upload trace files	false
`--upload-files`	Upload file attachments (.md, .pdf, .txt, .log)	false
`--upload-full-json`	Upload all attachments	false
`--json`	Output results as JSON to stdout (for CI/CD)	false
`-v, --verbose`	Enable verbose logging	false

Sharded Test Runs

For larger test suites, CircleCI parallelism splits tests across multiple containers. Each shard produces a blob report that needs to be merged before uploading.

How it works

CircleCI runs Playwright across 4 shards using parallelism: 4
Each shard saves its blob report to a workspace directory
A separate merge-and-upload job collects all blob reports, merges them, and uploads to TestDino
The merge job runs even if some shards fail

Full sharded config

.circleci/config.yml — Sharded config

.circleci/config.yml

version: 2.1

jobs:
  test:
    docker:
      - image: mcr.microsoft.com/playwright:v1.59.1-noble
    working_directory: ~/project
    parallelism: 4
    environment:
      CI: "true"
    steps:
      - checkout

      - run:
          name: Run Playwright shard
          command: |
            mkdir -p workspace/blob/$CIRCLE_NODE_INDEX
            npm ci

            set +e
            npx playwright test --shard=$((CIRCLE_NODE_INDEX + 1))/$CIRCLE_NODE_TOTAL
            TEST_EXIT_CODE=$?

            if [ -d blob-report ]; then
              cp -R blob-report/. workspace/blob/$CIRCLE_NODE_INDEX/
            fi

            echo $TEST_EXIT_CODE > /tmp/test-exit-code
            exit 0

      - persist_to_workspace:
          root: workspace
          paths:
            - blob

      - store_artifacts:
          path: test-results
          destination: test-results

      - store_test_results:
          path: test-results

      - run:
          name: Mark shard failed if tests failed
          when: always
          command: |
            exit $(cat /tmp/test-exit-code)

  merge-and-upload:
    docker:
      - image: mcr.microsoft.com/playwright:v1.59.1-noble
    working_directory: ~/project
    environment:
      CI: "true"
    steps:
      - checkout

      - attach_workspace:
          at: workspace

      - run:
          name: Install dependencies
          command: npm ci

      - run:
          name: Merge reports
          command: |
            mkdir -p merged-blob-reports playwright-report
            find workspace/blob -type f -name "*.zip" -exec cp {} merged-blob-reports/ \;
            npx playwright merge-reports --reporter=json merged-blob-reports > playwright-report/report.json

      - run:
          name: Upload to TestDino
          command: npx tdpw upload ./playwright-report --token="$TESTDINO_TOKEN"

      - store_artifacts:
          path: playwright-report
          destination: playwright-report

workflows:
  test:
    jobs:
      - test
      - merge-and-upload:
          requires:
            - test:
                - success
                - failed
                - canceled

Key details

Config Block	What It Does
`parallelism: 4`	Runs 4 shard containers in parallel
`--shard=$((CIRCLE_NODE_INDEX + 1))/$CIRCLE_NODE_TOTAL`	CircleCI uses 0-based indexing, Playwright uses 1-based
`set +e` / `exit 0`	Prevents shard failure from stopping blob report collection
`persist_to_workspace` / `attach_workspace`	Passes blob reports from shards to the merge job
`requires: success, failed, canceled`	Merge job runs regardless of shard outcomes

Run Locally

npm ci
npx playwright install --with-deps
npx playwright test
npx tdpw upload ./playwright-report --token="$TESTDINO_TOKEN"

Troubleshooting

Upload step skipped after test failure

Add when: always to the upload step. For sharded runs, the merge-and-upload job must require the test job with success, failed, and canceled statuses.

No report found at ./playwright-report

Verify your playwright.config.js outputs to playwright-report/. For sharded runs, ensure persist_to_workspace includes blob and the merge step writes to playwright-report/.

TESTDINO_TOKEN not found

Confirm the environment variable is set in CircleCI → Project Settings → Environment Variables. Variable names are case-sensitive.

Sharded reports not merging correctly

Ensure all shards copy blob reports to workspace/blob/$CIRCLE_NODE_INDEX/. Verify blob reports are .zip files.

Next Steps

CI Optimization

Reduce CI time with smart reruns

Branch Mapping

Map branches to environments for organized test runs

Integrations

Connect Slack, Jira, Linear, Asana, and more

TestDino MCP

Access test results and fix issues with AI agents

​Prerequisites

​Set Up Your API Key

​Basic Config

​Upload Options

​Sharded Test Runs

​How it works

​Full sharded config

​Key details

​Run Locally

​Troubleshooting

​Next Steps

CI Optimization

Branch Mapping

Integrations

TestDino MCP

Prerequisites

Set Up Your API Key

Basic Config

Upload Options

Sharded Test Runs

How it works

Full sharded config

Key details

Run Locally

Troubleshooting

Next Steps