[Grok-dev] Re: zope.testing autodiscovery
uli at gnufix.de
Tue Jun 24 05:11:16 EDT 2008
Wolfgang Schnerring wrote:
> * Wolfgang Schnerring <wosc at wosc.de>[2008-06-24 06:48]:
> > * Wolfgang Schnerring <wosc at wosc.de>:
> >> * Christian Theune <ct at gocept.com>:
> >>> Better test discovery and getting rid of the need of test_suite() is another
> >>> refactoring/feature I want to perform on zope.testing.
> > Never mind. After reading http://grok.zope.org/documentation/how-to/tests-with-grok-testing
> > which was linked from the Grok 0.13 release notes, I realized that z3c.testsetup
> > already does all this and more. %-)
> However... z3c.testsup is quite Zope-dependent (it pulls in most of Zope3 since
> it needs to support zope.app.testing). I'd quite like to use zope.testrunner
> for non-Zope projects, and I'd like to have some test discovery there, too.
> What do people think? Is it worthwile/inside zope.testing's scope to do this?
The 2.2 release of z3c.testsetup pulls in zope.app.testing only for the
internal tests. It is not a requirement any more for simply using the
package (except you want Zope integration tests, of course). The 'hard'
requirements now are: setuptools, zope.testing and martian only.
In fact I would be happy to see the package running also in non-Zope
projects. Didn't try it myself yet, though. Please tell what you need.
Possibly I can help with that.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 191 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://mail.zope.org/pipermail/grok-dev/attachments/20080624/903297cf/attachment.bin
More information about the Grok-dev