Changes between Version 20 and Version 21 of DeveloperGuidelines/Testing/Selenium
- Timestamp:
- 05/31/12 14:00:04 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DeveloperGuidelines/Testing/Selenium
v20 v21 30 30 31 31 == Running / Executing Automated test scripts: == 32 In Sahana Eden, the testing system is implemented in the directory: eden/modules/tests/ [[BR]]33 Now that you have installed all the Selenium packages to your Python on your machine, you can now run them to test Eden module(s) functionalities. [[BR]][[BR]]34 35 32 Before running the Selenium scripts, you should put your database into a known state: 36 33 {{{ … … 55 52 }}} 56 53 57 == Writing / Creating your own test scripts: ==54 == Writing / Creating your own test scripts: == 58 55 We aim to make it as easy as possible to write additional tests, which can easily be plugged into the testing suite or/and executed separately. 59 56 60 An example has been created: {{{eden/modules/tests/hrm/hrm001.py}}}57 The canonical example is: {{{eden/modules/tests/org/org_create_organisation.py}}} 61 58 62 59 New tests should be stored in a subfolder per module, adding the foldername to {{{eden/modules/tests/__init__.py}}} & creating an {{{__init__.py}}} in the subfolder. … … 73 70 * http://selenium.googlecode.com/svn/trunk/docs/api/py/selenium/selenium.selenium.html 74 71 72 We separate data out into a separate file, so that this is easy to change to allow reruns of the tsts with different data sets. 75 73 == !ToDo == 76 74 * Store results in a format suitable for use by CI
