bokner
Hello everyone,
I’m trying to run ExUnit tests from the shell, and I almost got it working:
iex(2)> ExUnit.start(autorun: false)
:ok
iex(3)> test_file = "test/sample_test.exs"
"test/sample_test.exs"
iex(4)> Mix.Compilers.Test.require_and_run([test_file], ["test"], formatters: [ExUnit.CLIFormatter])
........
Finished in 3.6 seconds
8 tests, 0 failures
{:ok, %{excluded: 0, failures: 0, skipped: 0, total: 8}}
So far so good, but the second run of Mix.Compilers.Test.require_and_run/3 doesn’t seem to do anything:
iex(5)> Mix.Compilers.Test.require_and_run([test_file], ["test"], formatters: [ExUnit.CLIFormatter])
Finished in 0.00 seconds
0 failures
{:ok, %{excluded: 0, failures: 0, skipped: 0, total: 0}}
It looks like the test compiler caches the test results. If that’s the case, can it be forced to invalidate it and run the tests from scratch again?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Catch errors, track performance, monitor hosts and more.
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.
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
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!"
First 7 of 7 Posts
Ninigi
Wild guess here, but I think
require_and_runmight check if all the files are required, and then chain it with a literal&&- so if the files are already required, it might returnfalseand the second part would not be executed.Like I said, idk, but it makes sense to me.
EDIT: Maybe the second time just run
.run? Another wild guess.EDIT2: and just because I am curious, why do you need this?
bokner
Did you mean ExUnit.run ? Unfortunately, it didn’t help.
There are currently 2 reasons as to why I want to do this:
Ninigi
Unfortunately I don’ t really know what you are talking about - but it sounds like a CI Server.
I like to actually be in charge of when to deploy updates or upgrades (which is something a UI server should consider.)
Kind of weird that nobody has implemented anything yet, but I guess you are on your own for now.
axelson
Interesting idea! Mix tasks don’t re-execute by default. Try running
Mix.Task.clear/0before require_and_run (docs: Mix.Task — Mix v1.20.2)bokner
Thanks!
Unfortunately, no luck with
Mix.Task.clear/0.paulanthonywilson
I wanted to do this because of the apps I’m working in at the moment has a long startup time, making TDD painful. Someone pointed me to a solution based on https://olshansky.medium.com/testiex-easier-test-driven-development-in-elixir-761cd1a9f11 and it works like treat.
filipe
basically you have to load it again to rerun the test
or even better compile_file, since load_file is depricated
then you can rerun