A Call For Removal: Custom Zope Product Test Runners
We’ve had the standard zope test runner with ‘zopectl test’ for a while now. But a lot (most?) of existing third-party products distribute their own runalltests.py and related files. This means as a contributor to any of these products a person has to make sure the tests run properly with runalltests.py and zopectl test which unfortunately often doesn’t run in the same manner.
So I put it out there that everyone stop providing their own custom test runners with their products. In fact, remove custom test runners that in your source control trunks of your products. We have the standard Zope test runner, lets just use that.
If someone doesn’t like the output or some other artifact of the standard Zope test runner, they should define their own local test runner, but don’t force everyone else to use it. And still be sure your tests run properly with the standard Zope test runner.
Hear, hear! We came to this same conclusion awhile back with FacultyStaffDirectory, tearing out the custom test entry point that ArchGenXML put in.
Comment by Erik Rose — Aug 4, 2008 5:46:04 PM | # - re
Comment waiting for approval