fix(trace): settle in-flight captures before writing a per-test slice

[vishnuv688]

What & why

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)

Notes for reviewers

Screenshots / recordings

[greptile-apps]

Confidence Score: 5/5

[Medium risk] Fixes trace capture timing for per-test slices.

The PR appears safe to merge based on the reviewed changes.

Findings

1.  Stuck metadata delays every test ▶

Summary

This PR waits for in-flight captures before writing per-test trace slices and uses newly recorded boundaries to keep later tests out of earlier slices. It also bounds WDIO's session viewport read and removes string-valued inline event handlers from replayed nodes.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Record slice boundary and capture index] --> B[Flush slice]
  B --> C[Wait for slice captures and session metadata]
  C --> D[Resolve next slice boundary]
  D --> E[Write bounded trace slice]
  E --> F[Finalization waits for pending work]
  F --> G[Write artifacts manifest]

Loading

_{Reviews (6) · Last reviewed commit: "fix(service): bound the viewport read so..."}

[greptile-apps]

Stuck metadata delays every test

If WDIO’s session-metadata driver read never settles, every per-test flush waits on that same promise for five seconds, even after an earlier flush timed out. Because the test-end hook awaits each flush, an affected suite incurs another five-second delay after every test instead of degrading once to fallback metadata.