benonymus
Hey,
I am using this mocking library:
https://github.com/jjh42/mock
and I am experience something weird:
I have 2 test cases in 2 different folders in the test folder that mock the same function and then asserts that this function has been called.
with_mock(CoolModule, do_something: fn _ -> :ok end
and then at the end
assert_called(CoolModule.do_something(2))
One of the tests, always the same fails if I run the tests together.
If I run the failing test by itself then it passes, or if I comment out the other test that also makes the test pass.
If I put a sleep in the failing test that also makes it pass.
I have async: false set on the test module.
According to the docs of Mock this should work.
Any ideas why this could be?
Thanks
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
We build reliable cloud platforms for business-critical systems.
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
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex
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.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
Enabling companies to succeed by building software people love.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First 2 of 2 Posts
thbar
Hi!
The best advice I can provide here is to, if possible, switch to using behaviours and Mox, following the advice outlined in Mocks and explicit contracts - Dashbit Blog, because this allows to keep async tests, and uses per-process expectations (even if it can be a bit harder to use in some contexts, in my experience), with clear boundaries.
On your specific question, also, without more code it will probably be a bit difficult to provide some help. If you have a way to share a smaller reproduction (and I know it can be hard to do), you will get more chance here! (or a bit more concrete elements).
al2o3cr
The overall vibe of these symptoms is “there is something leaking from the execution of one test and affecting the other test”, since they go away when run in isolation.
“If I put a sleep in the failing test that also makes it pass” sounds like a race: something that cleans up the first test is running in parallel with the second test, and if the second test beats the cleanup you get a failure.
I don’t see anything obviously asynchronous in the
mocksource - this issue mentions switching toExUnit.at_exitinstead ofafter, but the suggestion was not implemented.