Skip to content

Integration with Neotest #298

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
marcinjahn opened this issue Mar 29, 2025 · 8 comments
Open

Integration with Neotest #298

marcinjahn opened this issue Mar 29, 2025 · 8 comments

Comments

@marcinjahn
Copy link
Contributor

Neotest is probably the most popular testing framework for neovim. I think it'd be awesome to integrate easy-dotnet's test running capabilities with neotest by adding an adapter for neotest.

@GustavEikaas
Copy link
Owner

There is already a neotest adapter for dotnet.
thre has been some discussion with the plugin owner on integrating some of the techniques and code used in this repo.

Issafalcon/neotest-dotnet#90

@marcinjahn
Copy link
Contributor Author

Right, but neotest-dotnet doesn’t perform too well with bigger codebases (not sure if easy-dotnet does actually, didn’t check it yet)

@GustavEikaas
Copy link
Owner

GustavEikaas commented Mar 30, 2025

Right, but neotest-dotnet doesn’t perform too well with bigger codebases (not sure if easy-dotnet does actually, didn’t check it yet)

Due to the adapter or could it be neotest itself?

If you find any perf issues feel free to make an issue, havent spent much time optimizing yet

@bosvik
Copy link
Contributor

bosvik commented Apr 2, 2025

I work on a large codebase, monorepo with 700+ tests and multiple solutions. neotest was completely unusable but easy-dotnet works perfect. Easy to switch between solutions, quick test recognition and correctly parsing the tests to filter out skipped tests. I see liitle or no performance hit in a solution with say 500 tests compared to a solution with 30. It takes a few seconds more to refresh the testrunner in the largest solution but that's expected.

@GustavEikaas
Copy link
Owner

I checked out neotest for a bit but i'm not sure if it's an alternative to the easy-dotnet testrunner or a different use-case entirely. Any neotest-dotnet users want to share their thoughts. Pros, cons and usecases for neotest and easy-dotnet testrunner?

@marcinjahn
Copy link
Contributor Author

marcinjahn commented Apr 4, 2025

The pros of neotest is that it’s not just dotnet, any other language integrated with it will have the same set of keybindings, UI, experience. Having completely separate tooling for dotnet tests is a bit unfortunate (although still awesome and really appreciated! 😄)

@GustavEikaas
Copy link
Owner

Yeah, language agnostic is a really strong argument imo. I've started dabbling a little bit with a neotest adapter. Just to get a better understanding of what it is and how it works. Will keep you guys posted

@GustavEikaas GustavEikaas pinned this issue Apr 7, 2025
@GustavEikaas GustavEikaas unpinned this issue Apr 21, 2025
@GustavEikaas
Copy link
Owner

GustavEikaas commented Apr 21, 2025

Ill have to downprioritize this and instead work on MTP support for the time being #322

I got as far that I had neotest working with hardcoded values, so it definitely seems possible to make a neotest adapter. However i'm not sure I want to. Should probably discuss it with neotest-dotnet maintainer and maybe do a collab

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants