Hi Aslak, Thanks for the heads-up, but it seems the AfterStep block is only executed if a step passes and not if it fails, is pending, skipped or non-implemented.
I tried to run a debugger on it to see what happens, but I think Cucumber is opening another Ruby process and preventing me from debugging. Thanks Aidy 2008/12/22 aslak hellesoy <aslak.helle...@gmail.com>: > > > On Mon, Dec 22, 2008 at 9:46 PM, aidy lewis <aidy.le...@googlemail.com> > wrote: >> >> Hi, >> >> I am using Cucumber in combination with tests that drive the actual >> browser. >> >> Is there a place where I can easily trap an exception and take a >> screenshot of the browser? > > http://github.com/aslakhellesoy/cucumber/wikis/hooks > > Use AfterStep. Currently there is no easy way for the AfterStep block to > figure out whether a step failed or not though. > Existing tix: > > http://rspec.lighthouseapp.com/projects/16211-cucumber/tickets/44-ability-to-teardown-failing-or-pending-scenarios-in-different-ways > http://rspec.lighthouseapp.com/projects/16211/tickets/110-after-method-status-check > > Aslak > >> >> Regards >> >> Aidy >> _______________________________________________ >> 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
