Lines Matching refs:tests

129 include one or more tests to ensure that the crate does not regress in the future.
130 There are two ways to write tests: integration tests and documentation tests
131 (Tokio avoids unit tests as much as possible).
133 #### Integration tests
135 Integration tests go in the same crate as the code they are testing. Each sub
137 `tonic` utilities available to use in tests, no matter the crate being
141 integration tests in the crate and follow the style.
143 #### Documentation tests
146 use the API. Documentation tests are run with `cargo test --doc`. This ensures
149 The trick to documentation tests is striking a balance between being succinct
393 [documentation test]: https://doc.rust-lang.org/rustdoc/documentation-tests.html