Skip to content

chore(e2e): simplify testkit copy + stream relay-button-chat progress - #5

Open
NiKrause wants to merge 1 commit into
mainfrom
chore/consumer-followups
Open

chore(e2e): simplify testkit copy + stream relay-button-chat progress#5
NiKrause wants to merge 1 commit into
mainfrom
chore/consumer-followups

Conversation

@NiKrause

Copy link
Copy Markdown
Owner

Consumer follow-ups now that the shared @le-space/playwright testkit (relay-button 0.6.34) ships the fixes it needed.

What & why

1. Drop the testkit chunk-copy workaround (both E2E workflows)
build:publish is now self-contained (--no-splitting), so a single cp .../dist/index.js …/index.mjs replaces the previous "mirror the whole dist tree + synthetic {"type":"module"}" hack that worked around tsup code-splitting (Cannot find module chunk-*.js).

  • .github/workflows/js-peer-relay-button-e2e.yml
  • .github/workflows/js-peer-remote-replication.yml

2. Make relay-button-chat.spec.ts diagnosable instead of silent
The relay-button chat E2E previously ran for minutes with no output. It now uses the testkit's logging helpers:

  • forwardBrowserConsole(page, { label }) per browser → each browser's libp2p connection/discovery console lines stream into the test log.
  • createProgressLogger({ label: 'relay-chat' }) → timestamped stage markers (provisioning, opening-browsers, connecting-relay, and every evidence step via pass()), matching simple-todo's [remote-e2e] stage: … format.

Scope notes

🤖 Generated with Claude Code

The @le-space/playwright testkit now builds self-contained (--no-splitting
in 0.6.34), so both E2E workflows can copy a single dist/index.js instead of
mirroring the whole dist tree with a synthetic package.json — drop the
chunk-copy workaround in js-peer-relay-button-e2e.yml and
js-peer-remote-replication.yml.

Adopt the testkit's logging helpers in relay-button-chat.spec.ts so the run
is no longer silent for minutes: forward each browser's libp2p console into
the test log via forwardBrowserConsole, and emit timestamped stage markers
(provisioning, opening-browsers, connecting-relay, plus every evidence step)
through createProgressLogger.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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