Re: [Zope-dev] Why doesn't this buildout run the zdaemon tests?
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 ___ 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 )
Re: [Zope-dev] Why doesn't this buildout run the zdaemon tests?
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' inside a zc.recipe.testrunner section is for the eggs whose tests you want to run. What decides what eggs end up on the python path of bin/test? Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ 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 )
Re: [Zope-dev] Why doesn't this buildout run the zdaemon tests?
-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 = > http://svn.zope.org/*checkout*/Zope/tags/2.12.0a1/versions-zope2.cfg > versions = versions > develop = Zope zdaemon > > [versions] > setuptools = 0.6c9 > zc.buildout = 1.2.1 > zdaemon = > Zope2 = > > [test] > recipe = zc.recipe.testrunner > eggs = >Zope2 > > As before, "Zope" contains a checkout of the trunk of the Zope2 egg, and > zdaemon contains a checkout of the trunk of zdaemon egg? > > Zope2 depends on zdaemon, so why are its tests not getting run when I do > bin/test? bin/test no longer runs tests for separately-installed dependencies. You need to do the 'alltests' dance to run them (I just learned the chant this morning): $ bin/buildout -c alltests.cfg $ bin/alltests Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com 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 iD8DBQFJ3iwc+gerLs4ltQ4RAikZAJ40q5e14MkxS0TmowlZI4LlldvVqgCbBNKe 233njMhbS/E7y8VKMd1RxKk= =wHpT -END PGP 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 )
Re: [Zope-dev] Why doesn't this buildout run the zdaemon tests?
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 zdaemon Look at the alltests.cfg in trunk, to see how we run the tests for Zope2 and all its interesting dependencies. Hanno ___ 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 )
