dein.vim VS vim-test

For myself, I have only used Dein from the day I switched to Neovim and haven't switched since.

Dein: A super light and fast plugin manager

https://github.com/Shougo/dein.vim https://github.com/Shougo/shougo-s-github/tree/master/vim/rc See shougos vimrc for proper use

Plugins are managed with dein.vim

If you need inspiration, you can use vim-test as a reference. It's the Vim equivalent of neotest, written in Vimscript (doesn't support tree-sitter and diagnostics).

My plugin NeoTerm.lua supports "run test at cursor" out of the box with vim-test, i.e. zero configuration.

Vim test is great, supports a lot of frameworks and is easy to extend (with vi script) https://github.com/vim-test/vim-test

I am trying to set up the popular vim-test (https://github.com/vim-test/vim-test) plugin so that when I run tests they run on a tmux pane. vim-test uses a default strategy of running the tests via neovim’s built-in terminal. They also support many strategies which include running on a tmux pane.

I use https://github.com/vim-test/vim-test runs tests in a lot of languages. Very fast and clean output.

vim-test run your test with a simple mapping. Works with rSpec and Minitest (and dozens other languages)

I've made the move from vim to Emacs with Evil-mode for a little while now, but still miss https://github.com/vim-test/vim-test. I wonder if there's a port for evil-mode or if you know of something closer to it you can recommend. Thanks

One project that does a fantastic job on these two points is https://github.com/vim-test/vim-test Both adding new execution environments and test-runners can be done with minimal fuzz. Only thing is I would like a tutorial of how to add a new runner.