cargo test
does not give any warning when the specific test case does not exist
#14813
Labels
C-bug
Category: bug
Command-test
S-blocked-external
Status: ❌ blocked on something out of the direct control of the Cargo project, e.g., upstream fix
Problem
If I run
cargo test xxx
when xxx does not exist. cargo does not give any warning but output a bunch of green output.For example. I have a test case
test_foo
. Every time I change foo I run this test case by runningcargo test test_foo
. Then I change the name fromtest_foo
totest_foo_
and forget to change the test command(For example, by using bash history). So every time I run cargo test I still got a bunch of green output which make me take the test as passed for granted, causing more confusion in the future.Steps
cargo test xxx
xxx is a non-existing test case
Possible Solution(s)
Give warnings if the test case does not exist.
Notes
No response
Version
The text was updated successfully, but these errors were encountered: