Weird filter behavior if module is named tests

[ede1998]

I read in another issue (#123) that integration tests are automatically excluded from coverage reports while unit tests are not (so far).

This lead to a situation that had me very confused at first:
I have a module named tests in my crate that contains tests and test helper code.

Actual behavior:
The submodules of the tests module are ignored in coverage reporting but tests.rs is not.
My assumption is that it's probably because of the filtering for integration tests.
I was very confused at first and thought the coverage collection is not working properly or sth.

Desired behavior:
Either ignore all of the unit test code or none of it.

Minimal example:

src/
├── lib.rs
├── tests
│   └── example.rs
└── tests.rs

src/tests.rs

mod example;

src/tests/example.rs

fn hello_world() {
    println!("Hello");
}

src/lib.rs

mod tests;

[taiki-e]

Both readme and top-level comment of #123 says:

cargo-llvm-cov excludes code contained in the directory named tests from the report by default

Excluding tests.rs is proposed in #123 (comment) and I agreed with it in #123 (comment), but no one has implemented it yet. PR to implement it is welcome.

[ede1998]

Good to know. Don't have the bandwidth for the PR atm.

I didn't find a reference to the default exclusions in the README btw.

(And I assumed the top-level comment was referring to the tests directory for integration tests because it is named along side examples.)

One such that just popped in my mind: Is there a way to un-exclude the tests module? When I quickly tried it out, I didn't find a way.

[taiki-e]

I didn't find a reference to the default exclusions in the README btw.

One such that just popped in my mind: Is there a way to un-exclude the tests module? When I quickly tried it out, I didn't find a way.

Now documented by 8e02736. See https://github.com/taiki-e/cargo-llvm-cov?tab=readme-ov-file#exclude-file-from-coverage.