Fl4m3Ph03n1x
I always thought that the default value for ExUnit.Case, async was true. However in a recent video from ElixirCasts the author states otherwise:
Am I mistaken?
Do I need to use ExUnit.Case, async: true if I want concurrent tests?
I couldn’t find anything in the official docs:
Where Next?
Trending in Questions
Other Trending 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
- #blog-post
- #phoenix_html
- #iex
- #ai
- #graphql
- #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.
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 5- Show Best Posts
- Show All Posts (oldest first)
- Show All Posts (newest first)
lpil
Looks like it default to
falseelixir/lib/ex_unit/lib/ex_unit/case.ex at 3a3d68385ef02148136ff4b9490c70d3e6d3dbc3 · elixir-lang/elixir · GitHubpeerreynders
ExUnit.Case — ExUnit v1.20.2
tmbb
It defaults to
falselike it should. Elixir doesn’t know whether your test depends on some possibly hidden global state or not. Havingasync: truecould cause some of your tests to fail in unpredictable ways which would be hard to debug.lpil
I’d prefer it to default to concurrent, to nudge us into writing code that is safe to run concurrently by default
hauleth
The problem is that
async: truedoes something different from what people may expect. Tests in single module are always run synchronously, no deviations.async: truemean that tests in given module can be ran in parallel with other modules. So this would produce unexpected results when used with some persistent storage tools, when used without special preparations, or other hard to reason problems. Instead they have chosen to “safer default”. If you want to check your code for concurrency errors then you can check out Concuerror.