[Zope-dev] Zope Tests: 5 OK
Summary of messages to the zope-tests list. Period Wed May 14 11:00:00 2008 UTC to Thu May 15 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Wed May 14 21:00:10 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009550.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Wed May 14 21:01:40 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009551.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Wed May 14 21:03:10 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009552.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Wed May 14 21:04:40 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009553.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Wed May 14 21:06:11 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009554.html ___ 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 )
[Zope-dev] zope.testing console script
Hi, I am comparing nose, py.test and zope.testing, and I realized zope.testing does not install a console script at Python level. it is not really a problem when working with a buildout-centric approach (thanks to zc.recipe.testrunner), but how can zope.testing be used with plain Python package ? Is there any installer available, that would allow running zope.testing from the shell ? To advocate zope.testing, I need to be able to demonstrate it can be used like the other tools available out there :D If nothing exists, I would like to suggest adding a setuptools console entry point in zope.testing setup.py file, to get a python script in the $PYTHON/bin folder, exactly like what zc.recipe.testrunner does. It could be called zope.testrunner maybe ? (nose= nostests, py.test = py.test) Regards Tarek -- Tarek Ziadé | Association AfPy | www.afpy.org Blog FR | http://programmation-python.org Blog EN | http://tarekziade.wordpress.com/ ___ 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 )
[Zope-dev] Re: zope.testing console script
Tarek Ziadé wrote: If nothing exists, I would like to suggest adding a setuptools console entry point in zope.testing setup.py file, to get a python script in the $PYTHON/bin folder, exactly like what zc.recipe.testrunner does. +1 It could be called zope.testrunner maybe ? (nose= nostests, py.test = py.test) I suppose having it called 'test' (which is our convention) is a bit arrogant. But calling it 'zope.testrunner' creates the allusion that the package is called zope.testrunner as well. How about 'run-zope.testing' or something along those lines? ___ 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] zope.testing console script
Previously Tarek Ziadé wrote: I am comparing nose, py.test and zope.testing, and I realized zope.testing does not install a console script at Python level. it is not really a problem when working with a buildout-centric approach (thanks to zc.recipe.testrunner), but how can zope.testing be used with plain Python package ? Is there any installer available, that would allow running zope.testing from the shell ? To advocate zope.testing, I need to be able to demonstrate it can be used like the other tools available out there :D Is there a reason to advocate zope.testing over the others? Would it perhaps make more sense to use one of the more widely used tools instead of maintaing our own testing toolkit? Wichert. -- Wichert Akkerman [EMAIL PROTECTED]It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ 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] zope.testing console script
On Thu, May 15, 2008 at 01:43:05PM +0200, Wichert Akkerman wrote: Previously Tarek Ziadé wrote: I am comparing nose, py.test and zope.testing, and I realized zope.testing does not install a console script at Python level. it is not really a problem when working with a buildout-centric approach (thanks to zc.recipe.testrunner), but how can zope.testing be used with plain Python package ? Is there any installer available, that would allow running zope.testing from the shell ? To advocate zope.testing, I need to be able to demonstrate it can be used like the other tools available out there :D Is there a reason to advocate zope.testing over the others? Would it perhaps make more sense to use one of the more widely used tools instead of maintaing our own testing toolkit? For one: the others don't have layers. -- Christian Theune · [EMAIL PROTECTED] gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ 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] zope.testing console script
Tarek Ziadé wrote: Hi, I am comparing nose, py.test and zope.testing, and I realized zope.testing does not install a console script at Python level. it is not really a problem when working with a buildout-centric approach (thanks to zc.recipe.testrunner), but how can zope.testing be used with plain Python package ? Is there any installer available, that would allow running zope.testing from the shell ? FWIW, we wrapped it up like this: http://svn.repoze.org/repoze.zope2/trunk/repoze/zope2/scripts/testrunner.py (that's the backend for a zope2testrunner console script) - C ___ 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] zope.testing console script
On Thu, May 15, 2008 at 2:10 PM, Christian Theune [EMAIL PROTECTED] wrote: On Thu, May 15, 2008 at 01:43:05PM +0200, Wichert Akkerman wrote: Previously Tarek Ziadé wrote: I am comparing nose, py.test and zope.testing, and I realized zope.testing does not install a console script at Python level. it is not really a problem when working with a buildout-centric approach (thanks to zc.recipe.testrunner), but how can zope.testing be used with plain Python package ? Is there any installer available, that would allow running zope.testing from the shell ? To advocate zope.testing, I need to be able to demonstrate it can be used like the other tools available out there :D Is there a reason to advocate zope.testing over the others? Would it perhaps make more sense to use one of the more widely used tools instead of maintaing our own testing toolkit? Good question, I am not through in my comparison work, but the range of features are quite interesting in zope.testing ihmo, compared to others, and the zope community is used to it. For one: the others don't have layers. Yes, and other provides test fixtures at method, class, module and (nose) package level. Although, py.test and nose provide a lighter approach where there's no need to use the unittest base classes, as the tools wraps on the fly any function, class so there's no need for extra boiler-plate code. py.test is using an iterator to launch tests immediatly while looking for them, the script is very fast This work i am doing is for a book, but I can publish the conclusion here if it can help making a decision on this. At this point I think that the work being done by Collin Winter in Python 3K will lead to a new testing framework in Python/unitest that will be less Java-oriented and lighter for test writer. From there, the third party libraries will probably be reduced to the test discovery part. (I don't think this will be integrated in python but I might be wrong) My point of view is that zope.testing should evolve a little bit to be usable naturally from the command line like others, and maybe be more flexible in the discovering part, by wrapping tests that are not based on TestCase. This would make a unique testing tool, for the Zope community, and with a lighter way to write new tests, and with the command-line interface they are used to since years Tarek ___ 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] zope.testing console script
Phillip: I suppose having it called 'test' (which is our convention) is a bit arrogant. But calling it 'zope.testrunner' creates the allusion that the package is called zope.testrunner as well. How about 'run-zope.testing' or something along those lines? Chris McDonough [EMAIL PROTECTED] wrote: FWIW, we wrapped it up like this: http://svn.repoze.org/repoze.zope2/trunk/repoze/zope2/scripts/testrunner.py (that's the backend for a zope2testrunner console script) mmm, what about a shorter name ? ztests Tarek -- Tarek Ziadé | Association AfPy | www.afpy.org Blog FR | http://programmation-python.org Blog EN | http://tarekziade.wordpress.com/ ___ 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] zope.testing console script
On Thu, May 15, 2008 at 7:43 AM, Wichert Akkerman [EMAIL PROTECTED] wrote: Is there a reason to advocate zope.testing over the others? Would it perhaps make more sense to use one of the more widely used tools instead of maintaing our own testing toolkit? I'd also like for us to adopt one of the more widely used test runners, but as mentioned in replies, there are some features in zope.testing that we depend on. If someone were adequately motivated and had sufficient time (neither of which I have, so I suspect no one else does either), it would be interesting to attempt to endue another test runner with the features we need (layers, etc.). -- Benji York Senior Software Engineer Zope Corporation ___ 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] zope.testing console script
Hi, On Thu, May 15, 2008 at 02:19:17PM +0200, Tarek Ziadé wrote: On Thu, May 15, 2008 at 2:10 PM, Christian Theune [EMAIL PROTECTED] wrote: On Thu, May 15, 2008 at 01:43:05PM +0200, Wichert Akkerman wrote: Previously Tarek Ziadé wrote: I am comparing nose, py.test and zope.testing, and I realized zope.testing does not install a console script at Python level. it is not really a problem when working with a buildout-centric approach (thanks to zc.recipe.testrunner), but how can zope.testing be used with plain Python package ? Is there any installer available, that would allow running zope.testing from the shell ? To advocate zope.testing, I need to be able to demonstrate it can be used like the other tools available out there :D Is there a reason to advocate zope.testing over the others? Would it perhaps make more sense to use one of the more widely used tools instead of maintaing our own testing toolkit? Good question, I am not through in my comparison work, but the range of features are quite interesting in zope.testing ihmo, compared to others, and the zope community is used to it. Make sure you look at the trunk as well. I did some major refactorings on the grok sprint. Yes, and other provides test fixtures at method, class, module and (nose) package level. Although, py.test and nose provide a lighter approach where there's no need to use the unittest base classes, as the tools wraps on the fly any function, class so there's no need for extra boiler-plate code. The refactoring would be able to do that with a plugin. py.test is using an iterator to launch tests immediatly while looking for them, the script is very fast Even when gathering thousands of tests, this usually takes less than 1% of the time that the tests actually take to run. So it's a nice point but not that important IMHO. This work i am doing is for a book, but I can publish the conclusion here if it can help making a decision on this. At this point I think that the work being done by Collin Winter in Python 3K will lead to a new testing framework in Python/unitest that will be less Java-oriented and lighter for test writer. From there, the third party libraries will probably be reduced to the test discovery part. (I don't think this will be integrated in python but I might be wrong) And reporting and integrating debugging tools and ... I guess. My point of view is that zope.testing should evolve a little bit to be usable naturally from the command line like others, and maybe be more flexible in the discovering part, by wrapping tests that are not based on TestCase. The refactoring should allow this more easily. Christian -- Christian Theune · [EMAIL PROTECTED] gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ 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 )
[Zope-dev] Re: sad news about Joachim Schmitz
Martijn Faassen wrote: Hi there, Joachim Schmitz, long-standing member of the Zope community, died last weekend. Please see the following: http://faassen.n--tree.net/blog/view/weblog/2008/05/14/0 That was a wonderfully written memoriam, Martijn, thanks for writing it. A number of things you wrote brought back very vivid memories of Joachim. He's one of the originals and we were lucky to have him as part of our community. --Paul ___ 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] zope.testing console script
On May 15, 2008, at 7:00 AM, Tarek Ziadé wrote: I am comparing nose, py.test and zope.testing, and I realized zope.testing does not install a console script at Python level. That's a bug. If nothing exists, I would like to suggest adding a setuptools console entry point in zope.testing setup.py file, to get a python script in the $PYTHON/bin folder, exactly like what zc.recipe.testrunner does. +1 It could be called zope.testrunner maybe ? (nose= nostests, py.test = py.test) too long. I vote for test or runtest. Jim -- Jim Fulton Zope Corporation ___ 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 )
