cargo test accepts conflicting test flags

[casey]

cargo test accepts multiple flags that specify which tests to run, but will only honor one of them. For example, cargo test --lib --doc seems to only run the doc tests.

I ran into an issue where cargo test was invoked with --lib --doc on Travis, with the intent of running both library and documentation tests, but library tests were skipped, leading to an accidental gap in CI test coverage.

I would suggest that both flags be honored, but just returning an error for conflicting flags also seems reasonable.

[stale]

As there hasn't been any activity here in over 6 months I've marked this as stale and if no further activity happens for 7 days I will close it.

I'm a bot so this may be in error! If this issue should remain open, could someone (the author, a team member, or any interested party) please comment to that effect?

The team would be especially grateful if such a comment included details such as:

• Is this still relevant?
• If so, what is blocking it?
• Is it known what could be done to help move this forward?

Thank you for contributing!

If you're reading this comment from the distant future, fear not if this was closed automatically. If you believe it's still an issue please leave a comment and a team member can reopen this issue. Opening a new issue is also acceptable!