Skip to main content
@testdino/e2e streams each test run from the e2e framework by TesterArmy ↗ to TestDino while it executes. The test run appears on the dashboard when e2e starts it, and each test case arrives with its retries, steps, errors, console output, and artifacts as it finishes. Learn what each test case records in How e2e Reporting Works. e2e is an open-source framework for end-to-end tests of web and mobile apps. Use this reporter if your tests live in *.e2e.ts files and run with npx e2e run.
Real-time streaming and re-runs need @testdino/e2e 1.1.0 or later. With 1.0.x, the test run appears once it finishes.
For Playwright, use the Node.js CLI instead.

Prerequisites

  • e2e >= 0.16.0 and < 1, installed in your project
  • Node.js version your e2e release supports. For example, e2e 0.21.3 needs ^22.22.3 or >= 24.8.0. The reporter itself needs >= 22.12.0.
  • 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:
The variable lasts until you close the terminal, so run your tests in the same terminal.
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.

Run through TestDino in CI

testdino-e2e run runs e2e run and adds what a reporter cannot do on its own. Use it in CI in place of npx e2e run, and put e2e’s own options after --:
  • Test Controls decide the build result. A test run whose only failures are quarantined, or match a known error, exits 0. A critical test case that passed only on retry exits 1. Exit codes 2, 3, 4, and 130 never change. With plain npx e2e run, Test Controls do not change the exit code.
  • A GitHub Actions retry runs only what failed. When you re-run a test run’s failures from TestDino, each retried job runs only its own failed test cases. A job that cannot be narrowed safely, for example one passing --repeat-each, runs in full and says why. A retry started in GitHub itself, not from TestDino, also runs in full.
  • Run a stored test selection with --selection, as Run automated tests does:
    The selection is checked against your checkout first. A selection that would also run test cases nobody selected, or none of whose test cases exist, runs nothing and tells TestDino why. Missing test cases are skipped, or fail the job after the rest ran, as the selection says. A selected setup test runs when a selected test case needs it. A selection of only setup tests runs nothing, because e2e cannot run a setup test alone.

Re-run failed tests

testdino-e2e rerun runs again only the test cases that failed in a TestDino test run. The re-run is a new test run, linked to the original. Run it from the folder with your e2e.config.ts, with TESTDINO_TOKEN set:
Set TEST_RUN_ID to the test run’s ID, or copy the full command from the test run’s page (below). -p @testdino/e2e makes npx use this package, never an unrelated package named testdino-e2e. The command prints TestDino re-run: 3 of 4 failed test(s) from run …, then e2e’s own output, and ends with e2e’s exit code. Each test case runs on the target it failed on. Test cases that are not on your checkout are skipped and named. e2e cannot run a setup test alone, so re-running one also runs the test cases that use it. When nothing is left to re-run, it exits 0 without starting e2e. If TestDino cannot say which test cases to run, it exits 1 and runs nothing. Stopping the command with Ctrl+C or docker stop stops the test cases it started.

Start a re-run from the dashboard

Re-run is in the action row on a test run’s page. It appears when the test run has finished with at least 1 failed or flaky test case and was uploaded by @testdino/e2e 1.1.0 or later. The panel offers Failed, Flaky, Both, and Custom, and you can add tags. Run it against This commit, Latest, or Another branch, or choose Run manually to copy the command. On GitHub Actions, This commit runs the failed jobs again inside the original run, and jobs that use testdino-e2e run run only their failed test cases. For how re-runs appear in the run list and how the test cases are chosen, see Re-run Failed Tests.

Re-run from an AI agent

For an e2e test run, the get_rerun_selection MCP tool returns the same testdino-e2e rerun command, for your agent to run in the project. rerun_test starts the re-run in CI, as it does for a Playwright test run.

Differences from Playwright test runs

e2e test cases appear as they start, traces arrive as walkthroughs in Markdown, and Test Controls change the build result only under testdino-e2e run. See the full list in How e2e Reporting Works.

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.
The test run has no test cases in the scope you chose. The command exits 0 without starting e2e. Pick another --scope, or check the test run on the dashboard.
A test run’s failed test cases are known only once it finishes. Wait for it to finish, then run the command again.
Check the test run ID, and that TESTDINO_TOKEN is an API key of the project the test run belongs to.
Some test cases in the selection can be picked only by their file and line, and the re-run command does not select by line, so nothing runs. The message lists their locations. Run each one with npx e2e run <file>:<line> instead.
The selection does not fit on a Windows command line. Re-run a narrower --scope, or run the command on macOS or Linux.
The command did not find e2e from the current folder. Run it from the folder with your project’s package.json.

How e2e Reporting Works

What TestDino records for each e2e test case, and the limits

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 November 12, 2026