eileennoonan
How do I use Req.Test stubs with Poolboy?`
I’m making HTTP requests from inside a Poolboy pool.
I’m having a hell of a time trying to use Req.Test stubs in ExUnit in an e2e workflow sort of test.
Typically the error I get is:
** (EXIT from #PID<0.1312.0>) an exception was raised:
** (RuntimeError) cannot find mock/stub MyApp.WorkerStatusRequest in process #PID<0.1318.0>
I know that I need to use Req.Test.allow, but getting my test process pid into the code where poolboy runs has proven a challenge.
I’ve gone as far as trying to do an if Application.get_env(:my_app, :env_name) == :test do ... sort of check, using an agent to store a parent pid, but that feels hacky, plus it doesn’t allow me to configure my mocks for each individual tests. The more I try the more tangled of a mess I seem to make.
I can’t help but think there must be an elegant solution here. Can anyone point me to any examples?
Marked As Solved
wojtekmach
The mechanism described in Req.Test — req v0.6.2 is a sort of escape hatch I guess. Hope that helps!
Also Liked
jswanner
Are you writing the poolboy worker yourself? If so, you can set the :"$callers" in the process dictionary of the worker process, which is then used by the ownership mechanism in Req.Test.
def start_link(opts) do
opts = Keyword.put_new(opts, :callers, Process.get(:"$callers", []))
GenServer.start_link(__MODULE__, opts)
end
def init(opts) do
{callers, opts} = Keyword.pop(opts, :callers)
Process.put(:"$callers", callers)
# ...
jswanner
Glad you got it to work!
I should have mentioned that setting callers would mean you wouldn’t need to allow the poolboy worker, but you might need to allow whatever is starting the worker (or pass the callers through whatever process that is) if that’s not happening in the test process itself.
Popular in Questions
Other popular topics
Latest on Elixir Forum
Sponsor Spotlight
Develop your skills with books, videos, and courses.
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
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Real-time error tracking, performance insights, and observability for devs.
Practical resources that improve the lives of professional developers.
Enabling companies to succeed by building software people love.
The deployment platform built for Elixir: PaaS ease, VPS control.
Courses that'll move you from confusion to "Aha, now I get it!"