- Mine: Selenium Simplified [amazon.com] [amazon.co.uk] published by Compendium Developments
- David’s: Selenium 1.0 Testing Tools [amazon.com] [amazon.co.uk] published by Packt
I think both books complement each other well, and you can check for yourself with the free previews available:
- compare table of contents: David’s, Mine
- previews of both books: David’s, Mine – at scribd, on google docs
If you want to learn the IDE then read David’s book, he has done a fantastic job in covering this area. I know from some of the questions I received from readers of “Selenium Simplified” that there is a demand to see coverage of the IDE and I’m glad David has provided this. I don’t use the IDE very much and prefer to have all my tests in Java so this was an area of Selenium that I was never going to cover in detail. I provide an overview of the Selenium IDE, but really try to move people quickly into a Java IDE and get them coding their tests.
David provides an overview of all the main elements of the Selenium tool suite including Selenium Grid and Selenium 2.0. David’s overview of Selenium 2.0 highlights the differences between Selenium 2.0 and 1.0 well. And his Selenium 2.0 chapter will help those of you that know how to program to get started with Selenium 2.0.
My reading of David’s book is that it is an overview of the whole Selenium suite, providing good quality code samples so you can see how to implement some of the features, in and easier to follow style than the online Selenium manual provides.
My book was designed to get people into the coding and programming stage of test automation with Selenium 1.0 quickly. Consequently the bulk of my book is dedicated to coding topics using Java. In this way, I think, they complement each other well.
We both have custom web pages written specifically to allow our readers a place to practice their developing Selenium skills.
My intent was to provide a detailed tutorial to get testers coding Selenium tests in Java using JUnit. Leading them through the learning process of becoming competent with test automation in Java. So I think I provide more detailed information about Java, programming, the style of programming, page object models, refactoring, Ant, continuous integration etc.
Should I really be promoting someone else’s book? Have I accidentally been derogatory in this comparative review and subconsciously trying to steer you over to buying my book? I’d honestly like to think that because the books complement each other well that you will buy both books, and read them, and work through the examples.
David and I clearly wrote with different aims and I’m glad of that. This isn’t choosing between two programming books that cover the same topics in the same way. You will get something different from each book. And where we overlap, we approach the topic differently. The previews linked to above above should help you see the different styles and coverage areas.
So regardless of which (or both) you choose to buy, I think it is great to see alternative approaches available for testers trying to learn automation. And I hope that more practical books on test automation appear in print.
Both books are available in e-book and paperback format.