sevensoft comments

"pretty print your behavior" by James Hughes

Mon, 22 Sep 2008 08:18:21 +0000

Excellent stuff.

"RSpec 1.0 tutorial - before and after" by sevensoft

Fri, 25 May 2007 01:15:30 +0000

You are completely correct and I weighed that option before posting it but left it in just for the sake of the example like you said.

Perhaps I could have noted that in the article. Might go update it just to make sure that is clear..

btw.. being somewhat newish to the ruby/rails world It took me a minute to realize the benefit of RSpec. I couldn’t grasp why anyone would come up with another xUnit type framework. By the time I read a little further on the RSpec site it was perfectly clear that this (if nothing else) is a phenomenal way to approach testing and get documentation all in one shot. DRY indeed.

So to you and your developers a hearty ‘Thumbs up’ for turning a good development concept on its side and making it fun and useful.

Now i’m looking for ways to fit this into my corporate J2EE worklife via JRuby.

Thanks for the comment btw.

"RSpec 1.0 tutorial - before and after" by Aslak HellesÃ¸y

Fri, 25 May 2007 00:59:08 +0000

Hi, and thanks for writing the intro.

I realise it was probably just for the sake of the example, but I just want to mention that defining an after(:each) block to reset instance variables is discouraged.

Each example (instance) runs in a new instance anyway, and the instance variables are garbage collected.

The after(:each) here has no effect, and since it has no effect, doing it is confusing.