andthennothing.net: Selenium on Rails

Comment on Selenium on Rails by Igor

2008-03-05T10:17:38+00:00

Hi Jonas. Where can i see the by seleniumOnRails produces HTML-Output? I have a little problem with the .rsel-tests and AJAX. After click "commit" on ajax-form, only the partial is loaded (though is correct) but the other stuff like layouts and css is gone (i see like only the partial output not the whole page). The same test runs completely correct in selenium-IDE. Thank you in advance.

Comment on Selenium on Rails by nullkhairi

2006-12-10T09:57:48+00:00

I AM STUDENT RFOM IRAQ I NEED SEARCH ABOUT SELENIUM ELEMENT IF U CAN HELP ME WITH MY REGARDS ...

Comment on Selenium on Rails by Jonas

2006-05-11T22:46:41+00:00

Thank you CH! I've updated the svn repository.

Comment on Selenium on Rails by CH

2006-05-04T22:16:13+00:00

The SeleniumOnRails::FixtureLoader in Selenium on Rails tries to use every file under /test/fixtures when calling /selenium/setup?fixtures=all I'm using an image fixture for testing file upload, and I have image.gif in /test/fixtures. Changing the available_fixtures method seems to fix the problem: def available_fixtures files = Dir["test/fixtures/*.{yml,csv}"] files.collect {|f| f.sub(/\.[^.]*$/, '').sub('test/fixtures/', '')} end

Comment on Selenium on Rails by Anon

2006-03-27T17:58:28+00:00

Can't wait to try this out. Thanks for fully developing it as a plugin

Comment on Selenium on Rails by Jonas

2006-02-19T14:30:55+00:00

Shinya: the new version is enabled for test environment only by default.

Eric: your patch is included in the new version. Thanks a bunch!

Comment on Selenium on Rails by Jonas

2006-02-16T08:14:27+00:00

No, the two plugins are two different solutions to the same problem. If you want to write the tests in Ruby and use my plugin, Erik's patch above is the closest match at the moment. Have you noticed Selenium IDE? It's a neat way to author and edit Selenese test files.

Comment on Selenium on Rails by lstrecv

2006-02-16T06:26:11+00:00

http://svn.viney.net.nz/things/rails/plugins/selenium_testing/README Do you interface with this, use this?

Comment on Selenium on Rails by Eric

2006-02-15T21:40:32+00:00

I'm glad you like it! I included rdoc and test cases and tried to stick to your style as much as possible.

And yes, method_missing would be a perfectly valid approach. I put in stubs for two reasons:

It gives rdoc something to document, and
It would allow future support for keyword arguments, such as ':regex ...', where Selenium has multiple argument formats.

I think that (1) is useful, and (2) is probably not important. So it's up to you how it should work!

The one thing that I didn't include was easy support for loading fixtures before generating the tables. There's a really nice version of that {{here}}, but I'm not quite sure how it might work in Selenium On Rails.

Once again, my many thanks for a great plugin! It's going to make several upcoming projects much easier.

Comment on Selenium on Rails by Jonas

2006-02-15T21:02:48+00:00

Nice patch Erik, good job!

I've just browsed through the code briefly, but I have one question: don't you think it's better to use method_missing where no logic is required? It would result in less code and would support user-extensions.js.

I'm currently working on rake task support, so I will look into it further when I'm done with that.

Comment on Selenium on Rails by Eric

2006-02-15T14:06:25+00:00

Thanks for the cool plugin, Jonas! I agree, sometimes it's good to duplicate constants. Other times, though, I just want to write:

|assertTitle|#{SITE_NAME}|

...and not worry about updating a bunch of test cases when the site name changes. Similarly, I may not want manually update 20 test cases if I re-route some internal URLs.

My ideal goal is "Once and Only Once": each piece of knowledge should be represented in a single place, and tested in a single place. Perhaps my traditional controller tests already check that certain URLs get routed correctly, and I don't want that information to be duplicated throughout my Selenium tests.

I hope this make some kind of deranged sense, at least. ;-) In any case--on the off chance you find my patch useful--you're welcome to do anything you want with it. It's the least I can do to thank you for making my life much easier!

