From: Belorion <belorion@...>
Date: 2005-02-18T07:27:38+09:00
Subject: Re: test/unit non-exit on failure

> Can you just split the test into smaller ones?

Though that is certainly a viable solution, it is not ideal.  For
example, I have one test run which attempts 10 assertions on a single
method with varying parameter values.  5 of these assertions failed
(yes, my method obviously has some issues :P ).  This meant running
the test 5 times, and after each run I had to go comment out the known
failed assertions so I could find out what else did or did not work.

 Or, I could have written out 10 different smaller tests ... but to me
that seems to break the logic of wanting to run like assertions
together in the same test ... after all, they were all on the same
method and testing the same logic.  If, later down the line I want to
run these tests again, but not *all* of the tests in my suite, I would
have to pass each test_name at the command line.  This seems to make
unit testing more complicated than it should be (which I admit is
still nicer than unit testing in any other language I've used).  Is
asking test/unit to run all assertions in a test regardless of outcome
not possible then?