on master help sign in
Document how to run tests (#6268)

Co-authored-by: Jonatan Pettersson <jonatan.pettersson@proton.me>

commitf435f3b2e973ab71b6e110a5b6327a6ac0cfa2be authorJonatan Pettersson <jonatan.pettersson@pm.me> dateSat 11 Mar 2023, 15:03 (4 years ago) parentbb72079
1 file changed+7−1
docs/CONTRIBUTING.md+7−1
docs/CONTRIBUTING.md+7−1
@@ -33,7 +33,13 @@ inside the project. We use [xtask][xtask] as an ad-hoc task runner and
3333thus do not require any dependencies other than `cargo` (You don't have
3434to `cargo install` anything either).
3535
36−# Integration tests
36+# Testing
37+
38+## Unit tests/Documentation tests
39+
40+Run `cargo test --workspace` to run unit tests and documentation tests in all packages.
41+
42+## Integration tests
3743
3844Integration tests for helix-term can be run with `cargo integration-test`. Code
3945contributors are strongly encouraged to write integration tests for their code.