Changes between Version 73 and Version 74 of DeveloperGuidelinesTesting


Ignore:
Timestamp:
01/24/09 16:21:08 (13 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DeveloperGuidelinesTesting

    v73 v74  
    55This page defines what our current approach versus our [wiki:BluePrintTesting BluePrint for future options]
    66
    7 Test-Driven Development is a programming styles which says that you 1st write your test cases (from the [BluePrints specs]) & then proceed to make them pass.[[BR]]
    8 Behaviour-Driven Development takes this further to focus on the Specification rather than the Verification using something like [http://www.codeplex.com/pyspec pyspec] or [http://pypi.python.org/pypi/PyFIT/0.8a2 PyFIT]to provide testable specs:
    9  * http://behaviour-driven.org/BDDProcess
    10  * http://fitnesse.org/FitNesse.AcceptanceTests
     7Test-Driven Development is a programming styles which says that you 1st write your test cases (from the [BluePrints specs]) & then proceed to make them pass.
    118
    129[wiki:InstallationGuidelinesDeveloper#TestingSetup]
     
    4744print "test_%i@xxxxxxxx" % random.randint(1, 10000)
    4845}}}
     46!ToDo: Investigate how we can test multiple browsers.
    4947
    50 [http://cherrypy.org CherryPy]'s [http://cherrypy.org/browser/trunk/cherrypy/test/webtest.py WebTest] is good for in-process testing.[[BR]]
     48[http://cherrypy.org CherryPy]'s [http://cherrypy.org/browser/trunk/cherrypy/test/webtest.py WebTest] is good for in-process testing & can be run from a browser-less server(easier for CI-integration).[[BR]]
    5149These tests are stored in {{{/tests/webtest}}}.[[BR]]
    5250NB These are a work-in-progress...need to enable access to Web2Py environment (db, etc) using:
     
    8482== Continuous Integration ==
    8583We are starting to use the Trac-integrated [http://bitten.edgewall.org Bitten] to monitor code quality.
     84
     85!ToDo: Write a step to parse/store the results of Selenium's {{{HandleResults.py}}}
    8686{{{
    8787<step id="lint" description="Run PyLint">
     
    9494ToDo: Fix Windowss:
    9595{{{Error opening pylint results file ([Errno 2] No such file or directory: 'c:\\docume~1\\username\\locals~1\\temp\\bittenxx1j1x\\build_Trunk_3\\pylint-report.txt')}}}
     96We need to write a {{{build/test-results.xml}}} for this one:
    9697{{{
    9798<step id="test" description="Run unit tests">