vim-textobj-entire VS vim-ultest

I agree that ggVG is fine but not with the custom leader to copy to clipboard part. If you're gonna have to remember something might as well use a text object instead, that way you get the full range of actions and not just the hardcoded mapping. I use kana/vim-textobj-entire that provides e for entire buffer, so copying would be yie and life is smooth. There's a bunch of text object plugins, just get one or write it yourself would be my advice.

I like the entire document text object: https://github.com/kana/vim-textobj-entire

You should make your life easier and get the entire text object plugin. This is the easiest way to act one the entire buffer with no surprises, although it still does change the cusror position sometimes, but I still recommend it.

kana/vim-textobj-entire - Make entire buffer available as a text object

I now use entire text object for this with vie, which is more mentally coherent, for me, than ggVG.

kana/vim-textobj-entire adds e as text object for entire buffer

die (delete in entire) with the plugin vim-textobj-entire

I would suggest adding the text object "entire", either by making your own omap, or using a plugin like vim-textobj-entire.

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.