Changes between Version 18 and Version 19 of DeveloperGuidelinesTesting
- Timestamp:
- 01/11/09 19:32:52 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DeveloperGuidelinesTesting
v18 v19 7 7 * http://diveintopython.org/unit_testing/index.html 8 8 * http://vallista.idyll.org/~grig/articles/ 9 9 ---- 10 Testing that Developers should be doing: 10 11 == Unit Tests (must do) == 11 12 These should be written by the developers 12 13 * Doc Tests 13 14 * http://agiletesting.blogspot.com/2005/01/python-unit-testing-part-2-doctest.html 14 * !UnitTest 15 * !UnitTest (formerly [http://pyunit.sourceforge.net PyUnit]) 15 16 * http://docs.python.org/library/unittest.html 16 17 * 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 18 19 * Py.Test 19 20 * http://agiletesting.blogspot.com/2005/01/python-unit-testing-part-3-pytest-tool.html … … 28 29 == Regression Testing == 29 30 Fired 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 30 34 31 * http://docs.python.org/library/test.html 32 35 == Documentation == 36 As well as writing !DocStrings in all functions, we can generate an overall API using: 37 * http://epydoc.sourceforge.net/ 38 ---- 39 Testing that Testers should be doing: 33 40 == Boundary Testing (should do) == 34 41 Checks functionality of modules against spec.[[BR]]