Changes between Version 51 and Version 52 of DeveloperGuidelinesTesting


Ignore:
Timestamp:
01/16/09 19:07:50 (13 years ago)
Author:
Fran Boon
Comment:

+dutest

Legend:

Unmodified
Added
Removed
Modified
  • DeveloperGuidelinesTesting

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