[Zope-Coders] How to get going :-)

[Jeremy Hylton]

>>>>> "CMcD" == Chris McDonough <chrism@zope.com> writes:

  >> where's zctl.py nowdays? does it come with documentation?  Is the
  >> process for running the Zope tests the same or should I use
  >> testrunner.py?

  CMcD> This is a good question.  For now, I'd pick an existing test
  CMcD> module and ape its structure.

We need to get a better answer to this question :-).  Evan and I spent
some time reviewing testing issues last week.  I think we reached some
conclusions about how to keep the testing structure simple and
portable, meaning that it works the same way for different projects
like Zope and StandaloneZODB.

Evan-- Were you going to post anything about this?  Or should I?  We
really ought to write down what we talked about before we both forget
it all.

There's a further step to testing, which is to require that before you
check something in you should run the tests and make sure you haven't
broken anything.  I assume that the testrunner script is the right way
for Zope.  If you make changes in ZODB, BTrees, ZEO, etc., you should
also run the StandaloneZODB test suite.

There are a bunch of tests that fail when you run the Zope testrunner
from the trunk.  We should fix those ASAP, because external developers
shouldn't be committing changes while our own code is in an unknown
state.

Jeremy