Version 19 (modified by 16 years ago) ( diff ) | ,
---|
Testing
"A bug is a test case you haven't written yet"
"Unit Tests allow merciless refactoring": http://diveintopython.org/refactoring/refactoring.html
Testing that Developers should be doing:
Unit Tests (must do)
These should be written by the developers
- Doc Tests
- UnitTest (formerly PyUnit)
- http://docs.python.org/library/unittest.html
- http://agiletesting.blogspot.com/2005/01/python-unit-testing-part-1-unittest.html
- Nose - a discovery-based unittest extension
- Py.Test
- 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
- Patch Queue Manager - integrates with Bzr
- http://cruisecontrol.sourceforge.net/
Regression Testing
Fired by dev after certain number of changes or whenever they like.
Documentation
As well as writing DocStrings in all functions, we can generate an overall API using:
Testing that Testers should be doing:
Boundary Testing (should do)
Checks functionality of modules against spec.
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:
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:
Stress Tests
Security Tests
Whilst the Web2Py framework is secure by design, we should validate this:
Attachments (4)
- Regression tests.pdf (482.2 KB ) - added by 14 years ago.
-
Regression tests.odt
(349.2 KB
) - added by 14 years ago.
Source for the PDF
-
test.cmd
(1.9 KB
) - added by 14 years ago.
Non-Interactive
-
testui.cmd
(1.9 KB
) - added by 14 years ago.
Interactive Wrapper for Selenium
Download all attachments as: .zip