I just checked in a new test runner on the trunk. It is mostly backward compatible with the old test runner. You can get help on the test runner by running it with -h. There is more extensive documentation in lib/python/zope/testing/testrunner.txt. Note that the new test runner complains if test_suite functions don't return test suites. There is a zope.i18n test suite that it currently complains about. Unfortunately, I can't just fix this because it is an svn:external and it will be too painful to create a tag with the necessary fix in the short term. I expect we will be integrating a newer version of Zope 3 later in the week and we'll take care of this then. Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jim Fulton wrote:
I just checked in a new test runner on the trunk. It is mostly backward compatible with the old test runner. You can get help on the test runner by running it with -h. There is more extensive documentation in lib/python/zope/testing/testrunner.txt.
Note that the new test runner complains if test_suite functions don't return test suites. There is a zope.i18n test suite that it currently complains about. Unfortunately, I can't just fix this because it is an svn:external and it will be too painful to create a tag with the necessary fix in the short term. I expect we will be integrating a newer version of Zope 3 later in the week and we'll take care of this then.
I'm seeing test failures out of the self-tests for the new testrunner: Failure in test /home/tseaver/projects/Zope-CVS/Zope-SVN-trunk/lib/python/zope/testing/testrunner-coverage.txt Failed doctest test for testrunner-coverage.txt File "/home/tseaver/projects/Zope-CVS/Zope-SVN-trunk/lib/python/zope/testing/testrunner-coverage.txt", line 0 - ---------------------------------------------------------------------- File "/home/tseaver/projects/Zope-CVS/Zope-SVN-trunk/lib/python/zope/testing/testrunner-coverage.txt", line 20, in testrunner-coverage.txt Failed example: testrunner.run(defaults) Expected: Running unit tests: ... lines cov% module (path) ... testrunner.py) ... Got: Running unit tests: Ran 192 tests with 0 failures and 0 errors in N.NNN seconds. Running samplelayers.Layer1 tests: Set up samplelayers.Layer1 in N.NNN seconds. Ran 9 tests with 0 failures and 0 errors in N.NNN seconds. Running samplelayers.Layer11 tests: Set up samplelayers.Layer11 in N.NNN seconds. Ran 34 tests with 0 failures and 0 errors in N.NNN seconds. Running samplelayers.Layer111 tests: Set up samplelayers.Layerx in N.NNN seconds. Set up samplelayers.Layer111 in N.NNN seconds. Ran 34 tests with 0 failures and 0 errors in N.NNN seconds. Running samplelayers.Layer112 tests: Tear down samplelayers.Layer111 in N.NNN seconds. Set up samplelayers.Layer112 in N.NNN seconds. Ran 34 tests with 0 failures and 0 errors in N.NNN seconds. Running samplelayers.Layer12 tests: Tear down samplelayers.Layer112 in N.NNN seconds. Tear down samplelayers.Layerx in N.NNN seconds. Tear down samplelayers.Layer11 in N.NNN seconds. Set up samplelayers.Layer12 in N.NNN seconds. Ran 34 tests with 0 failures and 0 errors in N.NNN seconds. Running samplelayers.Layer121 tests: Set up samplelayers.Layer121 in N.NNN seconds. Ran 34 tests with 0 failures and 0 errors in N.NNN seconds. Running samplelayers.Layer122 tests: Tear down samplelayers.Layer121 in N.NNN seconds. Set up samplelayers.Layer122 in N.NNN seconds. Ran 34 tests with 0 failures and 0 errors in N.NNN seconds. Tearing down left over layers: Tear down samplelayers.Layer122 in N.NNN seconds. Tear down samplelayers.Layer12 in N.NNN seconds. Tear down samplelayers.Layer1 in N.NNN seconds. Total: 405 tests, 0 failures, 0 errors False - ---------------------------------------------------------------------- File "/home/tseaver/projects/Zope-CVS/Zope-SVN-trunk/lib/python/zope/testing/testrunner-coverage.txt", line 30, in testrunner-coverage.txt Failed example: os.path.exists('coverage_dir') Expected: True Got: False - ---------------------------------------------------------------------- File "/home/tseaver/projects/Zope-CVS/Zope-SVN-trunk/lib/python/zope/testing/testrunner-coverage.txt", line 32, in testrunner-coverage.txt Failed example: os.listdir('coverage_dir') Exception raised: Traceback (most recent call last): File "/home/tseaver/projects/Zope-CVS/Zope-SVN-trunk/lib/python/zope/testing/doctest.py", line 1256, in __run compileflags, 1) in test.globs File "<doctest testrunner-coverage.txt[7]>", line 1, in ? OSError: [Errno 2] No such file or directory: 'coverage_dir' - ---------------------------------------------------------------------- File "/home/tseaver/projects/Zope-CVS/Zope-SVN-trunk/lib/python/zope/testing/testrunner-coverage.txt", line 38, in testrunner-coverage.txt Failed example: shutil.rmtree('coverage_dir') Exception raised: Traceback (most recent call last): File "/home/tseaver/projects/Zope-CVS/Zope-SVN-trunk/lib/python/zope/testing/doctest.py", line 1256, in __run compileflags, 1) in test.globs File "<doctest testrunner-coverage.txt[9]>", line 1, in ? File "/home/tseaver/projects/Zope-CVS/lib/python2.3/shutil.py", line 142, in rmtree raise exc[0], (exc[1][0], exc[1][1] + ' removing '+arg) OSError: [Errno 2] No such file or directory removing coverage_dir .............. .................................................. .. Ran 7352 tests with 1 failures and 0 errors in 329.098 seconds. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDX3nh+gerLs4ltQ4RAnGmAJ9aNNuYiu9l0CIP19iS9UFFAkZsGwCg1zxx u1f3+8LRfQvX7qI4ktbHTw8= =R1zX -----END PGP SIGNATURE-----
Weird. I can't reproduce this. Is anyone else seeing this? Jim Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Jim Fulton wrote:
I just checked in a new test runner on the trunk. It is mostly backward compatible with the old test runner. You can get help on the test runner by running it with -h. There is more extensive documentation in lib/python/zope/testing/testrunner.txt.
Note that the new test runner complains if test_suite functions don't return test suites. There is a zope.i18n test suite that it currently complains about. Unfortunately, I can't just fix this because it is an svn:external and it will be too painful to create a tag with the necessary fix in the short term. I expect we will be integrating a newer version of Zope 3 later in the week and we'll take care of this then.
I'm seeing test failures out of the self-tests for the new testrunner:
Failure in test /home/tseaver/projects/Zope-CVS/Zope-SVN-trunk/lib/python/zope/testing/testrunner-coverage.txt Failed doctest test for testrunner-coverage.txt File "/home/tseaver/projects/Zope-CVS/Zope-SVN-trunk/lib/python/zope/testing/testrunner-coverage.txt", line 0
- ---------------------------------------------------------------------- File "/home/tseaver/projects/Zope-CVS/Zope-SVN-trunk/lib/python/zope/testing/testrunner-coverage.txt", line 20, in testrunner-coverage.txt Failed example: testrunner.run(defaults) Expected: Running unit tests: ... lines cov% module (path) ... testrunner.py) ... Got: Running unit tests: Ran 192 tests with 0 failures and 0 errors in N.NNN seconds. Running samplelayers.Layer1 tests: Set up samplelayers.Layer1 in N.NNN seconds. Ran 9 tests with 0 failures and 0 errors in N.NNN seconds. Running samplelayers.Layer11 tests: Set up samplelayers.Layer11 in N.NNN seconds. Ran 34 tests with 0 failures and 0 errors in N.NNN seconds. Running samplelayers.Layer111 tests: Set up samplelayers.Layerx in N.NNN seconds. Set up samplelayers.Layer111 in N.NNN seconds. Ran 34 tests with 0 failures and 0 errors in N.NNN seconds. Running samplelayers.Layer112 tests: Tear down samplelayers.Layer111 in N.NNN seconds. Set up samplelayers.Layer112 in N.NNN seconds. Ran 34 tests with 0 failures and 0 errors in N.NNN seconds. Running samplelayers.Layer12 tests: Tear down samplelayers.Layer112 in N.NNN seconds. Tear down samplelayers.Layerx in N.NNN seconds. Tear down samplelayers.Layer11 in N.NNN seconds. Set up samplelayers.Layer12 in N.NNN seconds. Ran 34 tests with 0 failures and 0 errors in N.NNN seconds. Running samplelayers.Layer121 tests: Set up samplelayers.Layer121 in N.NNN seconds. Ran 34 tests with 0 failures and 0 errors in N.NNN seconds. Running samplelayers.Layer122 tests: Tear down samplelayers.Layer121 in N.NNN seconds. Set up samplelayers.Layer122 in N.NNN seconds. Ran 34 tests with 0 failures and 0 errors in N.NNN seconds. Tearing down left over layers: Tear down samplelayers.Layer122 in N.NNN seconds. Tear down samplelayers.Layer12 in N.NNN seconds. Tear down samplelayers.Layer1 in N.NNN seconds. Total: 405 tests, 0 failures, 0 errors False - ---------------------------------------------------------------------- File "/home/tseaver/projects/Zope-CVS/Zope-SVN-trunk/lib/python/zope/testing/testrunner-coverage.txt", line 30, in testrunner-coverage.txt Failed example: os.path.exists('coverage_dir') Expected: True Got: False - ---------------------------------------------------------------------- File "/home/tseaver/projects/Zope-CVS/Zope-SVN-trunk/lib/python/zope/testing/testrunner-coverage.txt", line 32, in testrunner-coverage.txt Failed example: os.listdir('coverage_dir') Exception raised: Traceback (most recent call last): File "/home/tseaver/projects/Zope-CVS/Zope-SVN-trunk/lib/python/zope/testing/doctest.py", line 1256, in __run compileflags, 1) in test.globs File "<doctest testrunner-coverage.txt[7]>", line 1, in ? OSError: [Errno 2] No such file or directory: 'coverage_dir' - ---------------------------------------------------------------------- File "/home/tseaver/projects/Zope-CVS/Zope-SVN-trunk/lib/python/zope/testing/testrunner-coverage.txt", line 38, in testrunner-coverage.txt Failed example: shutil.rmtree('coverage_dir') Exception raised: Traceback (most recent call last): File "/home/tseaver/projects/Zope-CVS/Zope-SVN-trunk/lib/python/zope/testing/doctest.py", line 1256, in __run compileflags, 1) in test.globs File "<doctest testrunner-coverage.txt[9]>", line 1, in ? File "/home/tseaver/projects/Zope-CVS/lib/python2.3/shutil.py", line 142, in rmtree raise exc[0], (exc[1][0], exc[1][1] + ' removing '+arg) OSError: [Errno 2] No such file or directory removing coverage_dir
.............. .................................................. .. Ran 7352 tests with 1 failures and 0 errors in 329.098 seconds.
Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDX3nh+gerLs4ltQ4RAnGmAJ9aNNuYiu9l0CIP19iS9UFFAkZsGwCg1zxx u1f3+8LRfQvX7qI4ktbHTw8= =R1zX -----END PGP SIGNATURE-----
-- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jim Fulton wrote:
Weird. I can't reproduce this. Is anyone else seeing this?
For the benefit of those playing along at home: Jim and I discovered this evening that we were running on mostly-identical platforms (Ubuntu "Breezy" 5.10, Python 2.3.5 compiled from source). The only difference we could find was that I had rebuilt my Pythnon using GCC 4.0, while Jim's was one built under GCC 3.3. Go figure, Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDYEk7+gerLs4ltQ4RAvy1AKDIg4aoolifM8sKb/SLZkr7VANfyQCgzboL tIBd+gk++ECvgONcouW7KPA= =wJEw -----END PGP SIGNATURE-----
Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Jim Fulton wrote:
Weird. I can't reproduce this. Is anyone else seeing this?
For the benefit of those playing along at home:
Jim and I discovered this evening that we were running on mostly-identical platforms (Ubuntu "Breezy" 5.10, Python 2.3.5 compiled from source).
The only difference we could find was that I had rebuilt my Pythnon using GCC 4.0, while Jim's was one built under GCC 3.3.
Go figure,
Sigh. I rebuilt Python 2.3.5: jim@voyager:~/p/z2/2$ /usr/local/python/2.3.5b/bin/python Python 2.3.5 (#1, Oct 27 2005, 10:22:20) [GCC 4.0.2 20050808 (prerelease) (Ubuntu 4.0.1-4ubuntu9)] on linux2 Type "help", "copyright", "credits" or "license" for more information.
I don't get a test failure with this Python: cd ~/p/z2/2/ /usr/local/python/2.3.5b/bin/python test.py -szope.testing Running tests at level 1 Running unit tests: Running: .................................................. ....................................... Ran 89 tests with 0 failures and 0 errors in 32.003 seconds. Compilation finished at Thu Oct 27 11:04:40 Is anyone else getting this test failure? Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jim Fulton wrote:
Sigh.
I rebuilt Python 2.3.5:
jim@voyager:~/p/z2/2$ /usr/local/python/2.3.5b/bin/python Python 2.3.5 (#1, Oct 27 2005, 10:22:20) [GCC 4.0.2 20050808 (prerelease) (Ubuntu 4.0.1-4ubuntu9)] on linux2 Type "help", "copyright", "credits" or "license" for more information.
I don't get a test failure with this Python:
cd ~/p/z2/2/ /usr/local/python/2.3.5b/bin/python test.py -szope.testing Running tests at level 1 Running unit tests: Running: .................................................. ....................................... Ran 89 tests with 0 failures and 0 errors in 32.003 seconds.
Compilation finished at Thu Oct 27 11:04:40
Is anyone else getting this test failure?
Just to note that the tests aren't running cleanly on Stefan Holek's box, either (but they fail differently): http://mail.zope.org/pipermail/zope-tests/2005-October/003421.html http://mail.zope.org/pipermail/zope-tests/2005-October/003422.html Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDYPj0+gerLs4ltQ4RAv6bAJ4jZvj3unZ2mupaMKFVK0886+iuvgCgvi3I ka6+lOBnQ9l34slY+oD7kR8= =b/x2 -----END PGP SIGNATURE-----
Tres Seaver wrote: ...
Just to note that the tests aren't running cleanly on Stefan Holek's box, either (but they fail differently):
http://mail.zope.org/pipermail/zope-tests/2005-October/003421.html
http://mail.zope.org/pipermail/zope-tests/2005-October/003422.html
These are not failures. They are also not complete output. I'm hoping that Stefan will look at this. We also plan to add zope 2 to the buildbot config. It would be nice is someone would address the deprecation warning by getting rid of the whrandom reference. :) Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jim Fulton wrote:
Tres Seaver wrote: ...
Just to note that the tests aren't running cleanly on Stefan Holek's box, either (but they fail differently):
http://mail.zope.org/pipermail/zope-tests/2005-October/003421.html
http://mail.zope.org/pipermail/zope-tests/2005-October/003422.html
These are not failures. They are also not complete output.
I'm hoping that Stefan will look at this.
We also plan to add zope 2 to the buildbot config.
It would be nice is someone would address the deprecation warning by getting rid of the whrandom reference. :)
Jim
FWIW: $ pwd /home/tseaver/projects/Zope-CVS/Zope-2_8-branch $ find . -name "*.py" | grep -v "build-base" | xargs grep -l whrandom ./lib/python/AccessControl/DTML.py ./lib/python/Products/PythonScripts/help/PythonScript.py ./lib/python/Products/ZCatalog/regressiontests/regressionCatalog.py ./lib/python/Products/ZCatalog/regressiontests/loadmail.py ./lib/python/RestrictedPython/Utilities.py ./lib/python/DocumentTemplate/DT_Util.py ./lib/python/zope/security/examples/sandbox.py ./lib/python/zope/security/examples/sandbox_security.py The 'regressiontest' cases have been ripped out on the trunk already. For 2.8, we can't rip out the 'AccessControl/DTML.py' version without breaking third-party code which uses it in DTML. Here is what it does: import SecurityManagement, string, math, whrandom, random ... whrandom.__allow_access_to_unprotected_subobjects__=1 random.__allow_access_to_unprotected_subobjects__=1 Likewise RestrictedPython/Utilities.py: import string, math, random, whrandom ... utility_builtins = {} ... utility_builtins['random'] = random utility_builtins['whrandom'] = whrandom The Zope3 stuff could likely be replaced (e.g. for a 3.0.2 release), and should be gone for 2.9 / 3.2. Hmm, I see that RestrictedPython/Utilities.py on the Z3 trunk aliases 'random' as 'whrandom' -- could we use that strategy for 2.8 etc.? We could remove them for 2.9, I guess, and just make people fix their applications. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDYRtT+gerLs4ltQ4RAtvdAKDMKwFPaRysMkNa6c/k1f70YkWYNgCfRvcu xqLrTdDlDHrY41PhmyFPIiI= =zd+o -----END PGP SIGNATURE-----
Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE-----
FWIW:
Alot. :)
$ pwd /home/tseaver/projects/Zope-CVS/Zope-2_8-branch $ find . -name "*.py" | grep -v "build-base" | xargs grep -l whrandom ./lib/python/AccessControl/DTML.py ./lib/python/Products/PythonScripts/help/PythonScript.py ./lib/python/Products/ZCatalog/regressiontests/regressionCatalog.py ./lib/python/Products/ZCatalog/regressiontests/loadmail.py ./lib/python/RestrictedPython/Utilities.py ./lib/python/DocumentTemplate/DT_Util.py
./lib/python/zope/security/examples/sandbox.py ./lib/python/zope/security/examples/sandbox_security.py
Sigh. ...
Hmm, I see that RestrictedPython/Utilities.py on the Z3 trunk aliases 'random' as 'whrandom' -- could we use that strategy for 2.8 etc.?
Yes. random has the same documented functions and signatures as whrandon.
We could remove them for 2.9, I guess, and just make people fix their applications.
I suggest we make aliases and generate deprecation warnings if whrandom is used. (The later may be tricky, I realize.) Maybe for now, just make aliases and move on. :) Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jim Fulton wrote:
Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE-----
FWIW:
Alot. :)
$ pwd /home/tseaver/projects/Zope-CVS/Zope-2_8-branch $ find . -name "*.py" | grep -v "build-base" | xargs grep -l whrandom ./lib/python/AccessControl/DTML.py ./lib/python/Products/PythonScripts/help/PythonScript.py ./lib/python/Products/ZCatalog/regressiontests/regressionCatalog.py ./lib/python/Products/ZCatalog/regressiontests/loadmail.py ./lib/python/RestrictedPython/Utilities.py ./lib/python/DocumentTemplate/DT_Util.py
./lib/python/zope/security/examples/sandbox.py ./lib/python/zope/security/examples/sandbox_security.py
Sigh.
...
Hmm, I see that RestrictedPython/Utilities.py on the Z3 trunk aliases 'random' as 'whrandom' -- could we use that strategy for 2.8 etc.?
Yes. random has the same documented functions and signatures as whrandon.
We could remove them for 2.9, I guess, and just make people fix their applications.
I suggest we make aliases and generate deprecation warnings if whrandom is used. (The later may be tricky, I realize.)
Maybe for now, just make aliases and move on. :)
Jim
I have aliased 'random' to 'whrandom' in AccessControl.DTML and RestrictedPython.Utilities on the 2.8 branch and the 2.9 branch, and added comments noting BBB to be removed in Zope 2.10. I removed all mention of 'whrandom' the trunk. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDg02l+gerLs4ltQ4RAka7AJ9KMqjSPLf7z7PmMVXYJtxjRcfhhwCgk0/G rpQ/pfqd/bI+6Bae7GFKX9M= =PfQh -----END PGP SIGNATURE-----
Cool, thanks! Jim Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Jim Fulton wrote:
Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE-----
FWIW:
Alot. :)
$ pwd /home/tseaver/projects/Zope-CVS/Zope-2_8-branch $ find . -name "*.py" | grep -v "build-base" | xargs grep -l whrandom ./lib/python/AccessControl/DTML.py ./lib/python/Products/PythonScripts/help/PythonScript.py ./lib/python/Products/ZCatalog/regressiontests/regressionCatalog.py ./lib/python/Products/ZCatalog/regressiontests/loadmail.py ./lib/python/RestrictedPython/Utilities.py ./lib/python/DocumentTemplate/DT_Util.py
./lib/python/zope/security/examples/sandbox.py ./lib/python/zope/security/examples/sandbox_security.py
Sigh.
...
Hmm, I see that RestrictedPython/Utilities.py on the Z3 trunk aliases 'random' as 'whrandom' -- could we use that strategy for 2.8 etc.?
Yes. random has the same documented functions and signatures as whrandon.
We could remove them for 2.9, I guess, and just make people fix their applications.
I suggest we make aliases and generate deprecation warnings if whrandom is used. (The later may be tricky, I realize.)
Maybe for now, just make aliases and move on. :)
Jim
I have aliased 'random' to 'whrandom' in AccessControl.DTML and RestrictedPython.Utilities on the 2.8 branch and the 2.9 branch, and added comments noting BBB to be removed in Zope 2.10.
I removed all mention of 'whrandom' the trunk.
Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDg02l+gerLs4ltQ4RAka7AJ9KMqjSPLf7z7PmMVXYJtxjRcfhhwCgk0/G rpQ/pfqd/bI+6Bae7GFKX9M= =PfQh -----END PGP SIGNATURE-----
-- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org
On Tue, Oct 25, 2005 at 03:13:11PM -0400, Jim Fulton wrote:
I just checked in a new test runner on the trunk. It is mostly backward compatible with the old test runner. You can get help on the test runner by running it with -h. There is more extensive documentation in lib/python/zope/testing/testrunner.txt.
Somewhere I believe you said that the new testrunner is backward-compatible with the old testrunner's positional arguments used as regexes for matching modules. Not a big deal to me, but AFAICT this is not true with a current Zope2 trunk sandbox: pw@kermit Zope-Trunk $ ./bin/zopectl test -m "AcceleratedHTTP.*" Running tests via: /usr/bin/python /home/pw/Downloads/Apps/Net/Zope-Trunk/test.py -v --config-file /home/pw/Downloads/Apps/Net/Zope-Trunk/etc/zope.conf -m AcceleratedHTTP.* Parsing /home/pw/Downloads/Apps/Net/Zope-Trunk/etc/zope.conf Running tests at level 1 Running unit tests: Running: . Ran 1 tests with 0 failures and 0 errors in 0.246 seconds. pw@kermit Zope-Trunk $ ./bin/zopectl test "AcceleratedHTTP.*" Running tests via: /usr/bin/python /home/pw/Downloads/Apps/Net/Zope-Trunk/test.py -v --config-file /home/pw/Downloads/Apps/Net/Zope-Trunk/etc/zope.conf AcceleratedHTTP.* Parsing /home/pw/Downloads/Apps/Net/Zope-Trunk/etc/zope.conf Running tests at level 1 Running unit tests: Running: .................................................. (snip) .................................... Ran 4336 tests with 0 failures and 0 errors in 399.069 seconds. -- Paul Winkler http://www.slinkp.com
participants (3)
-
Jim Fulton -
Paul Winkler -
Tres Seaver