The proposal below is in the fishbowl, at
http://dev.zope.org/Wikis/DevSite/Proposals/UnitTestingProducts
The approach will be, developing the standalone ZUnit Product
while the proposal is in the fishbowl, then push for the
proposal (integrating it with App/Product*.py). Expect a first
The proposal below is in the fishbowl, at
http://dev.zope.org/Wikis/DevSite/Proposals/UnitTestingProducts
The approach will be, developing the standalone ZUnit Product
while the proposal is in the fishbowl, then push for the
proposal (integrating it with App/Product*.py). Expect a first
release
What do people think of this? What does DC think of this? Can I
go ahead and develop it in this direction?
For our XP endeavors, we've developed a testing framework we call
SimpleTest, which tests our systems using HTTP requests. Tests are
written in XML, along the lines of:
?xml
Lalo Martins [EMAIL PROTECTED] writes:
Then I figured in the long run a Product isn't the best
sollution; instead, fiddling with App/Product* sounds more like
it, to allow developers to register tests just like they
register classes, ZClass superclasses, _misc and help. Of
course, just like
We (I and Hiperlógica) started to develop a Product we called
ZUnit, intended for XP-style unit-testing Python-based
Products in a full Zope environment (with a real ZODB, REQUEST,
RESPONSE, etc).
We first conceived it as a kind of Zope-based version of
unittestgui.py - you create a "TestRunner"
nt: Monday, October 23, 2000 8:56 PM
Subject: [Zope-dev] Unit testing, ZUnit
We (I and Hiperlógica) started to develop a Product we called
ZUnit, intended for XP-style unit-testing Python-based
Products in a full Zope environment (with a real ZODB, REQUEST,
RESPONSE, etc).
We first conceived it
What do people think of this?
you get my vote
kapil
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
