README.markdown in selenium-client-1.2.2 vs README.markdown in selenium-client-1.2.3

- old
+ new

@@ -34,21 +34,33 @@ * State-of-the-art reporting for RSpec. Plain API ========= - Selenium client is just a plain Ruby API, so you can use it wherever you can use Ruby. For instance + Selenium client is just a plain Ruby API, so you can use it wherever you can use Ruby. + + To used the new API just require the client driver: + + require "rubygems" + require "selenium/client" + + For a fully backward compatible API you can start with: + + require "rubygems" + gem "selenium-client" + require "selenium" + + For instance to write a little Ruby script using selenium-client you could write something like: #!/usr/bin/env ruby # # Sample Ruby script using the Selenium client API # require "test/unit" require "rubygems" - gem "selenium-client" - require "selenium" + require "selenium/client" begin @browser = Selenium::Client::Driver.new("localhost", 4444, "*firefox", "http://www.google.com", 10000); @browser.start_new_browser_session @browser.open "/" @@ -140,11 +152,14 @@ Selenium client comes with some convenient Rake tasks to start/stop a Remote Control server. To leverage all selenium-client capabilities I recommend downloading a recent nightly build of a standalone packaging of Selenium Remote Control (great for kick-ass Safari and Firefox 3 support anyway). You will find the mightly build at [OpenQA.org](http://archiva.openqa.org/repository/snapshots/org/openqa/selenium/selenium-remote-control/1.0-SNAPSHOT/) - + + You typically "freeze" the Selenium Remote Control jar in your `vendor` + directory. + require 'selenium/rake/tasks' Selenium::Rake::RemoteControlStartTask.new do |rc| rc.port = 4444 rc.timeout_in_seconds = 3 * 60 @@ -187,6 +202,6 @@ You can then get cool reports like [this one](http://ph7spot.com/examples/selenium_rspec_report.html) - \ No newline at end of file +