Contributing: fix test command #4482
Conversation
Contributing.md
Outdated
| @@ -110,7 +110,7 @@ You can run these tests yourself with | |||
| `nox -s clippy-all` | |||
|
|
|||
| #### Tests | |||
| `cargo test --features full` | |||
| `nox -s test` | |||
There was a problem hiding this comment.
Is it potentially worth mentioning both options here? I tend to use cargo test to selectively run the ones I care about (and it's much quicker), though I agree most contributors would benefit from having this recommendation.
There was a problem hiding this comment.
There's also nox -s test-rust 😅
There was a problem hiding this comment.
But yes, for running a specific test cargo test is probably still best, I'll add a sentence.
Oh, and for adding a hint how to run Rust tests, is there a way to run a specific test from pytests?
There was a problem hiding this comment.
I think cd pytests && nox -s test -- -k <test> (the -k switch goes to underlying pytest execution)
There was a problem hiding this comment.
Or nox -f pytests/noxfile.py -s test -- -k <test> to avoid the cd.
Only "cargo test" does not run Python tests.
birkenfeld
force-pushed
the
contrib-fix
branch
from
e18782e
to
cd39179
Compare
|
Updated. |
Only "cargo test" does not run Python tests.