A Smattering of Selenium #44
What started out as the week of Capybara rounded itself out fairly nicely
I’m not a fan of using 3rd party abstraction layers (1st party are full win though) but Capybara has a large marketshare so Capybara (and Selenium) with RSpec & Rails 3: quick tutorial is likely going to be of interest to people.
And while on the subject of Capybara, here is a post on Checking Invisible Elements in it.
Keeping with the Capybara theme, we have Configuring User Agents with Capybara + Selenium Webdriver
Unit tests are overrated is a nice reminder to change all the tests in a system for a change — not just the unit ones. (C’mon, how many of us haven’t been burned and/or responsible for this.)
People-driven Test Automation includes this nice blurb
Successful test automation uses good tests that provide clear test results. A pass or no-pass result must be confident and trustworthy. By focusing on what the system should do rather than how it does it, this can be achieved easily and without breaking existing test cases whenever the logic of the system is changed.
Automate Kingdoms Camelot using Selenium reminds me of the days when I had the MUD we played in fully scripted.
How to include dynaTrace in your Selenium Tests is an interesting idea. Would be even better using Page Objects that were controlled externally so you don’t have to modify working scripts to enable/disable timings. But that’s an exercise for the reader to do. (Oh, and if their marketing firm wasn’t tweeting about it every day, that would be keen too.)
#SFSE Video: Selenium Problem Solving Sessions has, amung other things, a demo of the dynaTrace thing.
User-Extensions With Selenium RC Using Ruby Client Driver (selenium-client) is slightly out of date (use selenium-webdriver, not selenium-client) but aside from that, has an important missing bit of the user-extension documentation — how to use them from inside a script.
I haven’t watched it, but From Continuous Integration to DevOps: Co-Evolution of Agile and Automation seems interesting. I actually used the phrase “Selenium is the gateway drug to DevOps” the other week.
Jenkins, RVM, and Selenium is really about Cucumber, but…
Setting up Selenium server on a headless Jenkins CI build machine is similar to the 8th light one, but for Selenese
Building Custom Test Frameworks is a bit of a cautionary tale
The whole where-is-this-binary-hiding-on-this-machine-problem on windows has bit people a number of times, Test Automation: Checking for Bit-ness suggests a solution (in C#)
Functional Tests with Selenium 2.0 and cargo-maven-plugin updates some common documentation around launching the Se server and tests from inside Maven