WebObjects/Project WONDER/Frameworks/ERSelenium

From Wikibooks, open books for an open world
< WebObjects‎ | Project WONDER
Jump to navigation Jump to search

Really Quick Start[edit | edit source]

You can also use Selenium IDE to create and edit tests:

Overview and Usage Notes[edit | edit source]

ERSelenium provides several features for effective use of SeleniumCore with WebObjects applications including:

  • Custom setup/teardown actions that can be run before/after each test.
  • Base URL independence.
  • Support of HTML and Selenese test formats (Java support is planned).
  • "On-the-fly" generation of test suites from the files in your project's source tree.
  • Bookmarkable DirectAction url to run all tests (can be used for automated testing).
  • Metacommands (special instructions specified in comments).

SeleniumCore is the powerful javascript toolkit for web applications "black-box" testing. It emulates different kinds of user actions such as: clicking the hyperlink, editing text in the input field, choosing item from the list and so on.

Using ERSelenium[edit | edit source]

You can use ERSelenium directly from workspace:

  1. Specify it as your project's workspace dependency .
  2. Enable it in the project's Properties file:

Debug output of ERSelenium can be enabled in Properties by:

log4j.logger.er.selenium = DEBUG

Other ERSelenium properties:

  • SeleniumTestsRoot="SomeOtherPath" - change the tests location. By default ERSelenium will search for tests in "Resources/Selenium".
  • SeleniumActionsClass="FullClassName" - specifies the class with methods, which should be executed before and during the test using SeleniumAction direct action (see below for details). By default SeleniumDefaultSetupActions class is used.
  • SeleniumReportPath="PathName" - specified the path to the report file, which is created after the testing is done. "./Contents/Resources/" is the default value.

In your SeleniumTestsRoot folder (Resources/Selenium by default) you should create tests hierarchy. Tests are divided into groups, each group is located in its own folder. In each folder there should be a collection of test files, each in one of the formats, supported by ERSelenium. Example hierarchy:


You can use both standard HTML and wiki-like Selenese formats for writing tests although Selenese format is usually a preferred choice.

To run all tests point your browser to SeleniumStartTesting Direct Action: http://[baseurl]/wa/SeleniumStartTesting


To run a specific group of tests, add "/TestGroupName":


Some tips for writing tests for ERSelenium[edit | edit source]

  • Don't use full URLs with open/openWindow commands (http://[baseurl] part will be added by ERSelenium):
  • You can use setup/teardown methods from the class, specified in SeleniumActionsClass property by opening /wa/SeleniumAction/methodName URL, e.g.:
  • You can use @repeat-@values-@done metacommands to execute specific part of the test with different values edited in textboxes, e.g.:
  ...some actions...
  @values __selenium_test@ @__sel notcorrect@@
  ...some actions...

The commands between @repeat and @done will be repeated several times, each time with new value in "xpath=id('content')/input" input field.

Note: in Selenese format, lines that don't begin with "|" are treated as comments, so metacommands in the example above will be safely processed by Selenium IDE.

  • Selenium IDE Firefox plugin and XPath Checker can be very handy for creating and editing Selenium tests. Selenium IDE Selenese source plugin with proper comments support resides in ERSelenium/Resources/selenese-ide-plugin.js.