Skip to main content
@testdino/e2e reports each test run from the e2e framework by TesterArmy ↗ to TestDino when the run finishes. The test run appears on the dashboard with its test cases, retries, steps, errors, console output, screenshots, videos, and traces. For Playwright, use the Node.js CLI instead.

Prerequisites

  • Node.js >= 22.12.0
  • e2e >= 0.16.0 and < 1
  • TestDino API key (generate one)
  • Git initialized repository (for commit and branch metadata)
  • @types/node, if you type-check your project with tsc

Installation

View @testdino/e2e on npm ↗.

Set up

Add testdino() to the reporters array in your e2e config. Other reporters, such as list, are optional and yours to keep.
e2e.config.ts
Set your API key and run your tests:
When the run finishes, the TestDino line of the e2e output shows a link to the test run, or the number of test cases it uploaded.

Reporter options

Pass options to testdino(). An option set in the config takes precedence over its environment variable.
e2e.config.ts

Sharded runs

Set the same TESTDINO_CI_RUN_ID on every shard. TestDino merges the shards into 1 test run.
On GitHub Actions, use ${{ github.run_id }}-${{ github.run_attempt }} as the ID. A shard started without TESTDINO_CI_RUN_ID uploads as its own test run.

Split mode

When your jobs run different files, use split mode instead of sharding. Give each job its position and the same split ID. TestDino merges the jobs into 1 test run.
Set both variables. Learn how to read the Splits panel in Split mode.

Differences from Playwright test runs

Troubleshooting

The reporter found no API key. Set TESTDINO_TOKEN in the environment that runs npx e2e run, or pass token to testdino(). Generate a new key from API Keys if needed.
Your organization used its executions for this billing cycle. Tests still run, but the test run is not saved. To resume recording, upgrade your plan, or on Pro and Team plans an Owner or Admin can add executions for this cycle.
The machine running the tests could not reach TestDino. Check that it allows outbound connections to TestDino, then run the tests again.
A shard ran without TESTDINO_CI_RUN_ID. Set the same value on every shard, as in Sharded runs.
Only 1 of TESTDINO_SPLIT and TESTDINO_SPLIT_ID was set. Set both on every job, as in Split mode.

Configuration

Review the commit, CI, and targets of a test run

Generate API Keys

Create and manage keys for the reporter and CI
Last modified on October 27, 2026