[Zope-Coders] Shane's nightly test vs. my fresh checkout

[Tres Seaver]

Jeffrey P Shell wrote:

> On Tuesday, November 20, 2001, at 05:27  AM, Tres Seaver wrote:
> 
>>
>> BTW, I have checked in changes on a branch,
>> 'tseaver-utxr-refactoring-branch', which make it possible to
>> run all tests using the GUI testrunner;  I think we may be able
>> to promote running them this way as the standard::
>>
>>   $ cvs -q up -r tseaver-utxr-refactoring-branch
>>   $ PYTHONPATH=`pwd`/lib/python:`pwd` python2.1 \
>>     /home/tseaver/projects/unittestgui.py \
>>     Testing.Builder.allZopeTests
>>
> 
> Why use the GUI one as the standard?  Should it not matter if the tests 
> run from either the pure text or the GUI?  If testrunner.py is giving 
> spurious results, maybe its time to do a solid revamp of it to take 
> advantage of newer PyUnit features.


I'm not insisting on the GUI, but I do think that relying on the
ugly special hackery done by testrunner is contributing to our
testability problems.  Using the stock 'unittest.py' shipped with
Python would be equally useful::

    $ PYTHONPATH=`pwd`/lib/python:`pwd` python2.1 \
      /usr/local/lib/python2.2/unittest.py \
      Testing.allZopeTests

The GUI is actually nicer to use (and yes, you heard *me* say
that! :), because it collects the tracebacks into an introspectable
structure, rather than spewing them to standard output.  Getting
the brainstem's "red is danger" response involved is good, too. :)

Tres.
-- 
===============================================================
Tres Seaver                                tseaver@zope.com
Zope Corporation      "Zope Dealers"       http://www.zope.com