Module SeleniumPoetry
In: lib/selenium_poetry.rb

This module extends SeleniumOnRails::TestBuilder. It enables you to write more readable Selenium tests.

To use the methods of Selenium Poetry in your tests, you‘ll first need to load selectors. Do that with the method load_selectors.

Selector files must be place in your Rails application under the directory test/selectors. They should be YAML files.

Methods

click_on   click_on_and_wait   load_selectors   should_be   should_drag_and_drop   should_equal   should_have   should_have_text   should_not_be   should_not_have   should_store   should_wait_for   should_wait_for_absence_of   should_wait_for_equal   type_on  

Constants

SELECTORS_DIR = File.dirname(__FILE__) + "/../../../../test/selectors"

Public Instance methods

click_on(*selector_keys)

Is equivalent to Selenium‘s click.

click_on_and_wait(*selector_keys)

Is equivalent to Selenium‘s click_and_wait.

load_selectors(*filenames)

Use it load the selectors you‘ll need to use in your Selenium test. Example: 

 load_selectors :index

This will load selectors from the file test/selectors/index.yml. If you have to load selectors from several files, you do like this: 

  load_selectors :index, :checkout, :finish

It will load selectors from the files:

  • test/selectors/index.yml
  • test/selectors/checkout.yml
  • test/selectors/finish.yml

Place load_selectors in the beginning of your tests.

should_be(*selector_keys)

Is equivalent to Selenium‘s assert_eval somethind, true.

should_drag_and_drop(key_of_origin, key_of_target)

Is equivalent to Selenium‘s drag_and_drop_to_object.

should_equal(selector_keys_and_expected_values)

Is equivalent to Selenium‘s assert_eval.

should_have(*selector_keys)

Is equivalent to Selenium‘s assert_element_present.

Suppose you have the selector file test/selectors/index.yml with this content: 

  postcard of rio de janeiro:
      //ul/li/img[@src="images/riodejaneiro.jpg" and @alt="Rio de Janeiro" and @title="Rio de Janeiro"]
  postcard of recife:
      //ul/li/img[@src="images/recife.jpg" and @alt="Recife" and @title="Recife"]

Using should_have: 

  should_have "postcard of rio de janeiro"

This is equivalent to the regular Selenium command: 

  assert_element_present '//ul/li/img[@src="images/riodejaneiro.jpg" and @alt="Rio de Janeiro" and @title="Rio de Janeiro"]'

If you need to test more than one selector, use this syntax: 

  should_have "postcard of rio de janeiro",
              "postcard of recife"

This will produce the equivalent Selenium commands: 

  assert_element_present '//ul/li/img[@src="images/riodejaneiro.jpg" and @alt="Rio de Janeiro" and @title="Rio de Janeiro"]'
  assert_element_present '//ul/li/img[@src="images/recife.jpg" and @alt="Recife" and @title="Recife"]'
should_have_text(key, text)

Is equivalent to Selenium‘s assert_text.

should_not_be(*selector_keys)

Is equivalent to Selenium‘s assert_eval somethind, false.

should_not_have(*selector_keys)

Is equivalent to Selenium‘s assert_element_not_present.

Take a look at should_have for further explanation.

should_store(script_variable)

Is equivalent to Selenium‘s store_eval.

should_wait_for(*selector_keys)

Is equivalent to Selenium‘s wait_for_element_present.

Take a look at should_have for further explanation. It‘s the same thing, but uses wait_for_element_present instead of assert_element_present.

should_wait_for_absence_of(*selector_keys)

Is equivalent to Selenium‘s wait_for_element_not_present.

Take a look at should_not_have for further explanation. It‘s the same thing, but uses wait_for_element_not_present instead of assert_element_present.

should_wait_for_equal(script_expected)

Is equivalent to Selenium‘s wait_for_eval.

type_on(selector_keys_and_expected_values)

Is equivalent to Selenium‘s type.

[Validate]