-----BEGIN PGP SIGNED MESSAGE-----
Marius Gedminas wrote:
> 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.
Chris McDonough added support for 'setup.py test' to the ZODB trunk:
The set of tests which get run seems not to respect the '--all' flag,
even when I hack the 'alltests()' function to force it into the
Tres Seaver +1 540-429-0999 [EMAIL PROTECTED]
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -