Skip to main content
Set up CircleCI to upload Playwright test results to TestDino using the TestDino Orb , a prebuilt package that wraps the TestDino CLI so you don’t need to install it separately.
RecommendationFor more configuration options and the latest features, use the TestDino CLI approach instead. The Orb wraps the CLI but may not include all new updates immediately.

Pick an upload mode

The orb supports 4 upload modes. Pick one based on what you want in the dashboard.

Prerequisites

playwright.config.js

Set Up Your API Key

  1. Open your project in CircleCI
  2. Go to Project Settings → Environment Variables
  3. Click Add Environment Variable
  4. Set the name to TESTDINO_TOKEN
  5. Paste your TestDino API key as the value
  6. Save the variable
WarningNever commit your API key directly in config files. Always use environment variables.

Basic Upload

.circleci/config.yml

Upload with HTML Report

.circleci/config.yml

Upload Full Bundle

Include all artifacts (JSON, images, videos) in one upload.
.circleci/config.yml

Upload with Custom Paths

Specify custom report paths and include images and videos.
.circleci/config.yml

Orb Parameters

TipUse CircleCI contexts (e.g., testdino-credentials) to manage secrets across multiple jobs without repeating environment variable setup.

Troubleshooting

Ensure the orb is imported correctly: testdino: testdino/testdino@1.0.0. Check the CircleCI Orb Registry for the latest version.
Confirm the environment variable is set in CircleCI → Project Settings → Environment Variables. If using contexts, verify the job references the correct context name.

CI Optimization

Reduce CI time with smart reruns

Environment Mapping

Route test results to Dev, Staging, or Production by branch

Integrations

Connect Slack, Jira, Linear, Asana, and more

TestDino MCP

Access test results and fix issues with AI agents