Skip to main content

Jun 6, 2018 - 2 minute read - Selenium Simplified Blog WebDriver

Open Source Selenium Migration book

Back in 2011 I started to document migration steps from Selenium 1 to Selenium 2.

I covered Selenium 1 in Selenium Simplified and Selenium Webdriver in my online training course.

I created a workshop to support people migrating and seem to have converted into a ‘book’ format between 2011 and 2014.

Time to release it as Open Source.

Where is it?

What’s in it?

The repo above has all the source code for the book:

The repo has a Selenium 1 code folder \initial-code

And the same @Test and abstraction layers for Selenium 2 in \migrated-code

The ‘book’ is the text for the workshop and has all the migration steps and refactorings and code changes for moving from initial-code to migrated-code.

You can find the pdf of the book to download from the releases page.


The book is pretty much untouched since 2014.

I made a few small changes to generate the PDF.

  • amended the source code to be slightly better formatted by using ~~~~~~~~ blocks
  • added the images that were missing from the original doc
  • line wrapped the source code so it doesn’t fall off the page when generated as a pdf

But basically didn’t edit it or change it. I haven’t even checked it for spelling errors. Expect there to be spelling errors.

The code isn’t runnable since it uses Ant and I haven’t added the dependencies into the repo to keep it small - plus those version of Selenium won’t work with current browsers.

Why Release?

I think it is important to release as much of our work as we can. But also. Because it is a case study. I think it still has value.

  • Step by Step thinking of a migration project explained
  • Examples of Page Objects (admittedly I don’t write them like this now, but for some people this approach might be new)
  • comparison of the flatter Selenium API with WebDriver
  • its pretty short

Historical Artifact

Hopefully it adds some value, and it helps me trim out some files from my hard drive.

You will need a Github account to comment. Or you can contact me with your comment.

I reserve the right to delete spam comments e.g. if your comment adds no value and its purpose is simply to create a backlink to another site offering training, or courses, etc.