[RFC/MERGE](0.17) Auto load tests

[Robert Collins]

On Wed, 2007-05-02 at 18:01 +1000, Ian Clatworthy wrote:
> Robert Collins wrote:
> > On Fri, 2007-04-27 at 18:08 -0500, John Arbash Meinel wrote:
> >   
> >> Mostly I'm looking for feedback. I wanted to implement this for a
> >> plugin
> >> I was writing, because I was getting tired of manually tracking
> >> filenames. (Also with plugins you have to be careful about your python
> >> path, because you are actually loaded as bzrlib.plugins.PLUGIN.tests
> >> not
> >> PLUGIN.tests). 
> >>     
> >
> > I'm personally not a fan of autodiscovery of tests - it just feels like
> > too much magic. If we are going to do it I'd rather we looked at
> > leveraging nose or trial than rolling our own. -0 from me.
> >
> > -Rob
> >   
> Robert,
> 
> Can you give some more background as to why you dislike autodiscovery of 
> tests? Are there particular scenarios where you've seen it cause more 
> problems that it solves?

All the autodiscovery tools I've seen fail silently. This sucks :(. We
have a complex (but worth the complexity) test setup, and I'd hate to
see test coverage shrink due to a defect in the test loader.

Thats the primary concern for me given that John did allow a package
boundary to introduce different discovery policies. If I was writing a
discovery process I'd be doing that at the level of a module not a
package though, FWIW.

Rob
-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20070508/4e5b8b15/attachment.pgp