retest VS vim-test

Whatever you choose Retest (a gem I maintain) will acknowledge both naming conventions out of the box to increase the number of compatible Ruby projects. This is done in release 1.10.0. For example, you can now use Retest with Puma.

I created a gem: Retest which works on the terminal. A bit like Guard without any setup. The gem is smart enough to find the correct file to test after you save any.rb file.

I use retest. It works on every standard Ruby projects with no setup (understand no .Guardfile or Gemfile update). If you follow rspec, rails, rake or ruby standard file structure you get running in less than a minute. As a contractor I can checkout any repo and start TDD without caring about the repo setup. I use it even when Guard is already installed because the experience is consistent across all projects. It also has a —diff option that runs only spec files relevant from the diffs with another branch to run a final check before creating a pull request and triggering the whole test suite on CI.

But whatever the project I’m working on is, I always try using retest https://github.com/AlexB52/retest for awesome refactoring and TDD because it works with both Minitest and RSpec out of the box. Sorry for the shameless promotion.

Hi, I have created a gem called retest that helps you run specs after a file change without adding any configuration files to a repo. I created it for the specific reason you’re mentioning as I work in a consultancy. It is supposed to be dev centric and works with any ruby projects. I use it while working or refactoring. It might suits you, have a look

A great book by Sandi Metz is 99 bottles of OOP in Ruby where she explains heaps about refactoring. One of the best book I have read. I know you asked for article or videos but if you have time, it takes a day or two to read. I made a gem to help people refactor the same way she describes in the book. It will speed up your feedback loop when refactoring: retest

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.