nvim-config VS vim-ultest

client.lua server.lua

I have a configuration that is mostly Vim script. This might be an unpopular opinion, but Vim script actually a good language for what it was designed for. That being a configuration language for a text editor.

Here it is: https://gitlab.com/HiPhish/nvim-config

I have written my own :Debugpy command which lets me call the command like :Debugpy module foo.bar herp derp. I haven't made it into a plugin yet, it still needs a bit more polish to be of general use, but it's good enough for everyday use to me. You can find the code here, but as I said, it's really just written for myself, the usefulness might vary for others: https://gitlab.com/HiPhish/nvim-config/-/blob/master/plugin/debugpy.vim

How about https://github.com/rcarriga/vim-ultest ?

I have one that's half working for ultest. I haven't bothered to get the colors right.

vim-test & vim-ultest (also essential for work)

Vim-UltestHelps to debug quickly and easily

But I haven't yet set up anything properly other than Debugpy. nvim-dap is very barebones, so I feel that the best way is to have an extra configuration plugin on top. Debugpy.nvim is a very specific frontend plugin, but there are also more general plugins like nvim-metals and vim-ultest which also offer integration with nvim-dap.

Love seeing my plugins in the wild! Just FYI for anyone reading vim-ultest has an integration with nvim-dap which allows you to write debugging configs for any language and debug tests. There are currently recipes for python and go but I'd love to see more added! https://github.com/rcarriga/vim-ultest/wiki/Debugging-Recipes

Another thing I use for tests is https://github.com/rcarriga/vim-ultest which allows running the test and seeing the output inside vim, which works quite nice once I have narrowed down the test file that has the failing test.