[Zope3-dev] Functional testing of XML-RPC views
Hi, I just wanted to functionally test an XML-RPC view and saw that currently those requests are hand crafted using http(). Wolfgang and I came up with a special transport for xmlrpclib.ServerProxy as a wrapper to http() so you can use from zope.app.testing.xmlrpc import ServerProxy proxy = ServerProxy(http://mgr:[EMAIL PROTECTED]/) proxy.xy to do functional testing of XML-RPC views in Zope 3 now. I changed the publisher xmlrpc tests to use this utility now. This has two meanings 1) Those tests now both test the XML-RPC testing utility and the publisher 2) Those tests now have a bit different semantics: Instead of comparing exact request strings for the XML-RPC message the tests now test whether the xmlrpclib is able to talk to the view. I'd like some feedback on this change before checking this in to the trunk. Christian -- gocept gmbh co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: OpenPGP digital signature ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Functional testing of XML-RPC views
On Tuesday 19 September 2006 04:14, Christian Theune wrote: I changed the publisher xmlrpc tests to use this utility now. This has two meanings 1) Those tests now both test the XML-RPC testing utility and the publisher 2) Those tests now have a bit different semantics: Instead of comparing exact request strings for the XML-RPC message the tests now test whether the xmlrpclib is able to talk to the view. I'd like some feedback on this change before checking this in to the trunk. This is perfectly fine. The exact XML was never of interest. Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
RE: Re[2]: [Zope3-dev] possible bug in zope.wfmc
Hi Adam, Jim -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adam Groszer Sent: Monday, September 11, 2006 4:27 PM To: Jim Fulton Cc: zope3-dev Subject: Re[2]: [Zope3-dev] possible bug in zope.wfmc Hello Jim, My specific usecase is: - -| Final | -- / - ...--| Update |- - -- \-| Issue |--... ^ \ - |\-- | \--| Review | | -- | | +--+ Update - Final is guarded by review_result == 'accepted' Update - Issue is guarded by transitionName == 'update_issue' Update - Review is guarded by transitionName == 'update_review' On the UI I put up every possible transition. Now if my crazy user chooses Final if review_result != 'accepted' then bang, the process gets finished. No errors, no messages, no exceptions. I already thought of filtering the possible transitions on the UI, but how? transitionName still forces the other conditions to false. A kind of transition-precondition is not available as I know. In this usecase raising an exception and thus not letting any transition to fire fits me perfectly. Is this (Update - Final) not a end transaction? Do you mean that the end transaction concept istn't correct working? XPDL would give the options - exception - default exception - otherwise but none of these are implemented in zope.wfmc. I think finishing the whole process is definitely bad behaviour. But what's correct? Please give a hint what should be done. Sorry, I don't know. but I agree that it should be a difference if we finsih a transaction with a Fslse or True guard. Regards Roger Ineichen Monday, September 11, 2006, 4:00:01 PM, you wrote: JF On Sep 10, 2006, at 9:00 AM, Adam Groszer wrote: Hello, I think I found a bug in zope.wfmc. Let's say the ReviewPublish and ReviewReject transitions are guarded by conditions. --- --| Publish | -- -- / --- | Author |--| Review |--- -- -- \--| Reject | -- If at Review.workItemFinished() both conditions are still _FALSE_ the wfmc package finishes the whole process. I think the correct behaviour should be to not to allow to finish the workitem. JF I don't think that would be correct. Maybe an exception should be raised? JF You can actually model that in xpdl using an exception, although I JF don't reflect off-hand if that is supported in zope.wfmc. JF Jim JF -- JF Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! JF CTO (540) 361-1714 http://www.python.org JF Zope Corporationhttp://www.zope.com http://www.zope.org -- Best regards, Groszer Adam -- Quote of the day: Money, not morality, is the principle commerce of civilized nations. - Thomas Jefferson - ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/dev%40projekt01.ch ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Functional testing of XML-RPC views
Hi Stephan Richter wrote: On Tuesday 19 September 2006 04:14, Christian Theune wrote: I changed the publisher xmlrpc tests to use this utility now. This has two meanings 1) Those tests now both test the XML-RPC testing utility and the publisher 2) Those tests now have a bit different semantics: Instead of comparing exact request strings for the XML-RPC message the tests now test whether the xmlrpclib is able to talk to the view. I'd like some feedback on this change before checking this in to the trunk. This is perfectly fine. The exact XML was never of interest. Alright. I've added the support for handleErrors on the branch and tested it. I'm merging it to the trunk now. Thanks for the info about the XML. Christian -- gocept gmbh co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: OpenPGP digital signature ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] buildbot failure in Zope3 trunk 2.4 Linux zc-buildbot
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 7716 Blamelist: ctheune,jukart,shh BUILD FAILED: failed test_2 sincerely, -The Buildbot ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] buildout discussion on distutils SIG
Hi there, I figured I'd let everyone here know that we'll be using the Python distutils SIG mailing list for discussions on buildout itself in the future. (Jim asked there and got a yes) I think that's the distutils SIG mailing list a great place to engage non-Zope developers as well, and buildout is good for everyone. :) I imagine discussions specific to Zope 3 buildouts should still continue on this list. Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] buildout discussion on distutils SIG
On Tuesday 19 September 2006 07:39, Martijn Faassen wrote: I figured I'd let everyone here know that we'll be using the Python distutils SIG mailing list for discussions on buildout itself in the future. (Jim asked there and got a yes) How is the traffic on that list? Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re[4]: [Zope3-dev] possible bug in zope.wfmc
Hi Roger, Tuesday, September 19, 2006, 12:08:20 PM, you wrote: Update - Final is guarded by review_result == 'accepted' Update - Issue is guarded by transitionName == 'update_issue' Update - Review is guarded by transitionName == 'update_review' RI Is this (Update - Final) not a end transaction? RI Do you mean that the end transaction concept istn't correct RI working? Taken the above example, if review_result == 'rejected' and transitionName == 'final' when I fire workItemFinished in the workflow application neither condition is true. That makes zope.wfmc think that there are no outgoing transitions and proceeds to the finishes the process. The example is bad for this, because if there would be some activities after Final they would be skipped and the whole process would be finished. Hope that makes the picture clear. RI Sorry, I don't know. but I agree that it should be a difference RI if we finsih a transaction with a Fslse or True guard. I'm trying to get some answers at http://www.workflow-research.de/Forums , which should be an official forum for WFMC. -- Best regards, Groszer Adam -- Quote of the day: Criticism, like rain, should be gentle enough to nourish a man's growth without destroying his roots. - Frank A. Clark ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Functional testing of XML-RPC views
On 9/19/06, Stephan Richter [EMAIL PROTECTED] wrote: This is perfectly fine. The exact XML was never of interest. I think this is right for most cases. Sometimes it may be (especially in the case of reported bugs and error handling), but I think that's an unusual situation. Those cases can continue to use http() without problems. I'm +1 on merging the branch as well. -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Every sin is the result of a collaboration. --Lucius Annaeus Seneca ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] buildout discussion on distutils SIG
Stephan Richter wrote: On Tuesday 19 September 2006 07:39, Martijn Faassen wrote: I figured I'd let everyone here know that we'll be using the Python distutils SIG mailing list for discussions on buildout itself in the future. (Jim asked there and got a yes) How is the traffic on that list? Not too busy, steady trickle. It depends on the discussions going on, as ever. :) Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] buildbot failure in Zope3 trunk 2.4 Linux zc-buildbot
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 7718 Blamelist: fdrake BUILD FAILED: failed test_2 sincerely, -The Buildbot ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] buildbot failure in Zope3 trunk 2.4 FreeBSD tmiddleton
The Buildbot has detected a failed build of Zope3 trunk 2.4 FreeBSD tmiddleton. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 7718 Blamelist: fdrake BUILD FAILED: failed test_2 sincerely, -The Buildbot ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] buildbot failure in Zope3 trunk 2.4 Linux zc-buildbot
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 7719 Blamelist: fdrake BUILD FAILED: failed test_2 sincerely, -The Buildbot ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] buildbot failure in Zope3 trunk 2.4 FreeBSD tmiddleton
The Buildbot has detected a failed build of Zope3 trunk 2.4 FreeBSD tmiddleton. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 7719 Blamelist: fdrake BUILD FAILED: failed test sincerely, -The Buildbot ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] buildbot failure in Zope3 trunk 2.4 Linux zc-buildbot
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 7720 Blamelist: fdrake BUILD FAILED: failed test_2 sincerely, -The Buildbot ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] buildbot failure in Zope3 trunk 2.4 FreeBSD tmiddleton
The Buildbot has detected a failed build of Zope3 trunk 2.4 FreeBSD tmiddleton. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 7720 Blamelist: fdrake BUILD FAILED: failed test_2 sincerely, -The Buildbot ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] buildbot failure in Zope3 trunk 2.4 Linux zc-buildbot
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 7731 Blamelist: alecm,fdrake,jim,srichter BUILD FAILED: failed test_2 sincerely, -The Buildbot ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] buildbot failure in Zope3 trunk 2.4 FreeBSD tmiddleton
The Buildbot has detected a failed build of Zope3 trunk 2.4 FreeBSD tmiddleton. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 7731 Blamelist: alecm,fdrake,jim,srichter BUILD FAILED: failed test_2 sincerely, -The Buildbot ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] zope.interface.Interface.(isImplementedBy vs implementedBy)
Hi All, What's the difference between these two? implementedBy is what I meant to use, by I braino'ed isImplementedBy instead. Rather than getting an AttributeError, I just got unexpected behaviour :-( Any ideas? Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
