[TIP] unittest q: keeping track of the *right* number of tests
bugs at almad.net
Mon Mar 23 02:09:05 PDT 2009
On Monday 23 March 2009 09:49:00 holger krekel wrote:
> Hi Titus, all,
> I think that test tools should go out of their way
> to do run-to-run sanity-checking, i.e. report loudly if
> things changed between test runs in suspicious ways.
> Where the definition of "suspicious" is customizable, of course.
> This mostly requires a way to store results of test-runs (including
> exact skip reasons) and to have "meta/sanity" checks
> and reporting.
> Happy to discuss common approaches at our py.test / nose meetup.
that would be nice, I'd like to hear that too.
IMHO, it should not be hard to hack some nose plugin that will provide
SkipTest subclasses (to distinguish various skip reasons) and an option for
more detailled report (--with-kill-user-on-bad-skip)
More information about the testing-in-python