Resources for zope testing.

• Zope Product Developer's Guide: Zope Unit Testing
• Zope Developer's Guide: Chapter 7, Testing and Debugging
• http://dev.zope.org/CVS/ZopeTestingGuidelines
• http://dev.zope.org/Wikis/DevSite/Proposals/CleanUpAndUnifyCoreUnitTests
• Tres Seaver's FunctionalTests product provides support for writing functional tests, especially if you use ZEO.
• Puffin
• ZopeThree:RunningUnitTests
• ZopeThree:FunctionalTestingFramework
• The Nlpi Test Architecture "Because Nlpi is a rather complex and specialized software development application, it is very error prone. Basic components are a ZClass? product with several nested ZClasses? and a mix-in python product class whose classes call complex binaries (basically inform compilers, resource packagers and corresponding code interpreters). The ZClass? can be seen as the control/viewer layer and the python class as the underlying model layer. This document tries to describe the testing strategy which was used to stabilize it."
• Literate Testing - Automated Testing with doctest (pycon 2004)
• Adept , a declarative test framework (pycon 2004)
• ZopeTestCase
• PloneTestCase?
• mechanize support in CMFPlone?/ftests

Running unit tests

The hardest thing about Zope unit tests is running them. It is the blackest of black arts. Of the above, only ZopeThree:RunningUnitTests tackles this. Your best bet as of 2004/04 is probably to wrestle with Zope-2.7.0/test.py.

Until you get lucky. Here are recipes that worked for me (using the SimpleDirectoryLayout):

run test file directly

SOFTWARE_HOME=/zope/lib/python INSTANCE_HOME=/zope1 PYTHONPATH=/zope/lib/python python tests/testAdmin.py

run test file using old testrunner.py --

run test file using Zope 2.7 test.py --