[Winify]

Stack

• feat(core): stamp a trace and span id on each test attempt in the artifacts manifest #553 ← this PR
• feat: add a telemetry mode that writes only the artifacts manifest #554
• feat(otel): add a CLI that pushes artifacts manifests as OTLP spans #555
• docs(examples): add a Grafana LGTM stack for telemetry mode #556

Part 1 of 4 of the OpenTelemetry export, replacing #485.

What

The artifacts manifest (devtools-artifacts-<sessionId>.json) can now link a run to its traces:

• Each test attempt gets a trace and span id when it starts, recorded in a per-test attempts[] list. The test's last attempt is marked final, so a consumer reading the manifest can tell a retried test from its earlier attempts.
• The manifest records the run's runId and, when the run was launched under a TRACEPARENT, that parent context.
• WDIO entries carry start and end times, the framework-reported duration (Cucumber scenarios fall back to wall-clock time), and the final attempt's failure message.
• A Cucumber scenario is listed once, and its steps are no longer listed as tests.
• WDIO passes its retry count into the attempt record, so under specFileRetries the final flag and the attempt number agree.

Why

#485 created span ids when the manifest was uploaded, after the run ended. A test therefore had no id while it ran, so its span couldn't be linked live or carry a CI parent. Ids recorded when each attempt starts fix that. Pushing the same manifest again also gives the same spans.

Verification

pnpm build, pnpm test (3999 passed, 4 skipped), pnpm lint (0 errors) and pnpm docs:capabilities --check pass on this branch.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
devtools	Ready	Preview	Nov 11, 2026 1:27pm UTC

[plum117]

Reviewed the stack at 07b101a: ran the examples (WDIO mocha/Cucumber, Selenium, Nightwatch × telemetry/trace × retries × TRACEPARENT) and pushed each run to a fake receiver and to the #556 stack. Tests, lint, typecheck pass. Direction looks right. "read only" = found in the code, not run.

1. Selenium retry: wrong attempt data. A flaky test is listed twice. final is on the failed attempt 0, so the push sends 3 spans, one of them "pass, final". Cause: the metadata uid is generateStableUid (changes on retry), but the ledger uid is deterministicUid.
2. Absolute artifacts[].path. After test-results/ moves (CI artifact download), the push does not read the zips, gives no URL and exits 1. With relative paths, it works.
3. specFileRetries: both attempts are attempt: 0. WDIO sends the real count as retry on runner:start; the service reporter can record it.
4. Only the final attempt keeps error; the flaky attempt's failure is lost.
5. Selenium/Nightwatch record no error and no test-level timing, so a failing span has no message. The same change in 3 adapters → core?
6. (read only) suite-helpers.ts:192: in Selenium Cucumber, a repeated step text makes the scenario attempt: 1.
7. (read only) attempt-tracker.ts:85: renumbering in recordOutcome and numbering by length in recordStart can give attempt numbers that repeat or are out of order.