Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
27ef61ca
Commit
27ef61ca
authored
Mar 25, 2007
by
Brett Cannon
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Change the docs to no longer claim that unittest is preferred over doctest for
regression tests.
parent
3d52e5f0
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
7 deletions
+7
-7
Doc/lib/libtest.tex
Doc/lib/libtest.tex
+7
-7
No files found.
Doc/lib/libtest.tex
View file @
27ef61ca
...
@@ -14,11 +14,11 @@ your tests while \module{test.regrtest} drives the testing suite.
...
@@ -14,11 +14,11 @@ your tests while \module{test.regrtest} drives the testing suite.
Each module in the
\module
{
test
}
package whose name starts with
Each module in the
\module
{
test
}
package whose name starts with
\samp
{
test
_}
is a testing suite for a specific module or feature.
\samp
{
test
_}
is a testing suite for a specific module or feature.
All new tests should be written using the
\refmodule
{
unittest
}
module;
All new tests should be written using the
\refmodule
{
unittest
}
or
using
\refmodule
{
unittest
}
is not required but makes the tests mo
re
\refmodule
{
doctest
}
module. Some older tests a
re
flexible and maintenance of the tests easier. Some older tests are
written using a ``traditional'' testing style that compares output
written to use
\refmodule
{
doctest
}
and a ``traditional'' testing
printed to
\code
{
sys.stdout
}
; this style of test is considered
style; these styles of tests will not be cover
ed.
deprecat
ed.
\begin{seealso}
\begin{seealso}
\seemodule
{
unittest
}{
Writing PyUnit regression tests.
}
\seemodule
{
unittest
}{
Writing PyUnit regression tests.
}
...
@@ -29,8 +29,8 @@ style; these styles of tests will not be covered.
...
@@ -29,8 +29,8 @@ style; these styles of tests will not be covered.
\subsection
{
Writing Unit Tests for the
\module
{
test
}
package
%
\subsection
{
Writing Unit Tests for the
\module
{
test
}
package
%
\label
{
writing-tests
}}
\label
{
writing-tests
}}
It is preferred that tests
for the
\module
{
test
}
package use th
e
It is preferred that tests
that use the
\refmodule
{
unittest
}
modul
e
\refmodule
{
unittest
}
module and
follow a few guidelines.
follow a few guidelines.
One is to name the test module by starting it with
\samp
{
test
_}
and end it with
One is to name the test module by starting it with
\samp
{
test
_}
and end it with
the name of the module being tested.
the name of the module being tested.
The test methods in the test module should start with
\samp
{
test
_}
and end with
The test methods in the test module should start with
\samp
{
test
_}
and end with
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment