guard-minitest VS Guard

Since we use the minitest framework, my work guard setup includes the guard-minitest plugin. Guard supports a great range of plugins; this was another reason it appealed to me compared to solving this problem completely from scratch. I wanted to get something pulled together relatively quickly so I could try this workflow out after all.

Guard is a Ruby gem that can be used to run test cases automatically when source files change. For example, with guard-minitestand a simple Guardfile, you can run tests as the files are modified.

Text and file processing. Everything from parsing log files and generating reports, to watching folders with the Guard library and doing things with the files.

Perhaps using guard you can automate that https://github.com/guard/guard

It seems like where you are, devs are pushing code that fails in the CI/CD pipeline, which means, if your test suite isn't flakey, they aren't running tests locally. I had this problem too. I work on a rails monorepo, so I use the guard gem to automatically run certain tests when certain files are changed. There should be an analagous tool in whatever language/framework env(s) you're working in.

You should definitely use something more polished like Guard but you could also experiment with a "simpler" approach.

Check out https://github.com/guard/guard and https://github.com/guard/guard-rspec (if you're using rspec)

Probably https://github.com/guard/guard

Installation guide for guard

Now, consider this a mea culpa, as I know there are many ways this could go wrong. The guard documentation was also kind enough to warn me as such. This is, for better or for worse, my first attempt at building out a way to TCR in Rails. I’m excited to be able to follow up as I spend more time with my monstrous guardfile and this workflow so I can let you know how it goes.