Adam Figgins

No worries. Sure, I'll stick it on the todo list :)

@Drewfyre - Try https://github.com/Issafalcon/neotest-dotnet . I've not tested it on Windows yet, but hopefully this will become the adapter for dotnet testing. If it doesn't work, then it maybe more...

So I tried my adapter on Windows and discovering tests seems to just hang Neovim. Not had time to investigate, but I also tried the run commands of neotest directly...

I can confirm that this isn't just a C# tests thing. It occurs with the plenary adapter, the jest adapter and the python adapter, when neotest is used on Windows....

@rcarriga - So I think I have narrowed it down to a problem in lib/file.find.lua with the `find` function. The command (run using `fd`) and it's args all look OK,...

Nice one! That's done the trick to fix the test discovery issue. Looks like the correct tests are being returned in the summary pane (takes a couple of attempts -...

Thanks again for the quick updates! I gave it another go. The new file discovery seems to work a lot better with Windows, in that it now picks up all...

OK. So with a combination of your latest changes to neotest core @rcarriga , and a minor update to neotest-dotnet (see https://github.com/Issafalcon/neotest-dotnet/commit/8b4b5e452b1702ab94d5abca7023d13231694781), everything looks like it's working well on Windows...

Thanks @rcarriga ! Great work on this! 😃 I'll add an issue to the dotnet adapter to make sure it doesn't search unnecessary files. Just to clarify, when you say...

This symlink approach unfortunately doesn't work on Windows OS. To prevent Noevim plugin authors from unintentionally breaking plugins on Windows, a different approach will be required to allow this repo...