On Mon, Feb 9, 2009 at 6:11 AM, aslak hellesoy
It’s because Cucumber’s Rails support configures ActionController to
send all errors straight through.
Patches and suggestions about how to improve this are welcome.
(In most cases it’s easier to spot errors when exceptions ripple through)
Make it a configuration option? Or catch it with a proxy that
inspects the exception then passes it back to Rails, and provide
matchers or formatting options that display Cucumber’s analysis only
when the user wants it?
I’m with Jeff on this: RecordNotFound isn’t necessarily an “error,”
it’s just an exception. One that will frequently come up in normal
user interaction. A well-behaved app will do appropriate things with
that exception and Cucumber should be able to test for those
appropriate things. A testing framework that disrupts the application
behavior cannot test it.
Steve E. (email@example.com)
ESCAPE POD - The Science Fiction Podcast Magazine