On 9 January 2006, Scott David Daniels wrote: > There has been a bit of discussion about a way of providing test cases > in a test suite that _should_ work but don't. One of the rules has been > the test suite should be runnable and silent at every checkin. Recently > there was a checkin of a test that _should_ work but doesn't. The > discussion got around to means of indicating such tests (because the > effort of creating a test should be captured) without disturbing the > development flow. > > The following code demonstrates a decorator that might be used to > aid this process. Any comments, additions, deletions?
Interesting idea. I have been prepending 'f' to my test functions that don't yet work, so they simply don't run at all. Then when I have time to add new functionality, I grep for 'ftest' in the test suite. - Eric -- http://mail.python.org/mailman/listinfo/python-list