| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
Convert test/README to reST
|
|
|
|
|
| |
Expand the example to show some actual test functions, and a setUp()
and tearDown() method.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
imports e.g. test_support must do so using an absolute package name
such as "import test.test_support" or "from test import test_support".
This also updates the README in Lib/test, and gets rid of the
duplicate data dirctory in Lib/test/data (replaced by
Lib/email/test/data).
Now Tim and Jack can have at it. :)
|
|
|
|
|
| |
run_suite() instead of run_unittest(). Best practice is to plan for
multiple test classes.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
horridly inefficient hack in regrtest's Compare class, but it's about as
clean as can be: regrtest has to set up the Compare instance before
importing a test module, and by the time the module *is* imported it's too
late to change that decision. The good news is that the more tests we
convert to unittest and doctest, the less the inefficiency here matters.
Even now there are few tests with large expected-output files (the new
cost here is a Python-level call per .write() when there's an expected-
output file).
|
|
|
|
|
| |
tabs. The title was centered using 8-byte tabs, however, and the
result looked strange. Fixed this.
|
|
|
|
|
|
| |
Change test_doctest and test_difflib to pass regrtest's notion of
verbosity on to doctest.
Add explanation for a dozen "new" things to test/README.
|
|
|
|
| |
testing using doctest and PyUnit.
|
|
|
|
| |
and be clear that you need to clean it up when done.
|
|
|
|
|
| |
In README: Write up (Guido's) rules for intra-test imports; warn against
asserts; document test_support.use_large_resources.
|
| |
|
|
|
|
|
| |
to signify a test that should be marked as 'skipped' rather than 'failed'.
Also 'document' it, in README.
|
| |
|
|
|