Snipplr

(Ruby) Watchr config for use with PHPUnit - noah

Thu, 31 Mar 2011 14:28:22 GMT

A simple [Watchr](https://github.com/mynyml/watchr) config for running PHPUnit tests. This will run a [Pake](https://github.com/indeyets/pake/wiki) task called "test" and ring the system bell if the task fails. *Ringing the system bell* is especially nice when running inside a GNU Screen session. *Installation* To install you need [RubyGems](http://rubyforge.org). Then type: sudo gem install watchr

(Ruby) Howto set up a Rake task to start and stop the Selenium-RC server - noah

Mon, 08 Feb 2010 23:01:08 GMT

(Ruby) Howto set up a Rake task to run Cucumber features and generate reports - noah

Mon, 08 Feb 2010 22:41:45 GMT

Note that Rake is slower than just running `cucumber`

(Ruby) How to call JavaScript in the Application Under Test, from Selenium - noah

Thu, 17 Sep 2009 13:14:43 GMT

When writing functional tests with Selenium, it is often convenient to call JavaScript functions and methods, that are part of the Web application you are testing. After all, Selenium is a functional testing framework for Web UI and most of the exciting bits of Web UI are JS (sorry, all you CSS hackers, but them's the facts). The problem is that it's not immediately obvious how you can access the DOM of the Application Under Test (AUT). Selenium Core (in which all Selenium tests execute) is a frame set, and if you simply try to call your JavaScript with `getEval`, you'll get an error because `getEval` references Selenium Core's DOM, not the DOM of the AUT. Fortunately the answer is simple. Use `this.browserbot.getCurrentWindow()` to get a reference to the `window` object in *your* DOM. Then you can execute any of the JS that lives in your page, right from Selenium! This example uses the Ruby driver, but the principle is the same regardless of which language you use.

(Ruby) Waiting for events with the Selenium-Client Ruby driver - noah

Wed, 01 Jul 2009 10:57:06 GMT

## List of commonly used `wait_for` commands For convenience, here are direct links to the documentation of the Selenium-Ruby `wait_for` commands that are most often used. The [documentation of WaitFor commands in Selenium Core](http://release.seleniumhq.org/selenium-core/1.0.1/reference.html#waitForCondition "WaitForCondition entry in the docs for Selenium Core 1.0.1") may also be of interest. 0. [`wait_for_condition`](http://selenium-client.rubyforge.org/classes/Selenium/Client/Idiomatic.html#M000088) 0. [`wait_for_element`](http://selenium-client.rubyforge.org/classes/Selenium/Client/Extensions.html#M000257) 0. [`wait_for_field_value`](http://selenium-client.rubyforge.org/classes/Selenium/Client/Extensions.html#M000261) 0. [`wait_for_frame_to_load`](http://selenium-client.rubyforge.org/classes/Selenium/Client/GeneratedDriver.html#M000221) 0. [`wait_for_no_element`](http://selenium-client.rubyforge.org/classes/Selenium/Client/Extensions.html#M000258) 0. [`wait_for_no_field_value `](http://selenium-client.rubyforge.org/classes/Selenium/Client/Extensions.html#M000262) 0. [`wait_for_no_text `](http://selenium-client.rubyforge.org/classes/Selenium/Client/Extensions.html#M000260) 0. [`wait_for_page `](http://selenium-client.rubyforge.org/classes/Selenium/Client/Idiomatic.html#M000067) 0. [`wait_for_page_to_load `](http://selenium-client.rubyforge.org/classes/Selenium/Client/Idiomatic.html#M000068) 0. [`wait_for_popup `](http://selenium-client.rubyforge.org/classes/Selenium/Client/Idiomatic.html#M000069) 0. [`wait_for_text `](http://selenium-client.rubyforge.org/classes/Selenium/Client/Extensions.html#M000259) ## Where to find the documentation More information on`wait_for` with the Ruby client, including a complete list of the `wait_for` commands available in the Ruby client, is to be found in the [documentation for the Selenium-Client Ruby Gem.](http://selenium-client.rubyforge.org/ "selenium-client is the official Ruby driver for Selenium RC") As Selenium-Client defines many "idiomatic" Ruby aliases for built-in Selenium methods, it will probably be especially helpful to become familiar with the [Selenium Ruby driver command set](http://selenium-client.rubyforge.org/classes/Selenium/Client/GeneratedDriver.html) as well as Selenium-Client's [Idiomatic Ruby command set.](http://selenium-client.rubyforge.org/classes/Selenium/Client/Idiomatic.html) It may also be helpful to refer to the [documentation for Selenium Core](http://release.seleniumhq.org/selenium-core/1.0.1/reference.html#waitForCondition "WaitForCondition entry in the docs for Selenium Core 1.0.1") with regard to `WaitForCondition` and related commands. In general the **Selenium Core documentation** tends to provide more insight into how commands work, than does the documentation for any of the drivers. ## Examples Below are a couple of examples of using Selenium's `wait_for` family of commands with the [Ruby driver (Selenium-Client).](http://rubyforge.org/projects/selenium-client/ "Selenium Client Ruby Gem at RubyForge") One item of note is that , within `wait_for_condition`, one does *not* need to use `this.browserbot.getCurrentWindow()` to access the DOM of the AUT