Comment on Selenium on Rails by Eric

2006-02-15T13:50:40+00:00

OK, I decided to actually write some code. :-) Click on my name for a patch which enhances Selenium on Rails to support native Ruby test cases, including configuration data and URL routing.

Here's a sample:

test.setup # Load fixtures
test.open :controller => 'customer',
          :action => 'list'
test.assert_title 'Customers'
test.click 'myLink', :wait => true
test.assert_title 'Customer: *'

You can download my patch from here. (Yes, there's really a link there, even though it isn't underlined.)

Comment on Selenium on Rails by Jonas

2006-02-14T21:27:53+00:00

Thanks Erik! I'll consider it, but isn't it good with duplication in this case? If the constants change for some reason, don't you want the tests to fail?

Do you have any example of what kind of constant you're talking about?

Comment on Selenium on Rails by Eric

2006-02-14T13:05:46+00:00

Great plugin! One thought: It would be really nice to be able to use ERB from within Selenese. This way, I could look up site configuration variables and use them in test cases, eliminating some unnecessary duplication of constants.

Comment on Selenium on Rails by Jonas

2006-02-08T22:20:33+00:00

Thanks for sorting that out Shinya!

I agree that the plugin should only be available for test environment per default. It has been available for development due to convenience, but I'll change it.

Comment on Selenium on Rails by Shinya

2006-02-08T03:20:59+00:00

What do you think about adding an option to disable Selenium in development environment?

If you don't use fixtures, enabling Selenium in development environment would be useful. But if you do use fixtures, I prefer to disable it because it will mess up the development database.

Comment on Selenium on Rails by Shinya

2006-02-08T01:50:40+00:00

Jonas, thanks for the new version. It's working very well. I found that link= locator doesn't work in Selenium gem, but works if you install Selenium from svn into vendor/selenium/javascript. It seems that the gem version is too old...

Comment on Selenium on Rails by Jonas

2006-02-07T23:37:21+00:00

Check the new version out and see if it addresses your issues!

Shinya: Thanks! Selenium IDE looks great! I'll try it out some time...

Joe: link=linktext doesn't work for me either, but I have no idea why. I don't understand how this could be the plugin's fault though. Let me know if you sort it out.

Comment on Selenium on Rails by Joe

2006-02-07T18:43:13+00:00

I'm trying to use this (looks great), however I get errors when it tries to use element locators like "link=some link text to match" - it shows an error "Element link=some link text to match not found" Anyone else getting this?

Comment on Selenium on Rails by Shinya

2006-02-07T08:11:06+00:00

Comment on Vincent's patch: I also had to modify it to skip files that end with "~", which is an Emacs backup file.

Comment on Selenium on Rails by Shinya

2006-02-07T07:28:37+00:00

Very nice plugin! I'm an author of Selenium IDE which has been released recently (see http://www.openqa.org/selenium-ide/), and I've added a custom format to Wiki that can be used to edit tests for Selenium on Rails. http://wiki.openqa.org/display/SIDE/SeleniumOnRails

Comment on Selenium on Rails by Vincent

2006-02-07T06:02:16+00:00

That's just awesome thanks! I gonna start using it.
I've used the generator to produce a simple test and could run the tests. However, rake test produces errors: 28 tests, 58 assertions, 6 failures, 0 errors
any idea? I am running ruby 1.8.3 on Ubuntu
I also noticed that .svn directories are listed as test suites, so I wrote a small patch to omit hidden files:
Index: vendor/plugins/selenium_on_rails/lib/selenium_on_rails/suite_renderer.rb
===================================================================
--- vendor/plugins/selenium_on_rails/lib/selenium_on_rails/suite_renderer.rb (revision 2)
+++ vendor/plugins/selenium_on_rails/lib/selenium_on_rails/suite_renderer.rb (working copy)
@@ -37,6 +37,7 @@
dirs = [] #add dirs to an array in order for files to be processed before dirs
Dir.entries(path).each do |e|
next if ['.','..'].include? e
+ next if e.starts_with? '.'
filename = File.join path, e
if File.directory? filename
dirs << [filename, "#{suite_name}#{e.humanize}."]

Comment on Selenium on Rails by Wayne

2006-02-07T05:34:44+00:00

Suite, that works! (pardon the pun...) I was still getting unbalanced newlines (and 6 test failures), so I changed your clean_text method to: text.gsub("\t", ' ').gsub("\r\n", "").gsub("\n","") to just get rid of em all. Thanks for the update!

Comment on Selenium on Rails by Jonas

2006-02-07T01:10:22+00:00

Wayne, could you please try the new version out?

Comment on Selenium on Rails by Peter

2006-02-06T23:01:39+00:00

This looks very promising. Good work!

Selenium on Rails

2006-02-05T23:49:00+00:00

Selenium on Rails has moved.

New version.

Updates at the end.

One of the things I like about Rails is the built-in support for testing – it’s almost hard not to write tests. But even if I write extensive tests (currently “Code to Test Ratio: 1:3.4” according to rake stats in a small toy project) I still feel that it’s not enough. I occasionally get the urge to fire up the browser and click around to test that everything works. You shouldn’t have to “click around” to test that you haven’t broken anything that often (although it’s probably good to use the browser for checking usability).

That’s where Selenium comes in. It’s a javascript based functional test tool that uses Fit like test scripts to test web application directly in the browser. There are other ways to test in browsers, like Watir, but they don’t run in any browser/platform so I think that javascript based solutions are the way to go. And for javascript based solutions I don’t know if there are any competition at all.

However, I didn’t think that vanilla Selenium worked as smooth as it should in a Rails context. So I’ve been writing a plug-in that makes the experience much better, IMHO. It took a bit longer than what I thought, but I’ve been busy and stuff like this takes time to get into a good enough state to release to the world.

Please try it out and let me know if you have any problems using it or if you have suggestions for improvements!

Overview

Selenium on Rails provides an easy way to test Rails application with Selenium.

This plugin does four things:

The Selenium files don’t have to pollute /public, they can stay in the Selenium gem or in /vendor/selenium/javascript.
No need to create suite files, they are generated on the fly—one suite per directory in /test/selenium (suites can be nested).
Instead of writing the test cases in HTML you can use ERb/RHTML or Selenese (a template provided by this plugin).
Loading of fixtures and wiping of session (/selenium/setup).

Selenium on Rails is disabled for production environments.

Installation

Selenium needs to be available. It could either be installed as a gem (gem install selenium) or in /vendor/selenium/.
Install Selenium on Rails: script/plugin install http://andthennothing.net/svn/public/selenium_on_rails/
If RedCloth is available the Selenese test cases can use it for better markup.
Run the Rakefile in the plugin’s directory to run the tests in order to see that everything works. (If RedCloth isn’t installed a few tests will fail since they assume RedCloth is installed.)
Create a test case: script/generate selenium login
Start the server: script/server
Point your browser to http://localhost:3000/selenium
If everything works as expected you should see the Selenium test runner. The north east frame contains all your test cases (just one for now), and the north frame contains your test case.

Todo

user_extension.js

Selenium has support for user_extension.js which is a way to extend the functionality of Selenium. However there is currently no easy way to add such a file in Selenium on Rails.

Partials

It would be nice if common parts of test cases could be stored in partials.

More setup/teardown support?

Currently there is only support to load fixtures and to wipe the session in /selenium/setup. Is there a need for more kinds of setups or teardowns?

Credits

Jon Tirsen—initial inspiration

Contact

Jonas Bengtsson, jonas.b@home.se, http://andthennothing.net

Update: The first defect fix is out. It should now work on EdgeRails as well as Rails 1.0.0 (might work on other versions). And the tests ought to pass on non-Windows machines. Thanks Wayne for reporting these errors!

script/plugin update (or reinstall the plugin if that doesn’t work)

Update 2: Another defect fix to make sure .files, and files~ are handled correctly, and updated the tests (they work on Windows and NetBSD at least). Thanks Wayne, Vincent and Shinya!

Update 3: New version.