In case you missed it, here is the Selenium 3.0 Webinar:

The very first code for Selenium RC was pushed in November 2004.
The first code for WebDriver was released in January 2007.
Selenium 2.0 shipped in July 2011.
In 2016, the Selenium Project is working hard to (finally!) ship 3.0.

Watch this webinar with Simon Stewart, and discover:

  • What will this release contain?
  • What impact will it have on your test runs?
  • How can you preserve your existing investment in tests using the Selenium WebDriver APIs, and your even older RC tests?
  • Looking forward, when will the W3C spec be complete?
  • What can we expect from Selenium 4?

Well a lot of angles covered anyway. As I have a Mac at home and a Win8 PC in work I will be posting examples and tips from both setups. Hopefully it will be a fairly balanced approach. In work I’ll be using WebDriver with the C# programming language, Visual Studio 2013 and NUnit. From my Home setup I will be using Java programming language and the JUnit test framework to write the WebDriver tests, but I am so far undecided on the IDE and build process. For IDE’s Eclipse and NetBeans are free and Intellij is a paid-for application. And the build process can use Maven or Ant. From what I have read online it appears that Maven is the easier one to use to get up and running so I will start with that.

So far I have found the beginning process a lot easier with the C# Visual Studio NUnit approach than with the Java based approach. I think the biggest help for this was my access to Pluralsight training videos, which luckily for me, the trainers all used C#, Visual Studio and NUNit for their test examples in the training courses. I have yet to find a similar resource from the world of Java/JUnit/etc which is part of the reason for writing this blog.

Deciding to write tests with WebDriver is only half the battle, you still need to pick a programming language, and possibly a test framework also. Most of the examples that I will be posting will be using C# and NUnit, but for the most part it should still be readable and easy to transfer to your chosen flavour. Many people use the Java programming language and JUnit or TestNG as the test framework.

But the choice is up to you, pick a flavour that you are comfortable with and run with it!

The reason I am starting this blog is to provide information for people who are new to WebDriver. When I started writing tests with WebDriver I found it very difficult to find information for beginners. Just the basics to begin with, how to get a test up and running before adding any of the fancy stuff.

There are plenty of resources out there who advanced practitioners who know what they are doing, but I found very little for those who are starting off at the beginning.

Hopefully this site will rectify that situation and I also hope that you find it a useful resource.