Problem
Application requests initiated inside the browser run outside the Pest test's PHP process, so their Laravel broadcasts are invisible to the current in-memory capture driver. This is a common end-to-end flow for Livewire and Inertia applications.
Scope
Research a deterministic cross-process capture path without turning the package into a partial Reverb/Pusher server implementation.
Questions to answer
- Can a lightweight local capture broker safely bridge the application process and Pest process?
- Can Playwright WebSocket routing provide the required behavior through a stable public Pest Browser API?
- How would parallel tests isolate captures and simulated socket IDs?
- What failure modes, cleanup, and security boundaries would the feature introduce?
Acceptance criteria
- Produce a design note with at least two approaches and their tradeoffs.
- Identify the required Pest Browser and Laravel extension points.
- Include an isolation strategy for parallel test workers.
- Make an explicit implement/defer decision before production code is added.
Problem
Application requests initiated inside the browser run outside the Pest test's PHP process, so their Laravel broadcasts are invisible to the current in-memory capture driver. This is a common end-to-end flow for Livewire and Inertia applications.
Scope
Research a deterministic cross-process capture path without turning the package into a partial Reverb/Pusher server implementation.
Questions to answer
Acceptance criteria