wiki:DeveloperGuidelinesTesting

Version 13 (modified by Fran Boon, 13 years ago) ( diff )

--

DeveloperGuidelines

Testing

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

Unit Tests (must do)

These should be written by the developers

Continuous Integration

Whenever a commit is made it should be checked to see that it doesn't break anything

Regression Testing

Fired by dev after certain number of changes or whenever they like.

Boundary Testing (should do)

Checks functionality of modules against spec.

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:

Security Tests

Whilst the Web2Py framework is secure by design, we should validate this:


DeveloperGuidelines

Attachments (4)

Download all attachments as: .zip

Note: See TracWiki for help on using the wiki.