[soc2008-general] unit testing the standard library
Titus Brown
titus at caltech.edu
Tue Mar 25 23:09:19 CET 2008
On Tue, Mar 25, 2008 at 11:10:32PM +0100, Christian Heimes wrote:
-> Brett Cannon schrieb:
-> > Possibly. We need:
-> >
-> > * A function that imports the module being tested so that if it isn't
-> > imported the test is skipped, but all other import failures are an
-> > error.
-> > * Some way to specify what OSs the test can be run on, both expected
-> > and optionally.
-> > * A way to denote whitebox tests specific for CPython.
-> > * Rewrite regrtest to use all of this new stuff.
-> >
-> > That's everything I ever had an idea for. Most of it, though, is not
-> > overly complex (maybe the regrtest rewrite since that file has grown
-> > organically).
->
-> I also like to see:
->
-> * a way to execute a single test easily, for example
->
-> $ python regrtest.py test_sys:SysModuleTest.test_original_displayhook
->
-> * A simple way to record all failing unit tests and re-test just the
-> failing test functions
->
-> $ python regrtest.py --record
-> $ python regrtest.py --replay
->
-> * a bullet proof and reliable infrastructure to set up socket based and
-> threaded tests
->
-> * infrastructure for common operations like creating and removing a file
oooh, nice suggestions!
--titus
More information about the soc2008-general
mailing list