DeveloperGuidelines

= Testing =
"A bug is a test case you haven't written yet" [[BR]]
"Unit Tests allow merciless refactoring": http://diveintopython.org/refactoring/refactoring.html

 * http://pycheesecake.org/wiki/PythonTestingToolsTaxonomy
 * http://vallista.idyll.org/~grig/articles/
----
Testing that Developers should be doing:
== Unit Tests (must do) ==
 * http://diveintopython.org/unit_testing/index.html
These should be written by the developers
 * Doc Tests
  * http://agiletesting.blogspot.com/2005/01/python-unit-testing-part-2-doctest.html
 * !UnitTest (formerly [http://pyunit.sourceforge.net PyUnit])
  * http://docs.python.org/library/unittest.html
  * http://agiletesting.blogspot.com/2005/01/python-unit-testing-part-1-unittest.html
  * [http://somethingaboutorange.com/mrl/projects/nose/ Nose] - a discovery-based unittest extension
 * Py.Test
  * http://agiletesting.blogspot.com/2005/01/python-unit-testing-part-3-pytest-tool.html

 * Rspec is an equivalent for Ruby: http://rspec.info/

== Continuous Integration ==
Whenever a commit is made it should be checked to see that it doesn't break anything
 * [https://launchpad.net/pqm Patch Queue Manager] - integrates with Bzr
 * http://cruisecontrol.sourceforge.net/

== Regression Testing ==
Fired by dev after certain number of changes or whenever they like.
 * http://docs.python.org/library/test.html
 * http://www.pycheesecake.org/
  * Case Study: http://pycheesecake.org/wiki/CleaningUpPyBlosxom

== Documentation ==
As well as writing !DocStrings in all functions, we can generate an overall API using:
 * http://epydoc.sourceforge.net/
----
Testing that Testers should be doing:
== Boundary Testing (should do) ==
Checks functionality of modules against spec.[[BR]]
This sees the application as a black box & so the same tests could be run here against both the Python & PHP versions, for instance.

Functional tests can be written using:
 * [http://seleniumhq.org Selenium]
 * [http://jakarta.apache.org/jmeter/ JMeter]
This is done by the Testers who accept the Code as a result.

== Integration Testing (good thing) ==

== Usability Tests ==
=== Accessibility ===
 * Are we XHTML 1.0 compliant?
 * Are we usable without !JavaScript?

== Performance Tests ==
Whilst the Web2Py framework is fast, we should check that we're not doing anything stupid to slow it down:
 * http://groups.google.com/group/web2py/browse_thread/thread/cf5c5bd53bc42d49

== Stress Tests ==
 * http://tsung.erlang-projects.org/
 * Siege

== Security Tests ==
Whilst the Web2Py framework is secure by design, we should validate this:
 * http://mdp.cti.depaul.edu/examples/default/features
----
DeveloperGuidelines