On Dec 20, 2008, at 4:38 pm, doug livesey wrote:

> To reiterate a point made several times on this list, we is all  
> *begging* for talks / courses on RSpec & Cucumber -- if anyone knew  
> of any, I'd be grateful if they could let us know.

Well I've kinda promised to do a session at NWRUG in Jan that will  
cover Cucumber at least, RSpec as well (in the sense of model specs)  
may be asking too much for a pre-pub presentation.

I'm gonna be pretty tied up with existing clients for the next couple  
of months, although I will be able to fit in one- or two-day sessions  
here and there to suit the needs of individuals, pairs or maybe small  
teams.  But not enough to prepare a training course as such.   
(Everything I've done so far has been on an on-demand basis, to solve  
the BDD needs of whatever projects people are working on.)

But I'm starting to think maybe I should work on a Cucumber-focussed  
BDD course, maybe 3 or 4 days long, like an intensive crash course.


> Myself, I use & love RSpec, but have made no inroads into Cucumber  
> -- I wish there were some best practices out there!

"Best practices" is a misnomer.  "Best practices" are to software  
development what scales are to music or what forms are to martial arts  
- learning exercises.  That said, there is a lack of documentation  
about Cucumber and story-based automated web acceptance testing to get  
people going.  But you will very quickly hit something more unusual  
than a standard CRUD app - calling a command line tool, using a  
scheduled job, interfacing with an awkward web service*, parsing email  
etc.  And there's never a "best" way to deal with these, you have to  
go about it the way that gives you the best trade off between  
confidence in your code, development time and spec performance.


> Meantime, do any of the gurus have a list of recommended resources?

Right now the best resource is the rspec-users list[1].  Many, if not  
most, of the issues around BDD and Cucumber are still being thrashed  
out.  Recommended solutions to common (and uncommon) problems change  
frequently.  There's a lot talented developers both in and out of the  
core team that are very generous answering questions.  (I chime in too.)


Ashley


[1] http://rubyforge.org/mailman/listinfo/rspec-users

* DAMN YOU TWITTER!!!!!

-- 
http://www.patchspace.co.uk/
http://aviewfromafar.net/


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"NWRUG" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/nwrug-members?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to