core-jgi/selenese
Elaine Tan db4a4f5afd IDEMPIERE-92 Implement Selenium testing framework. Fix selenium library reference in classpath 2013-10-02 19:38:19 +08:00
..
.settings
resource/selenese IDEMPIERE-92 - Integrate Selenium. Refactor to 3 project, webdriver+jq, selenese and ztl. Refactor the webdriver+jq code to make it easier to write new test cases. Added logout and change role test case to the webdriver+jq project. Use GardenAdmin instead of SuperUser for example test cases. 2012-12-11 01:20:08 +08:00
src/test
.classpath IDEMPIERE-92 Implement Selenium testing framework. Fix selenium library reference in classpath 2013-10-02 19:38:19 +08:00
.project
Readme.txt

Readme.txt

test
- Example test cases exported from Selenium IDE ( JUnit4 + WebDriver )

resource/selenese
- selenese test script recorded by Selenium IDE

Notes
======
* The mapping between selenese ( the native format created from Selenium IDE recording ) and 
  web driver export is not one to one. For e.g, the fireEvent command is not needed in
  web driver test script.

* While both "id=loginPanel_Ok" and "loginPanel_Ok" work the same when you execute selenese test with Selenium IDE, 
you must use the id= syntax for the web driver export to work.

* The selenese script recorded by Selenium IDE required changes ( most of the time, you need to add insert fireEvent and sleep command )
before you can run it with Selenium IDE. However, it mostly work if you export it to the Java WebDriver format and run it from Eclipse.

* AdempiereIDGenerator is required for the recording and execution of selenese test cases.