[Zope-ZEO] Advice

[Chris McDonough]

> >But there are
> >really
> >two ways to do this, either of which is viable.
>
> 1. the right way ;-)
>
> >2.  Code all of your logic using TTW stuff and Zope components.  Use the
> >    Publisher.Test.test method to call methods of your Zope components
> >    in unit tests.
>
> Do you really think this is a viable approach for a product with a
> non-trivial amount of logic?

I'm afraid we are getting way off the topic of ZEO here, but... I think this
is important, so...

I do think it's a viable approach.  Testing, and in particular, unit
testing, is mostly about making assertions based on the return value of a
call.  Publisher.test.test aka Zope.debug allows you to make assertions
against returns of things that require the availability of REQUEST,
RESPONSE, mapply stuff, form variable mangling, etc. without needing to put
all this scaffolding into place manually.