D
Daniel Berger
Hi all,
I came across an article regarding unit testing philosophy that I
thought was interesting:
http://weblogs.asp.net/rosherove/archive/2005/04/14/AvoidMultipleAsserts.aspx
This sparked a conversation on IRC regarding coming up with a way to
have asserts continue even if one of them fails within a unit test. Is
there a way to alter the behavior of test-unit so that it doesn't bail
out on subsequent asserts if one fails? Something builtin to test-unit
or a simple hack?
Any opinions on multiple asserts within a single unit test? Any
opinions on what the default behavior should be for test-unit with
regards to multiple asserts where one fails?
Regards,
Dan
I came across an article regarding unit testing philosophy that I
thought was interesting:
http://weblogs.asp.net/rosherove/archive/2005/04/14/AvoidMultipleAsserts.aspx
This sparked a conversation on IRC regarding coming up with a way to
have asserts continue even if one of them fails within a unit test. Is
there a way to alter the behavior of test-unit so that it doesn't bail
out on subsequent asserts if one fails? Something builtin to test-unit
or a simple hack?
Any opinions on multiple asserts within a single unit test? Any
opinions on what the default behavior should be for test-unit with
regards to multiple asserts where one fails?
Regards,
Dan