vim-test VS vim-jumpsuite

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.

Oh, you're in luck because I've actually written this exact plugin, it's called vim-jumpsuite. It is personally one of my special weapons that's becoming completely indispensable for me.

vim-jumpsuite: parses python tracebacks and identifies the most "interesting" part of the stack to create a jump list; despite vim being in the name, the python part of the plug-in is usable with any editors that supports parsing grep/quickfix-style output

Here is link number 1 - Previous text "my"

vim-jumpsuite for creating a quickfix/loclist jumps out of unittest tracebacks

vim-test with lieryan/vim-jumpsuite

For more elaborate cases, I wrote a plugin that summarises python traceback into the quickfix list. vim-jumpsuite is designed to be used when writing unittest/pytest; for each failing test, it'll try to pick the three most important locations that you'll want to jump to. You can also configure certain files/functions to never be picked by vim-jumpsuite.

Plug: one of the most valuable plugin for me are the vim plugin that I wrote myself: lieryan/vim-jumpsuite. It's a plugin to quickly jump to "interesting" line of code from your test suite by converting unittest reports to a Quickfix jumplist. The plugin uses some customizable heuristics to find the lines from tracebacks that are most likely to be most useful to your code.