summaryrefslogtreecommitdiffstats
path: root/Lib/test/test_support.py
Commit message (Collapse)AuthorAgeFilesLines
...
* Fix test_unicode_file errors on platforms without Unicode file support,Mark Hammond2003-12-031-15/+21
| | | | | by setting TESTFN_UNICODE_UNENCODEABLE on these platforms. test_unicode_file only attempts to use the name for testing if not None.
* Add TESTFN_UNICODE_UNENCODEABLE, a unicode filename that can not beMark Hammond2003-12-031-0/+21
| | | | encoded using the default file system encoding.
* Extend last change to cover TestSuites as well as TestCases.Raymond Hettinger2003-07-161-1/+1
|
* run_unittest() to support TestCase instances as well as classes. Helps with ↵Raymond Hettinger2003-07-161-1/+4
| | | | doctests.
* Include module name in doctest summary.Raymond Hettinger2003-05-171-1/+1
|
* Provide a clue that the doctests have run.Raymond Hettinger2003-05-171-1/+3
|
* Patch #734231: Update RiscOS support. In particular, correctMartin v. Löwis2003-05-101-5/+5
| | | | riscospath.extsep, and use os.extsep throughout.
* 'forget' now also deletes any proper .pyo files.Brett Cannon2003-05-041-1/+19
| | | | Added some docstrings.
* Combine the functionality of test_support.run_unittest()Walter Dörwald2003-05-011-7/+8
| | | | | | | | | | and test_support.run_classtests() into run_unittest() and use it wherever possible. Also don't use "from test.test_support import ...", but "from test import test_support" in a few spots. From SF patch #662807.
* Factor out common boilerplate for test_supportRaymond Hettinger2003-04-271-0/+6
|
* if the test is run directly (__name__ == "__main__") don't actually requireSkip Montanaro2003-04-241-0/+4
| | | | particular resources
* Always initialize Py_FileSystemDefaultEncoding on Unix in Py_Initialize,Martin v. Löwis2003-03-051-2/+1
| | | | | and not as a side effect of setlocale. Expose it as sys.getfilesystemencoding. Adjust test case.
* test_support.requires(): Instead of raising TestSkipped, raise a newFred Drake2003-02-031-1/+9
| | | | | | | | | exception, ResourceDenied. This is used to distinguish between tests that are skipped for other reasons (platform support, missing data, etc.) from those that are skipped because a "resource" has not been enabled. This prevents those tests from being reported as unexpected skips for the platform; those should only be considered unexpected skips if the resource were enabled.
* Rearrange test_socket_ssl so that a skip is expected iff the networkTim Peters2002-12-041-1/+4
| | | | resource isn't enabled or the socket module doesn't support ssl.
* Don't try to convert the test filename to Unicode with -U.Martin v. Löwis2002-11-091-1/+6
|
* Whitespace normalization.Tim Peters2002-11-091-1/+1
|
* Fix SF # 631066, running regrtest in user mode failsNeal Norwitz2002-11-031-1/+21
| | | | | | Try to write to TESTFN, if that fails, try TESTFN in /tmp If that fails, print a warning and go on. Will backport.
* Patch #631972: Adds an is_jython flag.Finn Bock2002-11-011-0/+2
|
* Complete the absolute import patch for the test suite. All relativeBarry Warsaw2002-07-301-0/+3
| | | | | | | | imports of test modules now import from the test package. Other related oddities are also fixed (like DeprecationWarning filters that weren't specifying the full import part, etc.). Also did a general code cleanup to remove all "from test.test_support import *"'s. Other from...import *'s weren't changed.
* test_support: add a docstring to vereq().Tim Peters2001-12-291-0/+10
| | | | test_complex: repair new test's usage of vereq().
* Fix bad bug in structseq slicing (NULL pointers in result). Reported byTim Peters2001-10-301-0/+4
| | | | | | Jack Jansen on python-dev. Add simple test case. Move vereq() from test_descr to test_support (it's handy!).
* run_suite(): If testclass is not available, provide an even more generalFred Drake2001-10-041-4/+8
| | | | | | | error message. run_unittest(): Provide the testclass to run_suite() so it can construct the error message. This closes SF bug #467763.
* SF bug [#467336] doctest failures w/ new-style classes.Tim Peters2001-10-031-1/+2
| | | | | | | | | | Taught doctest about static methods, class methods, and property docstrings in new-style classes. As for inspect.py/pydoc.py before it, the new stuff needed didn't really fit into the old architecture (but was less of a strain to force-fit here). New-style class docstrings still aren't found, but that's the subject of a different bug and I want to fix that right instead of hacking around it in doctest.
* Guido points out that sys.__stdout__ is a bit bucket under IDLE. So keepTim Peters2001-09-251-1/+12
| | | | | | | the local save/modify/restore of sys.stdout, but add machinery so that regrtest can tell test_support the value of sys.stdout at the time regrtest.main() started, and test_support can pass that out later to anyone who needs a "visible" stdout.
* Get rid of the increasingly convoluted global tricks w/ sys.stdout, inTim Peters2001-09-251-26/+10
| | | | favor of local save/modify/restore. The test suite should run fine again.
* Set sys.save_stdout (to sys.stdout), so doctest-using tests can be runGuido van Rossum2001-09-251-0/+2
| | | | standalone.
* Oops. I didn't expect that some tests (test_cookie) have expectedGuido van Rossum2001-09-211-0/+1
| | | | | output *and* doctest stuff. Assuming the doctest stuff comes after the expected output, this fixes that.
* Change the way unexpected output is reported: rather than stopping atGuido van Rossum2001-09-211-16/+12
| | | | | | | | | | the first difference, let the test run till completion, then gather all the output and compare it to the expected output using difflib. XXX Still to do: produce diff output that only shows the sections that differ; currently it produces ndiff-style output because that's the easiest to produce with difflib, but this becomes a liability when the output is voluminous and there are only a few differences.
* run_suite(): Oops, update a docstring.Barry Warsaw2001-09-201-1/+1
|
* run_suite(): Factor this out of run_unittest() for tests that buildBarry Warsaw2001-09-201-2/+7
| | | | | | | | their own test suite from a multitude of classes (like test_email.py will be doing). run_unittest(): Call run_suite() after making a suite from the testclass.
* Repair late-night doc typos.Tim Peters2001-09-101-2/+2
|
* Teach regrtest how to pass on doctest failure msgs. This is done via aTim Peters2001-09-091-1/+46
| | | | | | | | | | | 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).
* It appears that unittest was changed to stop hoarding raw exception data,Tim Peters2001-09-081-4/+1
| | | | | | | | | saving instead a traceback string, but test_support's run_unittest was still peeking into unittest internals and trying to pick apart unittest's errors and failures vectors as if they contained exc_info() tuples instead of strings. Whatever, when a unittest-based test failed, test_support blew up. I'm not sure this is the right way to fix it; it simply gets me unstuck.
* Two small changes to the resource usage option:Guido van Rossum2001-09-061-2/+2
| | | | | | | | (1) Allow multiple -u options to extend each other (and the initial value of use_resources passed into regrtest.main()). (2) When a test is run stand-alone (not via regrtest.py), needed resources are always granted.
* use_large_resources => use_resourcesBarry Warsaw2001-08-201-2/+8
| | | | | | | | requires(): New function which can be used to `assert' that a specific -u/--use resource flag is present. Raises a TestSkipped if not. This is used in test_largefile and test_socket_ssl to enable external or resource consumptive tests that are normally disabled.
* Patch #445762: Support --disable-unicodeMartin v. Löwis2001-08-171-3/+10
| | | | | | | | - Do not compile unicodeobject, unicodectype, and unicodedata if Unicode is disabled - check for Py_USING_UNICODE in all places that use Unicode functions - disables unicode literals, and the builtin functions - add the types.StringTypes list - remove Unicode literals from most tests.
* Give more useful information about a failing PyUnit-style test.Fred Drake2001-07-161-2/+11
|
* Add support for Windows using "mbcs" as the default Unicode encoding when ↵Mark Hammond2001-05-131-0/+4
| | | | dealing with the file system. As discussed on python-dev and in patch 410465.
* Get rid of the superstitious "~" in dict hashing's "i = (~hash) & mask".Tim Peters2001-05-131-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The comment following used to say: /* We use ~hash instead of hash, as degenerate hash functions, such as for ints <sigh>, can have lots of leading zeros. It's not really a performance risk, but better safe than sorry. 12-Dec-00 tim: so ~hash produces lots of leading ones instead -- what's the gain? */ That is, there was never a good reason for doing it. And to the contrary, as explained on Python-Dev last December, it tended to make the *sum* (i + incr) & mask (which is the first table index examined in case of collison) the same "too often" across distinct hashes. Changing to the simpler "i = hash & mask" reduced the number of string-dict collisions (== # number of times we go around the lookup for-loop) from about 6 million to 5 million during a full run of the test suite (these are approximate because the test suite does some random stuff from run to run). The number of collisions in non-string dicts also decreased, but not as dramatically. Note that this may, for a given dict, change the order (wrt previous releases) of entries exposed by .keys(), .values() and .items(). A number of std tests suffered bogus failures as a result. For dicts keyed by small ints, or (less so) by characters, the order is much more likely to be in increasing order of key now; e.g., >>> d = {} >>> for i in range(10): ... d[i] = i ... >>> d {0: 0, 1: 1, 2: 2, 3: 3, 4: 4, 5: 5, 6: 6, 7: 7, 8: 8, 9: 9} >>> Unfortunately. people may latch on to that in small examples and draw a bogus conclusion. test_support.py Moved test_extcall's sortdict() into test_support, made it stronger, and imported sortdict into other std tests that needed it. test_unicode.py Excluced cp875 from the "roundtrip over range(128)" test, because cp875 doesn't have a well-defined inverse for unicode("?", "cp875"). See Python-Dev for excruciating details. Cookie.py Chaged various output functions to sort dicts before building strings from them. test_extcall Fiddled the expected-result file. This remains sensitive to native dict ordering, because, e.g., if there are multiple errors in a keyword-arg dict (and test_extcall sets up many cases like that), the specific error Python complains about first depends on native dict ordering.
* In Jython, `@' is not allowed in module names. Extend the TESTFN testBarry Warsaw2001-03-231-3/+7
| | | | to use "$test" when in Jython. Closes SF patch #403668.
* When the regression test is run in verbose mode, make the PyUNIT-basedFred Drake2001-03-231-1/+1
| | | | tests a little noisier, providing more progress information.
* Updated to latest PyUnit version (1.31 in PyUnit CVS); test_support.pySteve Purcell2001-03-221-10/+6
| | | | changed accordingly.
* Just import sys at the top instead of inside lots of functions.Fred Drake2001-03-211-3/+35
| | | | Add some helpers for supporting PyUNIT-based unit testing.
* Oops. A RISCOS patch I forgot to check in.Guido van Rossum2001-03-131-1/+7
|
* Whitespace normalization.Tim Peters2001-02-211-1/+0
|
* Add test for syntax error on "x = 1 + 1".Jeremy Hylton2001-02-191-0/+9
| | | | Move check_syntax() function into test_support.
* docstring typoSkip Montanaro2001-01-201-1/+1
|
* Change verify() function to raise TestFailed, not AssertionError.Guido van Rossum2001-01-191-2/+2
| | | | | | (I realize that I didn't really test this, because all the tests succeed, so verify() never raised an AssertionError -- but the test suite still succeeds, so I'm not too worried.)
* Use constructor form of "raise"; normalize <wink> docstrings.Tim Peters2001-01-191-9/+5
|
* Whitespace normalization. Leaving tokenize_tests.py alone for now.Tim Peters2001-01-181-10/+10
|
generated by cgit v0.12 at 2025-04-11 21:39:33 (GMT)