On Thu, Aug 13, 2009 at 2:26 AM, Wolfgang Schnerring<ws@gocept.com> wrote:

* Jim Fulton <jim@zope.com> [2009-08-12 20:56]: ...

...

Here's an alternative:

  [versions]   zope.foo = 1.2.3   zope.bar = 1.2.3   zope.app.baz = 1.2.3   grok.bar = 1.1.0   thirdparty.dependency = 4.4

  [ztk]   projects = zope.foo zope.bar zope.app.baz   also-tested = grok.bar

Yup, that looks much better. As far as I'm concerned, let's use this. (I'll leave it to Martijn to explain whether/which/why additional information should be stored in the KGS in computer-readable form.)

I've just updated z3c.recipe.compattest to support exactly this: ... Would you give it a try?

Yup. Works great. I've updated: svn://svn.zope.org/repos/main/zopetoolkit/branches/jim-kgs/kgs to use it. I created ztk.cfg that looks like: [ztk] libraries = ... under-review = ... projects = ${ztk:libraries} ${ztk:under-review} [buildout] versions = versions allow-picked-versions = false [versions] ... and a buildout.cfg: [buildout] parts = test-ztk extends = ztk.cfg [test-ztk] recipe = z3c.recipe.compattest include = ${ztk:projects} This gives me the test files I expect that use the specified versions. One minor quibble is that the recipe uses the part name as a test file prefix for the individual tests (e.g. test-ztk-zope.proxy). But the combined test runner has "test-" in front of the part name, so I get "test-test-ztk". I'd like to use the part name for the combined test name, "test-ztk". Thanks. Thanks too to Fabio for helping to move this forward! So, I think we now have a tool that will let us take the next steps. Can we all agree on this? Jim -- Jim Fulton