[Zope 2.12] how to test products/packages?
The Zope 2.12 documention tells that the "test" command was removed from "zopectl". "test" was a convenient way to test products and packages in the context of the instance. How is this use case now supported? -- Dieter
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 15.03.2009 8:31 Uhr, Dieter Maurer wrote:
The Zope 2.12 documention tells that the "test" command was removed from "zopectl".
Have to investigate that.
"test" was a convenient way to test products and packages in the context of the instance. How is this use case now supported?
Go with the buildout approach and use the alltests.cfg for testing support (see alltests.cfg). Means: work with a SVN checkout. - -aj - -- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: info@zopyx.com - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK - ------------------------------------------------------------------------ E-Publishing, Python, Zope & Plone development, Consulting -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkm8s+0ACgkQCJIWIbr9KYzEXwCgyo8SjYiDiHBJbucpaf/xbaWR TaoAoLQ0b5W7+oiBQW2EI+PW0O0Niihr =vJNj -----END PGP SIGNATURE-----
Andreas Jung wrote at 2009-3-15 08:53 +0100:
On 15.03.2009 8:31 Uhr, Dieter Maurer wrote:
The Zope 2.12 documention tells that the "test" command was removed from "zopectl".
Have to investigate that.
"test" was a convenient way to test products and packages in the context of the instance. How is this use case now supported?
Go with the buildout approach and use the alltests.cfg for testing support (see alltests.cfg). Means: work with a SVN checkout.
I do not want to test Zope, I want to test *MY* Zope based components. -- Dieter
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 15.03.2009 18:27 Uhr, Dieter Maurer wrote:
Andreas Jung wrote at 2009-3-15 08:53 +0100:
On 15.03.2009 8:31 Uhr, Dieter Maurer wrote:
The Zope 2.12 documention tells that the "test" command was removed from "zopectl". Have to investigate that.
"test" was a convenient way to test products and packages in the context of the instance. How is this use case now supported? Go with the buildout approach and use the alltests.cfg for testing support (see alltests.cfg). Means: work with a SVN checkout.
I do not want to test Zope, I want to test *MY* Zope based components.
Then write *your* dieter.cfg containing [buildout] extends = buildout.cfg parts += alltests [alltests] recipe = zc.recipe.testrunner eggs = dm.foo.bar and run buildout -c dieter.cfg and later bin/alltests - -aj -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkm9PKIACgkQCJIWIbr9KYxXoQCgr8j6/YMeP/N/OUX35Zz862ov pRoAoNqOu74upBaf20esiozNajq7+U/U =X1wQ -----END PGP SIGNATURE-----
Andreas Jung wrote at 2009-3-15 18:36 +0100:
...
"test" was a convenient way to test products and packages in the context of the instance. How is this use case now supported? Go with the buildout approach and use the alltests.cfg for testing support (see alltests.cfg). Means: work with a SVN checkout.
I do not want to test Zope, I want to test *MY* Zope based components.
Then write *your* dieter.cfg containing
[buildout] extends = buildout.cfg parts += alltests
[alltests] recipe = zc.recipe.testrunner eggs = dm.foo.bar
and run
buildout -c dieter.cfg
My experience with "buildout" is not good. I want to avoid it. -- Dieter
Dieter Maurer wrote:
The Zope 2.12 documention tells that the "test" command was removed from "zopectl".
"test" was a convenient way to test products and packages in the context of the instance. How is this use case now supported?
The normal way to develop anything in the Zope world is based on zc.buildout today. You can define a testrunner like this: [test] recipe = zc.recipe.testrunner eggs = Zope2 and extend the eggs section with your eggs under development. Zope2 behaves the same as any other zope.* package now and does no longer require any special test setup. The test command of zopectl depended on too many assumptions based on environment variables and specific directory layout, which are no longer true in the standard layout of eggs. Hanno
Hanno Schlichting wrote at 2009-3-15 11:10 +0100:
Dieter Maurer wrote:
The Zope 2.12 documention tells that the "test" command was removed from "zopectl".
"test" was a convenient way to test products and packages in the context of the instance. How is this use case now supported?
The normal way to develop anything in the Zope world is based on zc.buildout today. You can define a testrunner like this:
I do not have good experience with buildout and will try to avoid it. I will probably resurrect the old way to run tests in the same way I will resurrect ZClasses (i.e. though an externally maintained PyPI package). -- Dieter
Dieter Maurer wrote:
Hanno Schlichting wrote at 2009-3-15 11:10 +0100:
Dieter Maurer wrote:
The Zope 2.12 documention tells that the "test" command was removed from "zopectl".
"test" was a convenient way to test products and packages in the context of the instance. How is this use case now supported? The normal way to develop anything in the Zope world is based on zc.buildout today. You can define a testrunner like this:
I do not have good experience with buildout and will try to avoid it.
It ought to be possible to run the Zope testrunner by installing a script, e.g. installing zope.testrunner in a virtualenv to get the 'test' script. I don't know what more zc.recipe.testrunner does, but I agree that we shouldn't be dependent on buildout (over virtualenv+easy_install/pip) to be able to run tests. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book
participants (4)
-
Andreas Jung -
Dieter Maurer -
Hanno Schlichting -
Martin Aspeli