Changes between Version 18 and Version 19 of DeveloperGuidelinesTesting


Ignore:
Timestamp:
01/11/09 19:32:52 (13 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DeveloperGuidelinesTesting

    v18 v19  
    77 * http://diveintopython.org/unit_testing/index.html
    88 * http://vallista.idyll.org/~grig/articles/
    9 
     9----
     10Testing that Developers should be doing:
    1011== Unit Tests (must do) ==
    1112These should be written by the developers
    1213 * Doc Tests
    1314  * http://agiletesting.blogspot.com/2005/01/python-unit-testing-part-2-doctest.html
    14  * !UnitTest
     15 * !UnitTest (formerly [http://pyunit.sourceforge.net PyUnit])
    1516  * http://docs.python.org/library/unittest.html
    1617  * http://agiletesting.blogspot.com/2005/01/python-unit-testing-part-1-unittest.html
    17   * Formerly !PyUnit: http://pyunit.sourceforge.net/
     18  * [http://somethingaboutorange.com/mrl/projects/nose/ Nose] - a discovery-based unittest extension
    1819 * Py.Test
    1920  * http://agiletesting.blogspot.com/2005/01/python-unit-testing-part-3-pytest-tool.html
     
    2829== Regression Testing ==
    2930Fired by dev after certain number of changes or whenever they like.
     31 * http://docs.python.org/library/test.html
     32 * http://www.pycheesecake.org/
     33  * Case Study: http://pycheesecake.org/wiki/CleaningUpPyBlosxom
    3034
    31  * http://docs.python.org/library/test.html
    32 
     35== Documentation ==
     36As well as writing !DocStrings in all functions, we can generate an overall API using:
     37 * http://epydoc.sourceforge.net/
     38----
     39Testing that Testers should be doing:
    3340== Boundary Testing (should do) ==
    3441Checks functionality of modules against spec.[[BR]]