summaryrefslogtreecommitdiffstats
path: root/Doc/lib/libunittest.tex
Commit message (Collapse)AuthorAgeFilesLines
* SF Patch #1093896: miscellaneous doc typosRaymond Hettinger2005-01-011-1/+1
|
* Clarify that it's not necessary to subclass from TestCase to create aJohannes Gijsbers2004-11-071-1/+2
| | | | | test case. As Jeremy put it: "subclassing is an implementation technique, not a type declaration".
* - add a "See also" reference to the doctest moduleFred Drake2003-12-311-24/+25
| | | | | - slightly simplify a couple of examples - clean up some markup
* SF bug #855317: unittest: 5.3.9 Getting Extended Error InformationRaymond Hettinger2003-12-071-42/+0
| | | | | | | The example code did not work and could not easily be made to work. Since the docs were already complex and the feature was not used (it took two years for the errors to surface), we decided to dedocument it entirely, leaving unittest cleaner than before.
* Patch #808362: Fix typos.Martin v. Löwis2003-09-201-1/+1
|
* * Minor wording changeRaymond Hettinger2003-09-161-2/+8
| | | | * Reference the doctest.DocTestSuite() conversion tool.
* SF #767592: unittest docs don't suggest "unittest.main()"Raymond Hettinger2003-07-101-0/+96
| | | | | Expanded docs to have a quick start example showing how to create and run tests.
* Remove erroneous period.Michael W. Hudson2003-02-101-1/+1
|
* Incorporate Skip's suggestion to use SciPy's validation test nearRaymond Hettinger2002-12-291-0/+24
| | | | | | equality. Note, there is another flavor that compares to a given number of significant digits rather than decimal places. If there is a demand, that could be added at a later date.
* typo fix.Just van Rossum2002-12-151-1/+1
|
* Document when unittest was added to Python.Fred Drake2002-10-101-0/+1
|
* Add annotations that describe the change in the "errors" and "failures"Fred Drake2002-07-021-0/+4
| | | | attributes of the TestResult.
* Update the documentation of the errors and failures attributes of theFred Drake2002-07-021-6/+48
| | | | | | TestResult object. Add an example of how to get even more information for apps that can use it. Closes SF bug #558278.
* Use the \note and \warning macros where appropriate.Fred Drake2001-10-201-4/+4
|
* Several updates to cover omissions noted by Rich Salz.Fred Drake2001-09-061-3/+27
| | | | This closes SF bug #458771.
* Minor changes to match the style guide.Fred Drake2001-07-141-3/+3
|
* Added module synopsis for the chapter summary.Fred Drake2001-04-121-67/+186
| | | | | | | | | | | | | | | | | Added documentation for TestCase.assertRaises(). Added text for "Mapping concepts to classes", and merged it into the front matter instead of separating it into a new section. Removed use of "assert" in examples. Update the descriptions to reflect further changes from discussions on the pyunit-interest list. Added documentation for the defaultTestLoader object and the TestLoader methods. Added the assert*() names for the TestCase helper methods.
* Added a lot of text from Steve Purcell's HTML documentation.Fred Drake2001-04-121-29/+251
| | | | | | Updated reference material substantially based on discussions on the pyunit-interest mailing list (not all changes are in the code in CVS yet).
* Added definition of "test fixture".Fred Drake2001-04-101-2/+142
| | | | | | | | Added description of optional parameter to the TestSuite constructor. Added descriptions of the TestLoader and TextTestRunner classes. Added method descriptions for the TestCase class.
* Start of documentation for the unittest module. Some of this comes fromFred Drake2001-04-071-0/+266
Steve Purcell's documentation, and a lot of it is written based on using PyUnit and reading the implementation. There is more to come, but I want to get this check in before I have a disk crash or anything else bad happens.