Re: unittest. customizing tstloaders / discover()

References	<mailman.3518.1323638859.27778.python-list@python.org> <87y5uiu1t4.fsf@jubold.box> <mailman.3525.1323653551.27778.python-list@python.org> <8739cqf4so.fsf@jubold.box>
Date	2011-12-12 11:50 -0500
Subject	Re: unittest. customizing tstloaders / discover()
From	Nathan Rice <nathan.alexander.rice@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.3560.1323708658.27778.python-list@python.org> (permalink)

Show all headers | View raw

Nose is absolutely the way to go for your testing needs.  You can put
"__test__ = False" in modules or classes to stop test collection.

On Mon, Dec 12, 2011 at 5:44 AM, Thomas Bach <bachth@uni-mainz.de> wrote:
> Gelonida N <gelonida@gmail.com> writes:
>
>> Do I loose anything if using nose. or example can all unit tests / doc
>> tests still be run from nose?
>
> AFAIK you don't loose anything by using nose – the unittests should all
> be found and doctests can be run via `--with-doctest', I never used
> doctests though.
>
> regards
> --
> http://mail.python.org/mailman/listinfo/python-list

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

unittest. customizing tstloaders / discover() Gelonida N <gelonida@gmail.com> - 2011-12-11 22:27 +0100
  Re: unittest. customizing tstloaders / discover() Thomas Bach <bachth@uni-mainz.de> - 2011-12-12 00:27 +0100
    Re: unittest. customizing tstloaders / discover() Gelonida N <gelonida@gmail.com> - 2011-12-12 02:32 +0100
      Re: unittest. customizing tstloaders / discover() Thomas Bach <bachth@uni-mainz.de> - 2011-12-12 11:44 +0100
        Re: unittest. customizing tstloaders / discover() Nathan Rice <nathan.alexander.rice@gmail.com> - 2011-12-12 11:50 -0500

csiph-web