search

locriani / magmawiki

A wiki.
magmawiki.com
Other
13 stars 2 forks source link

Use guard instead of autotest? #4

Closed NobbZ closed 12 years ago

NobbZ commented 13 years ago

Hi!

Since I am using guard for my private projects, I got a hang on it :D

But I really think besides personal preferences, it is worth the discussion.

guard is a small ruby tool, that watches the files in the application and starts its submodules on certain changes. guard is hosted on github and can be found there --> https://github.com/guard/guard

Autotest only runs tests, feautures and specs. Guard is able to do much, much more like restart the dev server on config changes (guard-rails), it can install new Gems when Gemfile was updated (guard-bundler) and even run specs (guard-rspec) or features (rspec-cucumber)

All thinks that make development much more fluid (I think).

If you have use for them, there are much more guard modules (https://github.com/guard/guard/wiki/List-of-available-Guards), perhaps you can find a way to use them, that I missed so far.

NobbZ commented 13 years ago

I did conversion from autotest to guard in my feature/guard-branch, but cant find pull request button...

You could take a look at it, or just leave it alone, but please tell me your decission :D

NobbZ commented 13 years ago

Sorry for close, hit the wrong button :D

locriani commented 13 years ago

I'll look into this. Shortly, I will soon have more free time!

epitron commented 13 years ago

OPEN ISSUE.

locriani commented 13 years ago

It's far too easy to press the Comment & Close button. Github should make it red or something :/

epitron commented 13 years ago

Yeah.. Especially since "Close" usually means "Close this window", not "NEVER SEE AGAIN".

PManager1 commented 12 years ago

I moved to guard

locriani commented 12 years ago

Guard is default on develop.