Steve, That's really useful! Thank you.
- Mark On Wed, Jan 7, 2009 at 12:40 PM, Stephen Eley <[email protected]> wrote: > On Wed, Jan 7, 2009 at 6:36 AM, Matt Wynne <[email protected]> wrote: > > > > I would start your debugging by adding a puts statement between lines 26 > and > > 27 to show more of the (unexpected) response. Looking at response.code or > > response.body should give you some clues. > > You can also check the logfiles. I often keep two terminals running > in the background whenever I'm doing BDD coding; one's running > autospec, and the other one has 'tail -f log/test.log'. I don't have > to look at that all the time, but when something breaks and I can't > figure out why it's a huge time saver. I also found this post of Ben > Mabey's to be very useful for figuring out which chunk of log goes > with which spec: > > > http://www.benmabey.com/2008/07/04/global-setup-in-rspec-or-how-to-add-logging-for-specs/ > > > > -- > Have Fun, > Steve Eley ([email protected]) > ESCAPE POD - The Science Fiction Podcast Magazine > http://www.escapepod.org > _______________________________________________ > rspec-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/rspec-users >
_______________________________________________ rspec-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/rspec-users
