Re: [Zope-dev] New test summarizer format

2011-03-29 Thread Adam GROSZER
Hello, On Thu, 24 Mar 2011 10:51:44 +0100 you wrote: Hello, * Adam GROSZERagros...@gmail.com [2011-03-23 08:45]: On Wed, 23 Mar 2011 07:43:26 +0100 you wrote: On a tangentially-related note, what happened to the proposed new summarizer formatting? Half a year ago (or whenever), I got the

Re: [Zope-dev] Test fixture concepts

2011-03-29 Thread Jim Fulton
On Mon, Mar 28, 2011 at 5:27 PM, Martin Aspeli optilude+li...@gmail.com wrote: On 28 March 2011 15:45, Tres Seaver tsea...@palladion.com wrote: The vast majority of the doctest testcases in zope.* packages fall into this category:  poor isolation, lots of edge cases which would obscure any

[Zope-dev] Zope Tests: 74 OK, 14 Failed

2011-03-29 Thread Zope Tests Summarizer
Summary of messages to the zope-tests list. Period Mon Mar 28 11:00:00 2011 UTC to Tue Mar 29 11:00:00 2011 UTC. There were 88 messages: 8 from Zope Tests, 4 from buildbot at pov.lt, 23 from buildbot at winbot.zope.org, 8 from ccomb at free.fr, 45 from jdriessen at thehealthagency.com. Test

Re: [Zope-dev] [buildout] private releases

2011-03-29 Thread Adam GROSZER
Hello, On Fri, 25 Mar 2011 19:24:05 + you wrote: Hi Christian, On 25/03/2011 16:49, Christian Theune wrote: the German speaking Zope Users Group (DZUG e.V.) organizes a series of 4 sprints this year to support feature development within the proximity of the ZTK and solve problems

Re: [Zope-dev] Test fixture concepts

2011-03-29 Thread Stephan Richter
On Tuesday, March 29, 2011, Jim Fulton wrote: so I may forgo them. Which is a mistake. You should create separate tests. I typically put large tests, dealing with main use cases where there is a definite flow of activity in '.test' files. I do these in separate files because they're

Re: [Zope-dev] Test fixture concepts

2011-03-29 Thread Wichert Akkerman
On 3/29/11 14:40 , Stephan Richter wrote: On Tuesday, March 29, 2011, Jim Fulton wrote: so I may forgo them. Which is a mistake. You should create separate tests. I typically put large tests, dealing with main use cases where there is a definite flow of activity in '.test' files. I do

Re: [Zope-dev] Zope Tests: 74 OK, 14 Failed

2011-03-29 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Subject: FAILED : Zope Buildbot / zopetoolkit-1.0_win-py2.6 slave-win From: jdriessen at thehealthagency.com Date: Mon Mar 28 15:18:14 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036429.html Subject: FAILED : Zope

Re: [Zope-dev] Zope Tests: 74 OK, 14 Failed

2011-03-29 Thread Brian Sutherland
On Tue, Mar 29, 2011 at 10:22:45AM -0400, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Subject: FAILED : Zope Buildbot / zopetoolkit-1.0_win-py2.6 slave-win From: jdriessen at thehealthagency.com Date: Mon Mar 28 15:18:14 EDT 2011 URL:

Re: [Zope-dev] [buildout] private releases

2011-03-29 Thread Martijn Pieters
On Tue, Mar 29, 2011 at 14:16, Adam GROSZER agroszer...@gmail.com wrote: Well the problem is that it's not always so simple. For me a release process is preferably a single command or a single click on a button. Both zest.releaser and jarn.mkrelease offer you simple single-command release

Re: [Zope-dev] [buildout] private releases

2011-03-29 Thread Wolfgang Schnerring
* Martijn Pieters m...@zopatista.com [2011-03-29 20:59]: On Tue, Mar 29, 2011 at 14:16, Adam GROSZER agroszer...@gmail.com wrote: ...and just dump the .tgz sdists in that folder. Well the problem is that it's not always so simple. For me a release process is preferably a single command or a