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

Timestamp:

05/31/12 12:31:30 (13 years ago)

Author:

Fran Boon

Comment:

--

DeveloperGuidelines/Testing/Selenium

@@ -1 +1 @@
 = Testing =
 [[TOC]]
-'''Introducing automated testing system built inside Sahana Eden (S3) framework.'''
+"A bug is a test case you haven't written yet"
 
-"A bug is a test case you haven't written yet" [[BR]]
 "Unit Tests allow merciless [http://diveintopython.org/refactoring/refactoring.html refactoring]"
 
-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.
+This page defines what our current approach versus our [wiki:BluePrintTesting BluePrint for future options]
 
-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
+Test-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.
+
+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 used as Unit Testing
 
 We are building our framework around the new !WebDriver, despite having some legacy code in the older format:
 * http://seleniumhq.org/docs/appendix_migrating_from_rc_to_webdriver.html#why-migrate-to-webdriver
 
+TestCases - List of things to test
 == How does it work? == 
 The system relies on Selenium web driver and IDE to execute and/or create automated test scripts.