laravel-dev-tools VS neotest

In addition to that I use and somewhat maintain a blade language server https://github.com/haringsrob/laravel-dev-tools that gives me some useful blade autocomplete as well.

Already shared some earlier developments I did by making a blade specific LSP: https://github.com/haringsrob/laravel-dev-tools

You can give it a try with the instructions here: https://github.com/haringsrob/laravel-dev-tools

Nice. Might be good to add to the README what you intend to improve on: https://github.com/nvim-neotest/neotest?tab=readme-ov-file

What developer flow is complete without a unit test runner? For that work, I rely on Neotest. Neotest launches a Neovim buffer that sits on the side of my terminal. I don't have to pop up the summary. I can trigger Neotest in the background, get some notifications, and then move on. It also feels just like the other buffers I've mentioned above that can slide in and out as I need them.

My first neovim plugin project was to write an adapter (runner) for neotest, for a language that I use regularly and which was missing from the existing adapters.

There's overseer.nvim to run all sorts of things and neotest to run tests. In general, you can check awesome-neovim or TWiN to look for plugins.

Here's some things that may help: - https://github.com/mfussenegger/nvim-dap + dap ui - https://github.com/nvim-neotest/neotest

I use neotest to run tests (with pytest).

For testing I use https://github.com/nvim-neotest/neotest which gives a nice outline.

For those who don't know it, it's an adapter for neotest, a Neovim plugin that

You might look at how Neotest handles this, or even see if you can use/contribute to that project directly. It already has support for a fair number of languages at varying levels of maturity.