Re: zope-tests - FAILED: 12, OK: 8
Adam GROSZER <[email protected]>
| Newsgroups | gmane.comp.web.zope.devel |
|---|---|
| Message-ID | <[email protected]> |
On 09/23/2013 10:03 AM, Marius Gedminas wrote: > On Fri, Sep 13, 2013 at 09:01:37AM +0300, Marius Gedminas wrote: >> On Fri, Sep 13, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: >>> [2] winbot / zope.app.authentication_py_265_32 >>> [3] winbot / zope.app.http_py_265_32 >>> [4] winbot / zope.app.publication_py_265_32 >>> [8] winbot / zope.app.wsgi_py_265_32 >> >> zope.testbrowser-caused WebTest version conflict. > > I've no idea why these errors disappeared. > >> I plan to release zope.testbrowser 5.0.0 this week. It should fix these >> (and probably cause lots of pain elsewhere, if people use undocumented >> internals like .mech_browser directly, which they do). > > I basically chickened out. > > IIRC the new webtest-based zope.testbrowser breaks API pretty hard (e.g. > you can't use zope.app.testing.functional.FunctionalTestLayer any more; > you must create a WSGITestLayer from I-forgot-what-zope.-package). > > What's worse, it lacks documentation for how you're supposed to migrate > from older zope.testbrowser versions (<=4.x) to newer versions (5.x). > > I will not do a release until this documentation exists. Could you add a line to let's say CHANGES.txt about this? The idea would be to really block a release. Not that someone comes around and pushes the release out half baked. -- Best regards, Adam GROSZER -- Quote of the day: It is never worthwhile to make rents in a garment for the sake of mending them? Nor to create doubts in order to show how cleverly we can quiet them. - Charles Haddon Spurgeon _______________________________________________ Zope-Dev maillist - [email protected] https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )