@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.
@testdino/e2e 1.1.0 or later. With 1.0.x, the test run appears once it finishes.Prerequisites
e2e>= 0.16.0and< 1, installed in your project- Node.js version your
e2erelease supports. For example,e2e0.21.3 needs^22.22.3or>= 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 withtsc
Installation
@testdino/e2e on npm ↗.
Set up
Addtestdino() to the reporters array in your e2e config. Other reporters, such as list, are optional and yours to keep.
- macOS / Linux
- Windows (PowerShell)
Reporter options
Pass options totestdino(). An option set in the config takes precedence over its environment variable.
Sharded runs
Set the sameTESTDINO_CI_RUN_ID on every shard. TestDino merges the shards into 1 test run.
${{ 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.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 exits1. Exit codes2,3,4, and130never change. With plainnpx 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:
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.
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, theget_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 undertestdino-e2e run. See the full list in How e2e Reporting Works.
Troubleshooting
skipped (TESTDINO_TOKEN is not set)
skipped (TESTDINO_TOKEN is not 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.not recorded (the project is over its execution limit)
not recorded (the project is over its execution limit)
not uploaded (no event channel the server offered could be reached)
not uploaded (no event channel the server offered could be reached)
split ignored: a split position and TESTDINO_SPLIT_ID are needed together
split ignored: a split position and TESTDINO_SPLIT_ID are needed together
TESTDINO_SPLIT and TESTDINO_SPLIT_ID was set. Set both on every job, as in Split mode.TestDino re-run: nothing to re-run
TestDino re-run: nothing to re-run
0 without starting e2e. Pick another --scope, or check the test run on the dashboard.TestDino re-run: Run … has not finished yet
TestDino re-run: Run … has not finished yet
TestDino re-run: Run … is unknown, belongs to another project, or is not accessible with this token
TestDino re-run: Run … is unknown, belongs to another project, or is not accessible with this token
TESTDINO_TOKEN is an API key of the project the test run belongs to.TestDino re-run: Some of run …'s tests can only be told apart by file and line
TestDino re-run: Some of run …'s tests can only be told apart by file and line
npx e2e run <file>:<line> instead.TestDino re-run: … tests are too many to pass to e2e at once on Windows
TestDino re-run: … tests are too many to pass to e2e at once on Windows
--scope, or run the command on macOS or Linux.TestDino re-run: e2e is not installed in this project
TestDino re-run: e2e is not installed in this project
package.json.