-
Notifications
You must be signed in to change notification settings - Fork 483
What people say about Guard
Here's how Guard has helped others:
"For dev and devops, I use Vim, TMux and Guard. Productivity is through the roof - no more "typing in" commands. I just open a file, edit and hit save - Guard does everything else (building, testing, deploying, etc.)."
Cezary Baginski [email protected]
"I've been a user of Guard from the moment I discovered it, it really improved the ease with which I could test. Guard's tests are also a boon to developers who want to see a good canonical example of testing. I often just browse the files to learn something new. Also the Guard maintainers are awesome, and will answer questions from new users."
Daniël W. Crompton (@webhat) [email protected]
"Like the previous testimonial from Daniël, I've been using Guard for testing from the moment I discovered it. I use it with Minitest for doing Test-Driven Development (TDD) with Guard running the associated test file automatically upon saving. It's just a great workflow. A heartfelt 'thank you!' to the Guard creators and maintainers."
Jon Atack (@jonatack)
"guard-rspec greatly reduces the time from code change to test feedback, providing a fluid development experience."
Kris Leech (@krisleech)
(Feel free to add a snippet about your own experiences with Guard above.)
This wiki and the Guard README document contain a lot of information, please take your time and read these instructions carefully.
If you run into any trouble, you may start by understanding how Guard works.
We provide detailed changes for each Guard release.
Be sure to read the CONTRIBUTING guidelines before reporting a new Guard issue or open a pull request.
If you have any questions about the Guard usage or want to share some information with the Guard community, please go to one of the following places:
- Google+ community
- Google group
- StackOverflow
- IRC channel
#guard
(irc.freenode.net) for chatting