Skip to content

Conversation

@solebared
Copy link
Collaborator

Why

guard with guard-rspec is a fine solution but presented a few imperfections:

  1. It would slow down over time; every automatically triggered run would take slightly longer.
  2. By default it uses a 1 to 1 mapping of spec to app code. This is often a good choice, but i often want to run a set of specs as i make related changes. This is difficult to achieve with guard.
  3. It has a non-trivial configuration scheme. This is not often a problem since plugin gems usually generate configuration for us, but when we do need to tweak something, there's a significant api to learn.

rerun is a much simpler tool that addresses all of the above.

Outstanding Questions, Concerns and Other Notes

I'm not aware of any core/recent contributors using guard, but if anyone is, we can certainly keep it alongside rerun.
In fact the latter doesn't even need to be in the project Gemfile; there's just a slight advantage to putting such tooling in here to reduce external tooling (eg in a docker container).

@solebared solebared requested a review from h-m-m September 28, 2020 01:27
Copy link
Collaborator

@maebeale maebeale left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@solebared solebared merged commit 8e59c53 into main Sep 30, 2020
@solebared solebared deleted the replace-guard-with-rerun branch September 30, 2020 02:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants