Is using the gem Guard still state of the art in TDD with Ruby?

• retest

  6 118 7.4 Ruby

  A simple CLI to watch file changes and run their matching ruby specs. Works on any ruby projects with no setup.

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.

• entr

  47 4,002 6.8 C

  Run arbitrary commands when files change

I use entr instead. It works for more than ruby

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• binks

  1 3 0.0 JavaScript

  An (opinionated) test runner for rspec & cucumber

• vim-test

  40 2,898 7.5 Vim Script

  Run your tests at the speed of thought

  

Nothing wrong with guard, but I would lean towards getting familiar with editor integrations. Personally I use vim-test.

• rerun

  4 967 0.0 Ruby

  Restarts an app when the filesystem changes. Uses growl and FSEventStream if on OS X. (by alexch)

I use rerun to rerun all tests on file change (retest gem posted elsewhere can be smarter about which tests to run). Rerun also lets me relaunch a development app on changes.

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

Suggest a related project