Changes between Version 17 and Version 18 of DeveloperGuidelinesTesting


Ignore:
Timestamp:
01/11/09 18:55:06 (16 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TabularUnified DeveloperGuidelinesTesting

    v17 v18  
    3232
    3333== Boundary Testing (should do) ==
    34 Checks functionality of modules against spec.
    35  * Functional tests can be written using [http://seleniumhq.org Selenium] or [http://jakarta.apache.org/jmeter/ JMeter]
     34Checks functionality of modules against spec.[[BR]]
     35This sees the application as a black box & so the same tests could be run here against both the Python & PHP versions, for instance.
     36
     37Functional tests can be written using:
     38 * [http://seleniumhq.org Selenium]
     39 * [http://jakarta.apache.org/jmeter/ JMeter]
    3640This is done by the Testers who accept the Code as a result.
    3741
    … …  
    4751 * http://groups.google.com/group/web2py/browse_thread/thread/cf5c5bd53bc42d49
    4852
     53== Stress Tests ==
     54 * http://tsung.erlang-projects.org/
     55 * Siege
     56
    4957== Security Tests ==
    5058Whilst the Web2Py framework is secure by design, we should validate this: