I’m in San Francisco for a couple days, and so had to clear out some tabs before getting on the plane. Here’s what I thought was interesting.

  • Tellurium is another wrapper around Selenium. Looks like it has a couple things that we could borrow back.
  • Why Selenium and Rspec? describes how to use RSpec with Selenium and how to involve both people who can code, and those who cannot.
  • If you are writing Se tests, then you should also be running them under CI. Thoughts on Fowler’s Continuous Integration is a nice, quick tour through the [one of] the more important papers on the topic. Good review to some, necessary primer for others.
  • Looks like the ‘Se in the cloud’ space is about to get more crowded with regressr coming out of stealth mode soon. (Where is my invite?)
  • There is also Selenium Shots which looks like it is a custom Grid which will send you screen shots of what your page renders like in different browsers. I found out about them through their gem
  • Another gem that crossed my path was Cross-stub which attempts to solve Existing mocking/stubbing frameworks support only stubbing in the current process. This is OK most of the time. However, when running cucumber integration test suite in non-webrat mode, these in-process stubbing frameworks simply doesn’t help. Or something.
  • Want to run your Webrat, Polonium or JSUnit tests in the Sauce Labs OnDemand cloud? You could use the Saucelabs-adaptor gem that the folks at Pivotal have created.
  • Gojko discusses How to implement UI testing without shooting yourself in the foot
  • Alister Scott, a Watir core developer, talks a bit about the future of Watir, Selenium & WebDriver
  • Kevin wastes no time rebooting the Se-Grid project by releasing Se-Grid 1.0.6 which is primarily a bug fix release.
  • Testuff is ‘on-demand software test management’. I haven’t needed to use it, but they now have an integration with Se-IDE. Of course, what they should do is make it an Se-IDE plugin, but…
  • If you are using Se and Zope2, then Zelenium might be of interest. Or might not. Your call.
  • Aaron (after some prompting) ruminates on Smart or Dumb Page Objects.
  • I’ve never heard of the ZK Framework, but if you use it then you can run Se tests against it with zk-ztl
  • Speed of execution, and the need for increasing it are constant topics in the Se community. Here is one solution that uses Rake – Speeding up multi-browser Selenium Testing using concurrency
  • Kevin’s (as in the new maintainer of Se-Grid) day job is Mogotest which is where he posted a tutorial on How to Accept Self-Signed SSL Certificates in Selenium. Again, just say no to self-signed certificates in test, and this problem doesn’t happen.
  • Love RSpec and Se? You could try the selenium-rspec-dsl gem. Looks like its brand spankin’ new.
  • I love the Faker gem when automating in Ruby/Rails. There is now a C# (3.5 SP1) port of it.
  • For a client I need to look at controlling things of the browser, not in the browser. Here are some of the links I’ve collected on the subject. First, there is Selenium – Handle Dialogs which uses . And an alternate solution is Automating Windows with Autohotkey. For people on the Mac there isAutomator. But unfortunately if you are Linux then you are out of luck due to lack of standard windowing systems.
  • Synchronizing when an AJAX request is finished can sometimes be a pain. Here is a solution if you are using Ajax4JSF or RichFaces
  • The introduction to Pyrite pretty much says it all: We found Cucumber to be awesome, but no one was reading the features. We found Webrat to be fantastic, but way too complex for what we wanted. So, we made Pyrite – a few selenium-client methods wrapped up in a readable way.
  • Frames can be a bitch. Accessing IFRAME Data with Selenium RC tries to limit the pain
  • IronRuby has gone 1.0. If you are a .NET shop, stop creating your scripts in C# and start using IronRuby. As in immediately — if not sooner. (Well, you could also use IronPython, but thats not newsworthy this round.)