Clippy lints / Restriction
Clippy lint · Restriction · checked with Clippy 0.1.99
clippy::tests_outside_test_module: Triggers when a testing function (marked with the #[test] attribute) isn’t inside a testing module (marked with #[cfg(test)])
What it meansTriggers when a testing function (marked with the #[test] attribute) isn’t inside a testing module (marked with #[cfg(test)]). It is in the restriction group and off by default.
Does it matter?
The idiomatic (and more performant) way of writing tests is inside a testing module (flagged with #[cfg(test)]), having test functions outside of this module is confusing and may lead to them being “hidden”.
Lints that forbid language features for specific codebases (no unwrap, no indexing...). Off by default; pick them one by one, never the whole group.
How to fix it
Clippy does not fix this one automatically. Change the code by hand:
Flagged
#[test]
fn my_cool_test() {
// [...]
}
#[cfg(test)]
mod tests {
// [...]
}
Write this instead
#[cfg(test)]
mod tests {
#[test]
fn my_cool_test() {
// [...]
}
}
Turn it off, or on
It is off by default. To use it, set it to warn or deny:
Whole crate (Cargo.toml)
[lints.clippy]
tests_outside_test_module = "warn"In code
#![warn(clippy::tests_outside_test_module)]One run
cargo clippy -- -W clippy::tests-outside-test-moduleThe [lints] table needs Rust 1.74 or newer. In a workspace, put it under [workspace.lints.clippy] and add [lints] workspace = true to each member.
Clippy's own documentation
What it does
Triggers when a testing function (marked with the #[test] attribute) isn’t inside a testing module
(marked with #[cfg(test)]).
Why restrict this?
The idiomatic (and more performant) way of writing tests is inside a testing module (flagged with #[cfg(test)]),
having test functions outside of this module is confusing and may lead to them being “hidden”.
Example
#[test]
fn my_cool_test() {
// [...]
}
#[cfg(test)]
mod tests {
// [...]
}
Use instead:
#[cfg(test)]
mod tests {
#[test]
fn my_cool_test() {
// [...]
}
}
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- unwrap_usedChecks for .unwrap() or .unwrap_err() calls on Results and .unwrap() call on Options
- module_name_repetitionsDetects public item names that are prefixed or suffixed by the containing public module’s name
- expect_usedChecks for .expect() or .expect_err() calls on Results and .expect() call on Options
- string_lit_chars_anyChecks for <string_lit>.chars().any(|i| i == c)
- string_sliceindexing into a string may panic if the index is within a UTF-8 character
- suspicious_xor_used_as_pow`^` is not the exponentiation operator
- todo`todo` should not be present in production code
- try_errreturning an `Err(_)` with the `?` operator
- undocumented_unsafe_blocksChecks for unsafe blocks and impls without a // SAFETY: comment explaining why the unsafe operations performed inside the block are safe. Note the comment must appear on the line(s) preceding the unsafe block with nothing appearing in between
All 847 Clippy lints · Rust compiler errors · Cargo.toml checker
Up next
Related lintclippy::unwrap_usedChecks for .unwrap() or .unwrap_err() calls on Results and .unwrap() call on OptionsRead it next →Did this answer your question?