Changes between Version 53 and Version 54 of DeveloperGuidelines/Testing/Selenium


Ignore:
Timestamp:
01/04/13 03:46:13 (12 years ago)
Author:
Michael Howden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • DeveloperGuidelines/Testing/Selenium

    v53 v54  
    1 = Testing =
     1= Automated Tests - Selenium =
    22[[TOC]]
    3 ''"A bug is a test case you haven't written yet"''
    43
    5 ''"Unit Tests allow merciless [http://diveintopython.org/refactoring/refactoring.html refactoring]"''
    6 
    7 This page defines what our current approach versus our [wiki:BluePrintTesting BluePrint for future options]
    8 
    9 Test-Driven Development is a programming style which says that you 1st write your test cases (from the [BluePrint specs]) & then proceed to make them pass.
    10 
    11 == Introduction ==
    124Selenium provides the ability to test Sahana Eden as users see it - namely through a web browser. This therefore does end-to-end Functional Testing, however it can also be used as Unit Testing
    135
    … …  
    189181
    190182== See Also ==
    191  * [SysAdmin/ContinuousIntegration CI Server] - How we have set up the CI Server - may help you find the exact commands to run the tests.
    192  * TestCases - List of things to test
    193183 * http://code.google.com/p/selenium/wiki/PageObjects - Style suggestion
    194 
    195 Systers' approach:
    196  * http://systers.org/systers-dev/doku.php/automated_functional_testing
    197  * List of Tests: http://systers.org/systers-dev/doku.php/master_checklist_template
    198  * GSoC project: http://systers.org/systers-dev/doku.php/svaksha:patches_release_testing_automation
    199 
    200 Alternative Options:
    201  * http://zesty.ca/scrape/
    202   * [http://pycon.blip.tv/file/3261277 Lightning Talk] (2.30)
    203   * [http://pycon.blip.tv/file/3261277 Lightning Talk] (2.30)
    204   * [http://pycon.blip.tv/file/3261277 Lightning Talk] (2.30)