Changes between Version 12 and Version 13 of DeveloperGuidelines/Testing/Selenium


Ignore:
Timestamp:
05/31/12 12:31:30 (9 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DeveloperGuidelines/Testing/Selenium

    v12 v13  
    11= Testing =
    22[[TOC]]
    3 '''Introducing automated testing system built inside Sahana Eden (S3) framework.'''
     3"A bug is a test case you haven't written yet"
    44
    5 "A bug is a test case you haven't written yet" [[BR]]
    65"Unit Tests allow merciless [http://diveintopython.org/refactoring/refactoring.html refactoring]"
    76
    8 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.
     7This page defines what our current approach versus our [wiki:BluePrintTesting BluePrint for future options]
    98
    10 Selenium 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 sued as Unit Testing
     9Test-Driven Development is a programming style which says that you 1st write your test cases (from the [BluePrints specs]) & then proceed to make them pass.
     10
     11Selenium 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
    1112
    1213We are building our framework around the new !WebDriver, despite having some legacy code in the older format:
    1314* http://seleniumhq.org/docs/appendix_migrating_from_rc_to_webdriver.html#why-migrate-to-webdriver
    1415
     16TestCases - List of things to test
    1517== How does it work? ==
    1618The system relies on Selenium web driver and IDE to execute and/or create automated test scripts.