aboutsummaryrefslogtreecommitdiffstats
path: root/docs/test_suite.txt
diff options
context:
space:
mode:
authorWaylan Limberg <waylan@gmail.com>2012-08-09 06:34:36 -0400
committerWaylan Limberg <waylan@gmail.com>2012-08-09 06:34:36 -0400
commit2789026a0114dba2e8d60be71b4d7c8cc6eb61ed (patch)
tree74ee5e97d8bb39615ba00bc53aeebb91d05a76a8 /docs/test_suite.txt
parent2fe5b5b5803c138f70e5c90aaa77f85f3c596f1d (diff)
parent78fdbeb5ada03f869972be136a7300ba845bb638 (diff)
downloadmarkdown-2789026a0114dba2e8d60be71b4d7c8cc6eb61ed.tar.gz
markdown-2789026a0114dba2e8d60be71b4d7c8cc6eb61ed.tar.bz2
markdown-2789026a0114dba2e8d60be71b4d7c8cc6eb61ed.zip
Merge branch 'master' of https://github.com/waylan/Python-Markdown
Diffstat (limited to 'docs/test_suite.txt')
-rw-r--r--docs/test_suite.txt17
1 files changed, 6 insertions, 11 deletions
diff --git a/docs/test_suite.txt b/docs/test_suite.txt
index eb0c4a7..44b6c5c 100644
--- a/docs/test_suite.txt
+++ b/docs/test_suite.txt
@@ -23,8 +23,8 @@ Additionally, a nicely formatted HTML report of all output is written to a
temporary file in `tmp/test-output.html`. Open the file in a browser to view
the report.
-The test suite contains three kinds of tests: Markdown Syntax Tests, Unit
-Tests, and Doc Tests.
+The test suite contains two kinds of tests: Markdown Syntax Tests and Unit
+Tests.
# Markdown Syntax Tests
@@ -118,16 +118,11 @@ are not explicitly set.
## Unit Tests
+Unit Tests are used as regression tests for Python-Markdown's API.
All Unit Tests shipped with Python-Markdown are standard Python Unit Tests and
-are currently all contained in `tests/test_apis.py`. Standard discovery methods
-are used to find and run the tests. Therefor, when writing new tests, those
-standards and naming conventions should be followed.
-
-## Doc Tests
-
-Some Python-Markdown extensions also include standard Python doctests, which
-are discovered and run in the standard manner; one Unit Test for each file.
-
+are all contained in `tests/test_apis.py` and `tests/test_extensions`.
+Standard discovery methods are used to find and run the tests. Therefore, when
+writing new tests, those standards and naming conventions should be followed.
[Nose]: http://somethingaboutorange.com/mrl/projects/nose/
[Perl]: http://daringfireball.net/projects/markdown/