[RFC/MERGE](0.17) Auto load tests
Martin Pool
mbp at sourcefrog.net
Wed May 2 09:13:11 BST 2007
On 5/2/07, Ian Clatworthy <ian.clatworthy at internode.on.net> wrote:
> I can see the advantage of registering test modules explicitly because
> it does force one to think about the most sensible order to run the
> tests, module by module at least. But unittests ought to be independent
> in any case.
Actually we always run them in alphabetical order, and we require that
the list be in alphabetical order, so this advantage does not accrue
in practice in bzrlib. I used to think I wanted this so I could make
sure basic functions were working before testing complicated things
that might give complicated errors, but it turns out that --first does
the trick most of the time. If we did want ordering we can name the
tests so that they do that. (That's why some tests have numbers in
the name.)
I think Robert's objection was that autodetection can "fail closed"
meaning that tests are just not run if something causes them to not be
detected.
Anyhow, pending Robert's comments I like the sound of it too...
--
Martin
More information about the bazaar
mailing list