Changes between Version 51 and Version 52 of DeveloperGuidelinesTesting

Timestamp:

01/16/09 19:07:50 (16 years ago)

Author:

Fran Boon

Comment:

+dutest

DeveloperGuidelinesTesting

@@ -22 +22 @@
   * http://agiletesting.blogspot.com/2005/01/python-unit-testing-part-2-doctest.html
   * Web2Py supports running doctests on Controllers from the admin UI, e.g.: http://127.0.0.1:8000/admin/default/test/sahana/default.py
+  * [http://pypi.python.org/pypi/dutest dutest] - !DocTest !UnitTest integration (includes HTML-aware output checkers such as lxml.doctestcompare.LHTMLOutputChecker)
+   * http://ojs.pythonpapers.org/index.php/tpp/article/viewArticle/56
 
  * [http://docs.python.org/library/unittest.html UnitTest] (formerly [http://pyunit.sourceforge.net PyUnit])
@@ -53 +55 @@
 Testing that Testers should be doing as part of Acceptance:
 == Boundary Testing (should do) ==
-Checks functionality of modules against [BluePrints specs]: Building the Right Code
+Building the Right Code
+
+Checks functionality of modules against [BluePrints specs]
 
 This sees the application as a black box & so the same tests could be run here against both the Python & PHP versions, for instance.