Failing unittest Test cases

[Paul Rubin]

Scott David Daniels <scott.daniels at acm.org> writes:
> Recently there was a checkin of a test that _should_ work but
> doesn't.  The discussion got around to means of indicating such
> tests (because the effort of creating a test should be captured)
> without disturbing the development flow.

Do you mean "shouldn't work but does"?  Anyway I don't understand
the question.  What's wrong with using assertRaises if you want to
check that a test raises a particular exception?