Unittest testing assert*() calls rather than methods?

Ben Finney ben+python at benfinney.id.au
Thu Sep 29 04:27:27 CEST 2011

Roy Smith <roy at panix.com> writes:

> In article <87k48szqo1.fsf at benfinney.id.au>,
>  Ben Finney <ben+python at benfinney.id.au> wrote:
> > Worse, if one of the scenarios causes the test to fail, the loop will
> > end and you won't get the results for the remaining scenarios.
> Which, depending on what you're doing, may or may not be important.  In 
> many cases, there's only two states of interest:
> 1) All tests pass
> 2) Anything else

For the purpose of debugging, it's always useful to more specifically
narrow down the factors leading to failure.

 \      “A lie can be told in a few words. Debunking that lie can take |
  `\   pages. That is why my book… is five hundred pages long.” —Chris |
_o__)                                                Rodda, 2011-05-05 |
Ben Finney

More information about the Python-list mailing list