On 7/12/07, Anthony Carlos <[EMAIL PROTECTED]> wrote: > If you guys don't mind, I'm going to create a sample web page with > this concept on it, stealing from Ashley and David's writings. If > people like it, perhaps we can get it included in the documentation. >
Go ahead, that would be great! Aslak > On Jul 11, 2007, at 12:35 PM, Ashley Moran wrote: > > > > > On 11 Jul 2007, at 17:12, Anthony Carlos wrote: > > > >> What do you think? > > > > > > I think there's a lot of merit in that idea. I've come across loads > > of situations where it was not obvious how to write the specs or code > > so that the code or specs (respectively) are clear and useful. I'm > > sure they could be distilled to a set of template situations - I'd be > > happy to submit examples. > > > > When people ask what developing with tests is like I tend to say that > > the difference between using RSpec and writing specs is like the > > difference between learning how a paintbrush works and learning how > > to paint a picture. RSpec's easy enough to pick up, but I wish I > > could point people at a more theoretical how-to that helps with the > > difficult "how do I spec this?" problems. > > > > Ashley > > > > > > > > _______________________________________________ > > rspec-users mailing list > > rspec-users@rubyforge.org > > http://rubyforge.org/mailman/listinfo/rspec-users > > _______________________________________________ > rspec-users mailing list > rspec-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users > _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
