Feedback on The RSpec Book (beta)
February 13th, 2009
Thank you to all who are participating in The RSpec Book beta program. We’ve already gotten some good feedback, and we look forward to more as we release updates over the coming weeks.
For those of you who are reading the beta and would like to provide feedback, there are two outlets for you on the Pragmatic Programmers’ site.
The errata page is for technical errors, typos, etc. Things that don’t really require any discussion and are simple, task oriented fixes.
Although the errata page lists Suggestion as a type of errata, the system provides no opportunity for a conversation. Therefore, if you are making a comment like “I’m not sure I agree with the statement on page 37” or “you say x here and y there, which is it?”, etc, then the forum might be a better option. That way I (or any of the authors) can throw questions back at you to get a better feel for what you’d like to see and how it might help.
Of course, we’d rather have your feedback than not, so if you’re not interested in such a dialog, go ahead and stick to the one-way-street of the errata page.
Again, thanks for the feedback thus far. You’re helping to make this a better book for everyone else who will read it.
February 13th, 2009 at 6:00 am
Just bought the book today and am about half way through. The examples so far are absorbing fairly well. I’m still looking for more info on the cucumber+rspec+ci. I want to get the whole write a Feature (cucumber), write the Spec, build the Code to go green all in a red/green fashion. Do you have any suggestions for a tight CI environment between the two? I was thinking a OSX Widget that shows projects with an expandable/scrollable results page would be totally sweet. Once I figure out an refine my own BDD process and if there isn’t such a widget yet, I think this might be a cool addition.
February 13th, 2009 at 6:00 am
Hey Nathaniel,
We weren’t really planning to cover CI in the book, but there is a lot of talk about it on the rspec-users mailing list