[Bug]: Browser Testing HttpServer does not send StreamedResponse to the client
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 11.7k
- Forks
- 538
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 8
Description
What Happened
When using Laravel's useStream composable (@laravel/stream-vue) with Pest Browser Testing, the streamed data bypasses the browser UI completely and is output directly to the terminal console where the Pest test is running.
Expected behavior: The UI updates incrementally as data streams from the server.
Actual behavior: The stream freezes in the isFetching state, the UI never updates, and the streamed data appears in the terminal console instead.
How to Reproduce
See the demo in the Sample Repository
Sample Repository
https://github.com/theo-vdml/pest-browser-use-stream/
Pest Version
4.3.1
PHP Version
8.4.16
Operation System
Linux
Notes
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the sample repository and reproduce the issue using the @laravel/stream-vue useStream composable with Pest Browser Testing. Trace how the Browser Testing HttpServer handles the streamed response; done means streamed data updates the browser UI incrementally, the stream leaves isFetching, and nothing is written directly to the test terminal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- laravel, php
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100