@testdino/playwright, so no upload step is needed.
Quick Reference
Setup
Install@testdino/playwright and add it to the reporter array in your Playwright config. This is the only entry TestDino needs. Other reporters (html, list) are optional and yours to keep.
playwright.config.ts
Prefer not to edit your config?
Prefer not to edit your config?
Run It wraps
tdpw test instead of npx playwright test. Same result, no config change.npx playwright test, so any Playwright flag passes through, for example npx tdpw test --project=chromium --shard=1/3.Connection Status
While the page waits for a run, it reports the state of its live connection to TestDino.
Results are never lost while the connection is down. The reporter keeps sending, and the page catches up once it reconnects.
Active Test Runs
The Test Runs page displays a collapsible Active Test Runs section. Each active run shows a progress bar, live result counts, commit, branch, and CI source.
For sharded runs, the run is labeled SHARDED with tabs for each shard. Select a tab to view its workers and currently executing tests.
Runs assembled from separate CI jobs with split mode are labeled SPLITTED. Their progress bar carries one segment per split, and each split gets a tab. Progress advances as each job reports, so a group whose jobs run concurrently fills in steps rather than smoothly.
Multi-Tab Support
Only one browser tab opens a WebSocket connection to TestDino. This tab acts as the primary tab. Additional tabs receive updates through the browser’s BroadcastChannel API.- If you close the primary tab, another open tab promotes itself and opens a new WebSocket.
- All tabs display the same live data regardless of which tab holds the connection.
Known Limitations
FAQ
What happens if the WebSocket disconnects mid-run?
What happens if the WebSocket disconnects mid-run?
Results keep sending. The reporter delivers results directly from your test process, on a separate path from the dashboard’s live connection, so a dropped browser connection never affects what reaches TestDino. When the dashboard reconnects, it catches up to the current state.
Do I need to keep the dashboard open while tests run?
Do I need to keep the dashboard open while tests run?
No. The reporter sends results from CI whether or not anyone is watching. The Test Runs page is a viewer, not part of the delivery path. Open it whenever you like and the run is there, live or finished.
My test suite crashed halfway. Do I lose everything?
My test suite crashed halfway. Do I lose everything?
No. Results are sent as each test and step completes rather than in one batch at the end, so everything that ran before the crash is already recorded. The run shows the tests it completed and the point where it stopped.
Why does my run sit with no updates for a while?
Why does my run sit with no updates for a while?
A long-running test that produces no results is normal, for example a slow
waitFor or a lengthy setup step. The reporter sends a periodic signal during quiet stretches so the run stays live rather than being treated as abandoned. Updates resume when the next test finishes.Does disabling artifacts stop streaming?
Does disabling artifacts stop streaming?
No.
--no-artifacts skips uploading screenshots, videos, and traces. Test results, timings, and errors still stream normally. Use it when you want faster runs or smaller uploads and do not need the visual evidence.Related
Node.js CLI
Full CLI reference and configuration options
Test Runs
View and filter completed and active test runs
CI Integration
Configure GitHub Actions for automated test runs
Getting Started
Set up TestDino and run your first tests