Well, one method of attack is to develop the guts of your Product as a
Python-only layer. Do all the "hard stuff" in the Python-only part of
your Product. Develop unit tests to go along with this layer. Then,
when you're ready to Zope-ify it, wrap a thin Zope layer around it.
This works well with "small" products. The ZCatalog seems to have been
developed this way.
> -----Original Message-----
> From: Stefane Fermigier [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 15, 2000 4:20 PM
> To: [EMAIL PROTECTED]
> Subject: [Zope-dev] Re: unit testing framework proposal
> > Message: 2
> > From: Chris McDonough <[EMAIL PROTECTED]>
> > To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
> > Subject: [Zope-dev] unit testing framework proposal
> > Date: Tue, 15 Aug 2000 14:10:14 -0400
> > Please see
> http://dev.zope.org/Wikis/DevSite/Proposals/UnitTestingFramework for a
> > propsal for inclusion of a unit testing framework within
> Zope. Comments
> > appreciated.
> I'm also very tempted to use systematically unit testing when
> Zope products, but I don't quite get how to do it, since Zope products
> are so integrated within a whole framework.
> Stéfane Fermigier, Tel: 06 63 04 12 77 (mobile).
> <www.portalux.com>: le portail Linux / logiciel libre.
> "Amazon: we patent the dot in .com"
> Zope-Dev maillist - [EMAIL PROTECTED]
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://lists.zope.org/mailman/listinfo/zope )
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -