don't test any of that here.)

  - include a test suite declaration

  - slight clarification on some of the test names and content ids

(distutils mungs it anyway, so it's just relevant for developers)

Special Users and security managers that return None objects should not play.

_setObject method.

Specifically the key for 'Owner' local role should be the user's Id,
not UserName

Tests this behavior with six combinations:

  'None' security manager attempting to set ownership
  'Emergency User' security manager attempting to set ownership
  'System User' security manager attempting to set ownership
  'Anonymous User' security manager attempting to set ownership
  'User' security manager attempting to set ownership
  'Faux User' security manager attempting to set ownership

  'None' security manager not attempting to set ownership
  'Emergency User' security manager not attempting to set ownership
  'System User' security manager not attempting to set ownership
  'Anonymous User' security manager not attempting to set ownership
  'User' security manager not attempting to set ownership
  'Faux User' security manager not attempting to set ownership

when external user folders can specify a difference.

Uniform handling of errors is get_suite() allows this code to be
simplified.

Add docstring that explains rules for finding tests.
Reflow some paragraphs.

Remove 'python2.2' and 'python2.1' as acceptable executable names, as we're only interested in working under 2.3 now.

Python 2.2.3 and older are no longer acceptable versions of Python to use to run Zope 2.7+, as the logging package was removed from Zope proper and Zope requires it to start up.  The logging package exists in Python 2.3 and better.

Script (Python) objects now have a _filepath attribute, also used as the '__file__' global at runtime.  This prevents an import problem caused by the fix to #1074.

Wait 10 seconds to reload page after a restart.  On slower machines or machines with large databases, Zope can take a long time to restart and when the meta-refresh comes back before the server is up, it raises a browser error.  People who know what it does won't wait, and bumping up the timeout will help mitigate a FA
Q on the Zope lists and in the collector from those who don't.

attribute on databases.

   which is way too small with 4 lines. Increased it to 8 lines.

     - The DateTime module did not recognize the settings for
       "datetime-format".

settings from zope.conf. Because getConfiguration().datetime_format
can be expensive we provide a method getDefaultDateFormat() that
cache the value once retrieved from the configuration machinery.
Ugly (as the DateTime module) but it works.

Removing the import and call allows the tests to pass.

This code is a complete mystery.  It wasn't failing when I ran the
tests yesterday.  But if I do a checkout -D "yesterday," it fails with
an error on the Zope.startup() call.  It looks like that code should
have always failed.  No idea how it ever worked.

that these tests can fail for bogus reasons.  Jeremy saw them failing
today, and it took a while to figure out that this had nothing to do with
the ZODB changes he was making.

We'd like to deprecate explanation manipulation of a Persistent
object's _p_jar attribute.  Also use less obscure _p_deactivate()
call.

Revise comments and add assertions that object is stored and ghosted.

you to use scripts which require arguments under zopectl run.

If you do "zopectl run scriptname.py arg1 arg2", the value of sys.argv within the script will consist of ['scriptname.py', 'arg1', 'arg2'].

test_monitor_factory_with_emergency_user:  Two more that failed on
Windows, and still do, but later now.

and still fail, but later now.