Hi All,
Apologies for the current test failure on trunk, why doesn't the
following testrunner run the zdaemon tests?
[buildout]
parts = test
extends =
http://svn.zope.org/*checkout*/Zope/tags/2.12.0a1/versions-zope2.cfg
versions = versions
develop = Zope zdaemon
[versions]
setuptools = 0.6c9
Chris Withers wrote:
Apologies for the current test failure on trunk, why doesn't the
following testrunner run the zdaemon tests?
The testrunner recipe only puts the things in its own eggs section onto
the test path, so you need to do:
[test]
recipe = zc.recipe.testrunner
eggs =
Zope2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
Hi All,
Apologies for the current test failure on trunk, why doesn't the
following testrunner run the zdaemon tests?
[buildout]
parts = test
extends =
Hanno Schlichting wrote:
Chris Withers wrote:
Apologies for the current test failure on trunk, why doesn't the
following testrunner run the zdaemon tests?
The testrunner recipe only puts the things in its own eggs section onto
the test path,
Ah, I only just got that :-)
Okay, so 'eggs'
Tres Seaver wrote:
$ bin/buildout -c alltests.cfg
$ bin/alltests
Any reason alltests.cfg isn't in the root buildout.cfg?
(not that I'm using the root buildout.cfg either...)
Chris
--
Simplistix - Content Management, Zope Python Consulting
- http://www.simplistix.co.uk