New submission from Justin Mazzola Paluska <[EMAIL PROTECTED]>: The attached patch (unittest-disable.patch) allows methods in unittest.TestCases to be "disabled". The patch is against Python2.5 from Debian:
%python2.5 Python 2.5.2 (r252:60911, Apr 17 2008, 13:15:05) [GCC 4.2.3 (Debian 4.2.3-3)] on linux2 Disabled tests are not run, but are "remembered" in the output of the test program. For example, the attached sample_tests.py has two tests, one of which has been disabled. The output is: %python sample_tests.py .D ---------------------------------------------------------------------- Ran 2 tests in 0.000s OK where the D indicates that a test has been disabled. Disabling tests is useful if you're using a "test first" coding workflow, as some tests may test functionality that hasn't been implemented yet. The failures of these tests (with their noisy tracebacks) makes it harder to concentrate on other, real failures that may be occurring in your tests. ---------- components: Library (Lib) files: unittest-disable.patch keywords: patch messages: 68752 nosy: jmp severity: normal status: open title: Wish: disable tests in unittest versions: Python 2.5 Added file: http://bugs.python.org/file10735/unittest-disable.patch _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3202> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
