In many buildouts I have a [test-all] section. Just like [test], but then
with more eggs (typically all the dependencies). That's too much work, so I'm
looking for a recipe to handle that for me. My thoughts:
- Subclass zc.recipe.testrunner in a new recipe.
- Look for a [test] part in buildout and take the defaults there.
- Examine the eggs in test:eggs and look up their setup.py dependencies.
- Those dependencies, that's the new list of eggs that need testing.
- Just a [test-all] with the new recipe should be enough to test all main
Question: is there an existing recipe that does this? Main point is that I
don't want to specify the dependencies that are to be tested by hand, so that
seems to rule out z3c.recipe.compattest. But there's been so much talk about
testing everything in the last weeks that I thought it better to ask :-)
Reinout van Rees - rein...@vanrees.org - http://reinout.vanrees.org
Software developer at http://www.thehealthagency.com
"Military engineers build missiles. Civil engineers build targets"
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -