So this was HELPFUL

however if you could present the websites as simply directions for

MAC OSX and then UBUNTU thatd be TONS simpler :D

theres a good bit of info and i think it would be much clearer if these were broken into 2 separate pages

not to mention this tutorial ACTUALLY works and the guy publishing his book on www.railstutorial.org could use a working one

i say chop it in two and give him a message ... bc his current one @ this website called "automate everything" just doesnt work.

-toodles!

Check out http://groups.diigo.com/groups/rubyonrails

It's useful. Thanks! ;-)

Merci! Félicitations pour ton blog, le design est super élégant! Il ne te manque qu’une CSS pour le code en Ruby, tu peux t’inspirer de http://blog.wolfman.com/articles/2006/05/26/howto-format-ruby-code-for-blogs

Thanks!

Congratulations for this guide! I have also posted some instructions to install & configure rspec 0.9.0 beta2 + ZenTest 3.5 on my blog

Jean-Michel

Great tutorial!

I noticed a typo: “If these conventions are not your cup of tea and you have your owns, the next paragraph explains how to configure Autotest so that it runs the whole test suite each time you save a file.”. Should be “own”.

Also, if one visits /getting_started_with_autotest/ with a trailing slash, then the comment links will point to /getting_started_with_autotest/getting_started_with_autotest/comments which obviously doesn't work.

Thanks for the autotest guidance - it was helpful

Excellent overview—thanks.

By the way, I find sometimes when I make a mistake Autotest spews a huge stacktrace onto the console. Picking apart the trace to find the error breaks my flow. Happily Autotest is well written and it was easy to solve this problem

When I run autotest it print the letter E to the screen, I’m guessing this means Exception because it I run the full test with Ctrl+C I get an error about Broken Pipe and notify_listen. I see some bug fixes regarding Pipes but I only installed the gem today, so should have the latest version...

Many thanks, K.

Favorited this one, dude

The ubuntu code will not work for rspec tests—> Working version

For people looking to setup autotest and snarl on windows I have written a simple step by step instructions here

For the ruby stand alone project. The class names need more details.

At the moment your article states " Test class names must start with Test"

Which is true, but you will get this error.

Unable to map class TestThingy to a file.

To avoid this you need

Test class names must be Test{ClassName}"

Just for completeness: RSpec and RedGreen don't work together. To get coloured output for RSpec running on its own you can pass a --colour option. But within AutoTest you have to pass it via an options file instead. This (and any other options you need) have to go in spec/spec.opts. This path is hard-coded.

Ben