I've seen that sometimes the test functions are directly in the module that gets tested and not a nested module. I guess the lint isn't applicable in that case.

Could you elaborate? Maybe showing a module tree

Is anyone looking into this?

Could you elaborate? Maybe showing a module tree

Something like that

struct Foo;

// test `Foo` in the middle of the file 
#[cfg(test)]
#[test]
fn test_foo() { todo!() }

struct Bar;

// test `Bar` in the middle of the file 
#[cfg(test)]
#[test]
fn test_bar() { todo!() }

// ...

Oh I didn't know you could do that, we could just limit this lint for items in a module containing test in its name, kind of like https://rust-lang.github.io/rust-clippy/master/index.html#module_name_repetitions

i personally don't see a point to the test_ prefix even if it isn't in a module containing test in the name.

if the function is a test, we can see

#[cfg(test)]
#[test] // it says test right here. it's the same thing, just moved up a line.
fn foo_works() { todo!() }

so it's obvious in the code. and when we run tests, we see

test foo_works ... ok

so cargo test output already adds a test at the beginning. plus, you just ran cargo test so it should be obvious that the functions you're looking at are tests.

@rustbot claim

@Caylub are you still working on this? If not, I'd like to give it a try (starting with the review comments in your PR).

@farazdagi Yeah, this is my bad, I opened this with good intentions, and never followed through.

Feel free to pick this up!

Thank you!
@rustbot claim