@s1n7ax I think I made some progress, but I skipped using the LSP method to check if the file is a test file. Neotest heavily relies on the is_test_file method, when I used lsp for this, it made everything really slow (i mean project scan etc). So, I tried to set up the other stuff. (however, when I tried, the folder filter method didn't work well, so lot of wrong files were sent to to the server)

project repo. It's depends on the nvim-java-test and nvim-java-core project, I added a separate logger to it for better debugging.

Currently, I'm not sure if it's fully async, and I don’t really know the proper way to check it, so I hope you can help with this too.
working features:

run/debug : folder/class/method.

limitation:

With the new neotest version, the project is duplicated in the tree view (fully scanned two times). I think its related to this - pr, but I haven't looked into it yet. (this pr enables the watch feature)

For the treesitter query i used the neotes-java project

I'm curious what you think about it.

Uh oh!

POC: neotest integration #97

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions