vim-ultest VS telescope.nvim

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.

for telescope.nvim (optional) live grep: ripgrep find files: fd

Here we have a configuration for telescope.nvim, a very popular fuzzy finder.

EDIT: I found what I was looking for https://github.com/nvim-telescope/telescope.nvim and https://github.com/nvim-telescope/telescope-file-browser.nvim

Fuzzy Finder: fzf.vim (for its speed) along with telescope.nvim (for its ecosystem)

Just landed on Telescope.nvim: https://github.com/nvim-telescope/telescope.nvim/pull/2572

This extension allows you to use the power of ast-grep to find code patterns in your editor, using the familiar and awesome interface of telescope.nvim.

telescope.nvim

My solution is using telescope.nvim with lsp extension, and map the vim.lsp.buf.definition keybinding to telescope one https://github.com/nvim-telescope/telescope.nvim