[neotest] Hide folder/filenames + don't show folders/modules containing no tests

[DragonDev1906]

Checked other resources

• This is not a bug report or feature request (Please use issues for those).
• This is a question about rustaceanvim, not rust-analyzer or Neovim.
• This is not a question about autocompletion.
• I have read the README.
• I have read the FAQ.
• I have searched for a solution using :h rustaceanvim.
• I have searched existing discussions.
• I have searched the existing issues/discussions of other plugins related to this question (if applicable).
• I have searched the existing rust-analyzer discussions (if applicable).
• I have added a very descriptive title to this question.

Description

I'm not sure if this belongs here or with neotest, but since rustaceanvim is providing the list of tests, I think it belongs here.

For the neotest summary: Is there a way to:

• Only use module+function names and remove the folder+filename entries, making the output more compact+readable (I don't need to know a test is in src for example) (3, 4)
• Disable/Hide files/modules that do not contain any tests (might already be the case if folders+filenames are gone)? (1) (2)

I couldn't find any configuration (neither here nor in neotest) to do this.

Context

rustaceanvim.neotest has a lot of redundant information (at least for me, especially in a multi-crate workspace):

1. The summary of neotest (require("neotest").summary.toggle()) lists files that do not contain any tests (without any indicator that this is the case)
2. Files without tests are continuously spinning, but no cargo test process is running, there is nothing to test and the first line indicates all tests have passed.
   
3. In the following file layout the module names show up twice (only one contains tests), with a redundant naming scheme (could be the case with other situations, too):

./src
./src/accesscontrol
./src/accesscontrol/tests
./src/accesscontrol/tests/rule.rs
./src/accesscontrol/tests/check.rs
./src/accesscontrol.rs

// accesscontrol.rs
#[cfg(test)]
mod tests {
    mod check;
    mod rule;
}

4. Often there is the filename, followed by the module name, which is exactly the same:
   

---

Ideally the summary output would be like this (only crate, module and test function names, combined where possible):

rustaceanvim  132  132  0  0  0 
crate_name
    module_1
        inner_mod1
            test_name
        inner_mod2
            test_name
    module_2
// Compressed format (only one child module/test)
second_crate::module::inner
        test_name

// Example from the screenshots
// cli crate doesn't show up because there are no tests
crate_1
    access_control::tests
        check
            secret
            preimage
            // ...
        rule
            // ...
    // ...
// Compressed if there is only one module with tests
crate_2::compatibility_test
        operator_response_compatibility
        // ...

Example Code

-- Sorry for no minimal example, but I think this happens with the default configuration, too.
require("neotest").setup({
    adapters = {
        require("rustaceanvim.neotest"),
    },
})

Neovim version (nvim -v)

v0.11.1

Operating system/version

Arch

Output of :checkhealth rustaceanvim

==============================================================================
rustaceanvim:                           require("rustaceanvim.health").check()

Checking for Lua dependencies ~
- ✅ OK optional dependency nvim-dap not installed. Needed for debugging features [mfussenegger/nvim-dap](https://github.com/mfussenegger/nvim-dap)

Checking external dependencies ~
- ✅ OK rust-analyzer: found rust-analyzer 1.86.0 (05f9846 2025-03-31)
- ✅ OK Cargo: found cargo 1.86.0 (adf9b6ad1 2025-02-28)
- ✅ OK rustc: found rustc 1.86.0 (05f9846f8 2025-03-31)

Checking config ~
- ✅ OK No errors found in config.

Checking for conflicting plugins ~
- ✅ OK No conflicting plugins detected.

Checking for tree-sitter parser ~
- ✅ OK tree-sitter parser for Rust detected.

[mrcjkb]

Hey 👋

The underlying issue is that neotest's adapter interface requires the implementation of an is_test_file function.

This doesn't work with rust, because any file could contain test modules. You'd have to read and parse the file (not great for performance) to determine if it contains test modules.
Because I don't want that complexity and potential performance issues in rustaceanvim, I decided not to do that. And that's why the neotest summary output doesn't work great with rustaceanvim's neotest adapter.

I'm fine with that - I've never needed the summary because I never use neotest to run the whole suite (I use Nix for that). So I won't put any energy into fixing this.

If someone wants to contribute, you're more than welcome and I'll be happy to review and guide.
Just keep in mind that parsing files should at least be behind a configuration option (disabled by default). And don't assume the tree-sitter parser for rust is installed.

[DragonDev1906]

Thank you for the quick reply.

This doesn't work with rust, because any file could contain test modules

Which probably requires always returning true, which neotest probably interprets as "Please display this". I see.

Doesn't rust-analyzer provide a way to list files that actually contain tests?
It seems to be able to do so for a single file (see runnables and testables), thus indicating whether there are tests.
And it looks like there is an (experimental) way to get a list of all tests (including their filename): https://rust-analyzer.github.io/book/contributing/lsp-extensions.html?highlight=tests#test-explorer.

I never use neotest to run the whole suite (I use Nix for that). So I won't put any energy into fixing this.

Nix as in the package manager? I'll probably continue to use bacon + cargo-nextest then (at least for running all tests).

[mrcjkb]

Doesn't rust-analyzer provide a way to list files that actually contain tests?
It seems to be able to do so for a single file (see runnables and testables), thus indicating whether there are tests.

It gives you a list of runnable targets. Querying rust-analyzer for each file that neotest requests would be worse for performance than parsing them.