[Python-Dev] Checking in a broken test was: Re: [Python-checkins]r41940 (original) (raw)
"Martin v. Löwis" martin at v.loewis.de
Sun Jan 15 20:45:32 CET 2006
- Previous message: [Python-Dev] Checking in a broken test was: Re: [Python-checkins]r41940 - python/trunk/Lib/test/test_compiler.py
- Next message: [Python-Dev] Checking in a broken test was: Re: [Python-checkins]r41940 - python/trunk/Lib/test/test_compiler.py
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Collin Winter wrote:
When I've implemented this kind of thing in the past, I've generally called the decorator/marker/whatever "TODO" (or some variation of caps/lowercase).
I usually call things TODO if they need to be done. The test case is not "TODO", since it is already done. "TODO" would be the place in the code that needs to change; for an expected failure, you might not even know where that code is.
Regards, Martin
- Previous message: [Python-Dev] Checking in a broken test was: Re: [Python-checkins]r41940 - python/trunk/Lib/test/test_compiler.py
- Next message: [Python-Dev] Checking in a broken test was: Re: [Python-checkins]r41940 - python/trunk/Lib/test/test_compiler.py
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]