-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Add mix test --dry-run flag #14499
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Nezteb
wants to merge
3
commits into
elixir-lang:main
Choose a base branch
from
Nezteb:mix-test-dry-run-flag
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Add mix test --dry-run flag #14499
+63
−5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
0eadca6
to
64bb5e1
Compare
Nezteb
commented
May 15, 2025
Nezteb
commented
May 15, 2025
Nezteb
commented
May 15, 2025
Nezteb
commented
May 15, 2025
whatyouhide
reviewed
May 16, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, implementation-wise I think we might need to take a different approach. Right now, I see two main issues:
- We're not running
ExUnit.Formatter
s on dry runs—I think we might want to. Basically, the only thing we want--dry-run
to do is to literally skip executing the body of tests (+setup
/setup_all
calls and whatnot), but everything else would be the same. - We are printing test files, but this doesn't give us information about what tests (or test cases even, if there are >1 test cases in a file) would run. I think this is important. Think of using
--dry-run
to answer the question "if I pass this--exclude
option, how many tests will be skipped"?.
Do these points make sense? I am not even sure this is very feasible, so we'd need to sort of proof-of-concept this.
Nezteb
commented
May 16, 2025
d23bce5
to
56e03ed
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Aims to address #14393