#32602: Clarify wording re: parallel testing and test case vs. test case class
-------------------------------------+-------------------------------------
Reporter: Chris Jerdonek | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Testing framework | Version: 3.1
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Chris Jerdonek):
Also, from the "Organizing test code" section:
https://docs.python.org/3/library/unittest.html#organizing-test-code
> The basic building blocks of unit testing are ''test cases'' — single
scenarios that must be set up and checked for correctness. In `unittest`,
test cases are represented by `unittest.TestCase` instances. To make your
own test cases you must write subclasses of TestCase or use
FunctionTestCase.
> ... If the test fails, an exception will be raised with an explanatory
message, and `unittest` will identify the test case as a ''failure''.
--
Ticket URL: <https://code.djangoproject.com/ticket/32602#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.98362f3243d8836b44be1e38eea3f685%40djangoproject.com.
