[Python-Dev] no expected test output for test_sort? (original) (raw)

Walter D�rwald walter@livinglogic.de
Wed, 08 Jan 2003 19:25:24 +0100

Guido van Rossum wrote:

So should I go on with this? Do we want to change all tests before 2.3 is finished, or start changing them after 2.3 is released (or something in between)?

I'd say something in between. It's probably good if someone (not me) reviews your patches.

Definitely. Any volunteers?

It's never good to rush these things, and I've said before that there's no reason to insist on all tests being PyUnit tests. (Definitely don't touch anything that's using doctest.)

I won't. I'll start with the easy ones.

In particular, I don't want you to literally translate existing tests to PyUnit idiom. Try to improve on the tests -- think about end cases, etc.

I would find it easier to do this in two steps. Enhancing the tests takes time, so the test will change in CVS and I'd have to keep track of the changes. I'd prefer to check in the 1:1 port as soon as possible and enhance the tests afterwards.

There are coverage tools (ask Skip) -- when testing Python modules, see if the test covers all code in the module!

Bye, Walter D�rwald