[Zope3-dev] Zope3 unit tests

[Jim Fulton]

Jeremy Hylton wrote:
> 
> The instructions for running unit tests in the RunningUnitTests Wiki
> page say to use Zope.Testing.allZopeTests as the name to pass to
> unittest.py or unittestgui.py.  This will only run tests that are part
> of the Zope package, which isn't all of the tests!
> 
> At the moment, people using this approach don't run tests for ZODB,
> Persistence, or BTrees.  (They also miss the tests in ZopeLegacy, but
> that's a good thing.)  How can we fix these instructions so that
> people run *all* the tests except ZopeLegacy tests?
> 
> The test.py script will run all the tests except ZopeLegacy, so it
> should be good enough for the nightly test runner.  But it doesn't
> provide the GUI framework from utilities/unittestgui.py.  Perhaps
> someone could extend test.py with an option to use a GUI.

First add mention of the test script to the page.  Feel free
to point out the limitations of using allZopeTests, but also
mention that they are useful for testing local changes because they
run a little faster and because the GUI tool is sorta nice.

Jim


--
Jim Fulton           mailto:jim@zope.com       Python Powered!        
CTO                  (888) 344-4332            http://www.python.org  
Zope Corporation     http://www.zope.com       http://www.zope.org