The Zope 2.7 test suite no longer fulfills an essential unit test suite requirement: that tests can be run in isolation.
Many test files contain "import Zope; Zope.startup()". When run in isolation, many of them fail because "getConfiguration().dbtab" is "None".
Some test files seem to hande this configuration issue such that the complete test suite can be used. However, you do not want to analyse singular problems by always executing the complete test suite...
I usually use test.py --dir lib/python/some/directory to test subsections of Zope or test.py lib/python/a/file.py works too. That said I agree it would be nice to have these tests continue to work standalone as they're written. This would boil down to being able to set the ZOPE_CONFIG attribute as you advocated earlier.
- C
On Mon, 2003-12-29 at 08:33, Dieter Maurer wrote:
The Zope 2.7 test suite no longer fulfills an essential unit test suite requirement: that tests can be run in isolation.
Many test files contain "import Zope; Zope.startup()". When run in isolation, many of them fail because "getConfiguration().dbtab" is "None".
Some test files seem to hande this configuration issue such that the complete test suite can be used. However, you do not want to analyse singular problems by always executing the complete test suite...
-
Chris McDonough -
Dieter Maurer