diff options
author | Thomas Wouters <thomas@python.org> | 2000-08-04 13:34:43 +0000 |
---|---|---|
committer | Thomas Wouters <thomas@python.org> | 2000-08-04 13:34:43 +0000 |
commit | ad51f8c6d8bbcd7fbce346c7ed3f1ddc8cce98c5 (patch) | |
tree | 43d957a81c383a019670044772443229a84888aa /Lib/test/README | |
parent | a760beb8d66222b456b160344eb0b4b7fccbf84a (diff) | |
download | cpython-ad51f8c6d8bbcd7fbce346c7ed3f1ddc8cce98c5.tar.gz |
Raise 'TestSkipped' (from the test_support) module rather than 'ImportError'
to signify a test that should be marked as 'skipped' rather than 'failed'.
Also 'document' it, in README.
Diffstat (limited to 'Lib/test/README')
-rw-r--r-- | Lib/test/README | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/Lib/test/README b/Lib/test/README index c969fcc58f..94b1964b0d 100644 --- a/Lib/test/README +++ b/Lib/test/README @@ -12,7 +12,8 @@ functionality. The mechanics of how the test system operates are fairly straightforward. When a test case is run, the output is compared with the expected output that is stored in .../Lib/test/output. If the test runs to completion and the actual and expected outputs match, the test succeeds, if -not, it fails. If an ImportError is raised, the test is not run. +not, it fails. If an ImportError or test_support.TestSkipped error is +raised, the test is not run. You will be writing unit tests (isolated tests of functions and objects defined by the module) using white box techniques. Unlike black box |