Crowdhailer
Creator of Raxx
Testing Chunked responses from a phoenix endpoint using `Plug.Test` or `Phoenix.ConnTest`
I am implementing Server Sent events in a phoenix project. This is easy enough to do by using plug directly. I am following this gist.
However I am not sure of the best way to test such an endpoint. I could use HTTPoison Async Requests and connect to the test server but I would rather just test the conn object using Plug.Test or Phoenix.ConnTest. Is this possible are there any examples out there on how to do this.
Trending in Questions
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
Using Phoenix.LiveView.TagEngine as an EEx.Engine is deprecated!
To compile HEEx, use Phoenix.LiveView.TagEngine.compile/2 instead.
Sta...
New
Hello !
We want new/edit form pages to POST/PUT to their own URL rather than the resources REST defaults (post /things, put /things/:id)...
New
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app?
Looking for hints regarding:
Addi...
New
Hi all, I wanted to ask how the community is dealing with post-release steps.
Today we have Ecto migrations, which make sure that the db...
New
I am using Oban and occasionally, shortly after a deployment, a handful of jobs can fail because of dependency on other parts of the syst...
New
Other Trending Topics
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
I just stumbled on a newly redesigned elixir-lang.org. :tada: It looks like @Software_Mansion did the work, and I think it is generally a...
New
@hugobarauna and I (Alex Koutmos) have been hard at work on writing a book on Nerves that takes you from simply blinking LEDs to building...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #performance
- #security










Most Liked
Nagasaki45
I researched this a bit, and it’s indeed far from being trivial. From what I found, when we call
Plug.Conn.chunk(conn, chunk), plug callsconn.adapter.chunk. From there, the chunk should be sent to the server (e.g. cowboy) for further handling. The conn is not aware of the chunk anymore.In tests, the adapter is
Plug.Adapters.Test.Conn, and its chunk function reply with{:ok, payload}. It doesn’t really matter what the payload is, becausePlug.Conn.chunkis probably called from a process that is not going to finish / return this state in any way. This process communicate messages back to the client forever, in a loop.So, in the case of the test, I see no way to get the chunk out of the process, at least not in a “conventional” way. So, I tried to solve this by mocking
Plug.Conn.chunkto send a the chunk to the test process, and there Iassert_receivefor it. You can see an example here. It’s not the cleanest solution, I know… What do you think?zemuldo
I tried to get the method by @Nagasaki45 but I could not get it to work. I also tried mocking
Plug.Conn.chunkwhich also didn’t work for me I ended up doing this.I created a function with minimal side effects and used that to run the chunking.
Now in my controller, i call
chunk_to_conn(conn, current_chunk)which I can mock in test to give me the chunks like thisIn my test support
And in my test
AntoineAugusti
I am resurrecting this topic to share that you can test chunk responses if you follow the documentation for chunk. The test adapter collects chunks and updates the response body.
And in tests
Last Post!
linusdm
The setup you’re describing works because the chunks are being sent before your controller returns the
conn. So your test only gets a hold of the response after all chunks have been sent. If any of the chunks are being sent asynchronous, this won’t work. Your controller doesn’t really trigger that situation.I’ve come across the situation where the chunks are being streamed from a transaction, which takes some time. Then the chunks are only sent after the controller has returned the
conn. In that case, the chunks are not available yet in the test.I resorted to using a real http client (req) from tests to obtain the complete response (req then does the waiting and accumulating of the whole body). It required some fiddling with cookies to ensure the request was authorized though.