@testdino/e2e sends each test run from the e2e framework by TesterArmy to TestDino while it executes. The test run appears when e2e starts it, each test case is listed as it starts, and its result, errors, logs, and artifacts arrive as it finishes. To install and configure the reporter, see the E2E page.
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, failure details, app logs, walkthroughs, and re-runs need
@testdino/e2e 1.1.0 or later. Check yours with npm ls @testdino/e2e. With 1.0.x, the test run appears once it finishes.What appears while the test run executes
Test cases that have not started yet are not listed. A Playwright test run lists every test case from the start; an e2e test run lists each one as it begins. Learn how active runs update on the dashboard in Real-Time Streaming.
What TestDino records for each test case
Open a test case to see these on its test case page.
Failure details
A failed test case’s error shows the line of the test file that failed, then what e2e saw at the moment of failure:
Each line holds at most 1,000 characters. These lines sit in the error’s details, not its message, so they do not change how the failure is grouped or classified.
App logs
What the app under test logged during a test case appears in its Console, next to the test case’s own output. Each line names its source and the step it happened in:stderr, everything else as stdout. Each attempt keeps its newest 200 lines and says how many earlier lines it left out. A URL in a line keeps its address and path, without a password, query string, or fragment. App logs need e2e 0.19.0 or later.
Walkthroughs
A walkthrough is a step-by-step record of a test case’s last attempt: each step and what it did, what the app logged, and the screen at failure. It appears in the Attachments of that attempt, namedwalkthrough, for each test case e2e keeps a trace page for. e2e’s trace setting decides which: by default (retain-on-failure), test cases that failed, timed out, were interrupted, or were flaky. Set trace: 'on' in your e2e config to keep one for every test case. Expand it to read it, or download it.
Walkthroughs need e2e 0.19.0 or later. They open as text, not in the trace viewer, which reads Playwright traces only.
How e2e failures are classified
TestDino sorts each failure by e2e’s error code. The category appears on the Failed and Flaky cards of the run summary and on the Errors tab.
A Setup issue means a step was blocked before it could check the app: a credential was missing or rejected, the app or environment did not answer, seed data was missing, a setup test failed, the app was not open, a policy refused the action, or no AI model was available. The failure points at the test setup, not at the app under test. Other codes are classified from the error text, as for Playwright: a timeout as Timed out, a refused connection as Network error, and anything else as Unclassified error.
Differences from Playwright test runs
Related
E2E
Install the reporter, set options, and re-run failed tests
Errors tab
Group a test run’s failures by cause and category