Skip to content

Treat trace.webdriver.io as live and run its scheduled check - #552

Merged
vishnuv688 merged 4 commits into
mainfrom
docs/hosted-player-live
Nov 10, 2026
Merged

vishnuv688 merged 4 commits into
mainfrom
docs/hosted-player-live

Conversation

@vishnuv688

Copy link
Copy Markdown
Member

What & why

Part of #494.

trace.webdriver.io is live: Vercel's Git integration deploys main to production and builds a preview for each PR. This brings the repo in line with that.

  • README and changeset: the hosted player heading links trace.webdriver.io again (it said "not deployed yet"), and the hosted-trace-player changeset says it is the build trace.webdriver.io serves.
  • Scheduled check: scheduled-hosted-player.yml skipped every run. It read vars.HOSTED_PLAYER_URL, which is unset (the URL was added as a secret, which a workflow cannot read there), and its deployment_status trigger never fires because Vercel reports in PR comments, not as GitHub deployments. It now defaults to https://trace.webdriver.io when the variable is unset and runs every six hours and on demand; the dead trigger is removed. Issue open/close behaviour is unchanged.
  • Capability matrix: a new row, "Prints where each kept trace was written": the WebdriverIO service prints the path to stdout whatever the logLevel (evidence: packages/service/tests/trace-granularity.test.ts); Selenium, Nightwatch and Python log it at info level, so partial with that reason. README tables regenerated. Seven single-argument reasons moved to capability-reasons.ts to keep features.ts under the size cap; rendered text unchanged.
  • ARCHITECTURE.md / CLAUDE.md: one sentence each on how Vercel deploys and how the check now runs.

Type of change

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Polish (an improvement to an existing feature)
  • Breaking change (existing behavior changes for users)
  • Documentation
  • Internal (build, CI, dependencies, tooling)

Packages touched

  • shared (types and contracts)
  • core (framework-agnostic capture/reporting)
  • elements (published element/snapshot API — @wdio/elements)
  • service (WebdriverIO adapter)
  • nightwatch-devtools (Nightwatch adapter)
  • selenium-devtools (Selenium adapter)
  • selenium-devtools-py (Selenium Python adapter)
  • backend (server)
  • app (UI)
  • script (page-injected runtime)
  • trace (Trace mode)

Plus conformance (the matrix) and CI. No published package changes, so no new changeset; the existing hosted-trace-player changeset's wording is corrected.

Capability matrix

  • packages/conformance/src/features.ts updated, and tables regenerated with pnpm docs:capabilities, if this adds or changes user-facing behaviour

The new row is mirrored on the docs site in webdriverio/webdriverio#16379.

Notes for reviewers

  • Player-side features (opening a whole run, the hosted player, ?trace= links) get no matrix row: every row declares a cell per adapter, and these behave the same for any adapter's zip.
  • Checked against this round's merged changes (the Log tab default, closed wait rows, show-trace not caching, password masking): nothing in the README, CLAUDE.md, ARCHITECTURE.md or matrix reasons was untrue, so nothing else changed.
  • pnpm build, pnpm typecheck, pnpm test (4011 passed, 1 skipped), pnpm lint and pnpm docs:capabilities --check are green.
  • After merge, the next scheduled run (or "Run workflow" on Hosted player check) should run instead of skipping.

Screenshots / recordings

None.

🤖 Generated with Claude Code

vishnuv688 and others added 4 commits November 10, 2026 12:00
The service prints each kept trace's path to stdout whatever the logLevel,
while Selenium, Nightwatch and Python only log it at info level, which a
run hiding info messages never shows. The matrix should say so rather than
leave users to find out from a silent run.

Seven single-argument reasons move to capability-reasons.ts so each cell
fits on one line and features.ts stays under the 500-line soft cap.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The hosted player is deployed: Vercel serves main at trace.webdriver.io and
builds a preview per PR, so the README heading and the pending changeset no
longer describe it as not yet deployed, and ARCHITECTURE.md says where the
hosted build is served from.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The workflow read vars.HOSTED_PLAYER_URL, which is unset, so every run was
skipped, and its deployment_status trigger never fired because Vercel
reports deploys in PR comments rather than as GitHub deployments. Default
the URL to the production player and drop the dead trigger; the schedule
and workflow_dispatch remain, and the issue open/close behaviour is
unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Nov 10, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
devtools Ready Ready Preview Nov 10, 2026 6:39am UTC

Request Review

@vishnuv688 vishnuv688 self-assigned this Nov 10, 2026
@vishnuv688
vishnuv688 merged commit 51c1827 into main Nov 10, 2026
14 checks passed
@vishnuv688
vishnuv688 deleted the docs/hosted-player-live branch November 10, 2026 07:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant