You have installed the tools? You have an IDE setup? You’ve written and run your first Selenium WebDriver test?
If not then follow our free tutorial videos on this very site, then come back here.
You need to:
- Browse the documentation on the Selenium HQ (http://seleniumhq.org/) site.
- Follow the official blog , particularly the “Smattering of Selenium” posts that Adam Goucher writes (http://seleniumhq.wordpress.com/)
- Read and follow my Selenium Simplified blog rss feed or
subcribe to our email list
If you only do one of the above then make it step 2. Then follow the links in “Smattering of Selenium” to find other resources and links that are worth following.
Read Other People’s Code
When I learned to code I did so by reading other people’s code.
People tend not to do that today, so you can get an edge.
Remember the most important code to look at is the Selenium code base itself, so attach the source, and start browsing.
There are open source projects which use WebDriver – have a look at their code:
- RichFaces uses WebDriver in its testing https://github.com/richfaces
- The Vorburger project may have some interesting code to learn from https://github.com/vorburger/webdriver-reporting
- Thucydides is a library built on top of WebDriver which again you can read the code and see how other people have used WebDriver https://github.com/thucydides-webtests/thucydides
Recommended books for Java:
- Java For Testers by Alan Richardson
- Effective Java by Joshua Bloch
- Implementation Patterns by Kent Beck
- Growing Object-Oriented Software, Guided by Tests by Steve Freeman and Nat Pryce
And probably in that order.
The most important thing to do is to build automation code.
If you get stuck then consider our full WebDriver Course. It goes into depth of the API with lots of exercises. It provides some structure as you learn, with working source code you can refer to if you get stuck.
But the most important thing is to start doing. Add automation where it adds value on your projects. Add Abstraction layers so that you don’t spend your entire time maintaining the code.
Just start experimenting.