On Tue, Mar 04, 2008 at 05:03:13PM -0500, Tres Seaver wrote: > Marius Gedminas wrote: > > > Also, I think that lack of a bin/test for any package can be rightly > > considered to be a bug. > > 'bin/test' doesn't make much sense to me as a way to run the tests > belonging to the packge-being-tested: it corresopnds to the tests for > an entire configured environment.
And that's what you get when you run bin/buildbot in a checkout of any zope.foo package -- an entire configured environment, sufficient for testing that package. IMHO. > I would think that getting 'python setup.py test' to work for each > package-being-tested, which a) makes sure that the package works even > for non-buildout-aware users, and b) fits what everybody else in the > Python eggs word expects. That would be great. Do you know how to make setup.py test invoke the zope.testing test runner? The standard unittest test runner that setuptools uses by default is not sufficient -- it doesn't know anything about test layers. Marius Gedminas -- As an aside, UPnP's implementation (which features SOAP, HTTP over multicast/broadcast UDP, and extremely odd XML) is a must-read for fans of unnatural and baroque network protocols. -- Anthony Baxter
Description: Digital signature
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )