Selenium 1.0 Testing Tools: Beginner's Guide
and over one million other books are available for Amazon Kindle .
Learn more
| |||||||||||||||
 Trade In this Item for up to £12.20
Get an extra £5 when you trade in books worth £10 or more until June 30, 2012. Trade in Selenium 1.0 Testing Tools Beginner's Guide for an Amazon.co.uk gift card of up to £12.20, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Find more products eligible for trade-in.
|
Frequently Bought Together
Product details
|
More About the Author
Product Description
Product Description
Selenium is a suite of tools to automate web application testing across many platforms. A strong understanding of using Selenium will get you developing tests to ensure the quality of your applications.
This book helps you understand and use Selenium to create tests and make sure that what your user expects to do can be done. It will guide you to successfully implement Selenium tests to ensure the quality of your applications.
The Selenium Testing Tools Beginner’s guide shows developers and testers how to create automated tests using a browser. You’ll be able to create tests using Selenium IDE, Selenium Remote Control and Selenium 2 as well. A chapter is completely dedicated to Selenium 2. We will then see how our tests use element locators such as css, xpath, DOM to find elements on the page.
Once all the tests have been created we will have a look at how we can speed up the execution of our tests using Selenium Grid.
A beginner’s guide to writing Selenium tests using different aspects of the Framework to give you confidence in your web application
This book helps you understand and use Selenium to create tests and make sure that what your user expects to do can be done. It will guide you to successfully implement Selenium tests to ensure the quality of your applications.
The Selenium Testing Tools Beginner’s guide shows developers and testers how to create automated tests using a browser. You’ll be able to create tests using Selenium IDE, Selenium Remote Control and Selenium 2 as well. A chapter is completely dedicated to Selenium 2. We will then see how our tests use element locators such as css, xpath, DOM to find elements on the page.
Once all the tests have been created we will have a look at how we can speed up the execution of our tests using Selenium Grid.
A beginner’s guide to writing Selenium tests using different aspects of the Framework to give you confidence in your web application
Inside This Book
(Learn More)
Suggested Tags from Similar Products(What's this?)Be the first one to add a relevant tag (keyword that's strongly related to this product)
|
What Other Items Do Customers Buy After Viewing This Item?
Customer Reviews
Most Helpful Customer Reviews
2 of 2 people found the following review helpful
Format:Paperback
Selenium 1.0 Testing Tools: Beginners Guide is exactly that. It is a book that is aimed at those who are beginners with the technology (not necessarily beginners to testing or coding). Overall, David Burns has written a good book here. The conversational style is helpful; you feel like you are talking to a team-mate who is explaining the system to you in a friendly and engaging manner. The exercises selected are of a level that you are eased into working with the technology and the tools. The first five chapters are dedicated to the Selenium IDE, which for many testers is all they will ever see of Selenium, and for many testers who want to automate front end tests on Firefox, it may be all they ever need. If that's the case, the first five chapters will give you a lot of practical information and give you some solidly ninja levels skills to write tests and make them robust and solid. They will be limited to the Selenese format, but even with that limitation, there's a lot of cool things that a tester can do, from declaring and using variables, calling JavaScript events, and managing for examining objects and creating robust tests to help enhance testing.
The second half of the book deals with Selenium Remote Control (RC) and here is where some deviation takes place, at least for me. First off, I did not have the exact environment described in this book. I was close, but I had some set-up differences that caused some headaches. A number of the examples in the book just flat out would not work for me. Since my environment was different than that recommended (a Windows 7 machine on a 64-bit Athlon processor), I can't hold David responsible for my roadblocks. It does, however, show a critical issue with the Learn by Doing format of this book. If everything is the same, the format is terrific, and the first 6 chapters I was able to accomplish most of the project objectives and practice using the tools as listed. When I found myself stuck, there was little I could do to get around the issues. Be aware of that going in, your mileage may vary with the examples shown in the book.
Another frustration I had was specifically in Chapter 7, which dealt with writing your own scripts in Selenium RC. The chapter is structured around using the IntelliJ Idea Java IDE. In and of itself, this is not a bad practice, but when things start to not line up due to environments being different, adding an IDE into the mix can add even more complications and details to keep track of. While I appreciated the clean nature of integrating JUnit and the Selenium libraries under one roof, it added another layer that I personally felt might have been better handled by not including another tool. Agreed, CLI's are not sexy and they require repetition that the IDE doesn't, but I would have appreciated more specific examples and more complete examples. As it is, to get around the behaviors I was seeing, I generated tests in the IDE, saved the structure as a separate file, and then loaded that file to write my tests.
Again, these criticisms are actually pretty minor, and they are colored because my own environment had trouble with the examples (of which David states that 64 bit environments will have issues). Overall, this is a great first effort in describing the tools and the methods involved in loading, installing, and working with the Selenium stack. As the technology becomes more well known and solidifies, I'd like to see what David does with a future Selenium treatment. There's a lot of gold in here, and a few pieces of pyrite (and again, I have to take responsibility for my own panning), but all in all it fills a void for documentation for Selenium with a continuity that a beginner can appreciate and get productive with quickly.
The second half of the book deals with Selenium Remote Control (RC) and here is where some deviation takes place, at least for me. First off, I did not have the exact environment described in this book. I was close, but I had some set-up differences that caused some headaches. A number of the examples in the book just flat out would not work for me. Since my environment was different than that recommended (a Windows 7 machine on a 64-bit Athlon processor), I can't hold David responsible for my roadblocks. It does, however, show a critical issue with the Learn by Doing format of this book. If everything is the same, the format is terrific, and the first 6 chapters I was able to accomplish most of the project objectives and practice using the tools as listed. When I found myself stuck, there was little I could do to get around the issues. Be aware of that going in, your mileage may vary with the examples shown in the book.
Another frustration I had was specifically in Chapter 7, which dealt with writing your own scripts in Selenium RC. The chapter is structured around using the IntelliJ Idea Java IDE. In and of itself, this is not a bad practice, but when things start to not line up due to environments being different, adding an IDE into the mix can add even more complications and details to keep track of. While I appreciated the clean nature of integrating JUnit and the Selenium libraries under one roof, it added another layer that I personally felt might have been better handled by not including another tool. Agreed, CLI's are not sexy and they require repetition that the IDE doesn't, but I would have appreciated more specific examples and more complete examples. As it is, to get around the behaviors I was seeing, I generated tests in the IDE, saved the structure as a separate file, and then loaded that file to write my tests.
Again, these criticisms are actually pretty minor, and they are colored because my own environment had trouble with the examples (of which David states that 64 bit environments will have issues). Overall, this is a great first effort in describing the tools and the methods involved in loading, installing, and working with the Selenium stack. As the technology becomes more well known and solidifies, I'd like to see what David does with a future Selenium treatment. There's a lot of gold in here, and a few pieces of pyrite (and again, I have to take responsibility for my own panning), but all in all it fills a void for documentation for Selenium with a continuity that a beginner can appreciate and get productive with quickly.
1 of 1 people found the following review helpful
Format:Paperback
This book is beneficial, but i found it quite vague, particularly around exercises, the author gives you the code to write a small exercise and then says to have a go at something a bit more difficult but doesn't give the answer to it anywhere, its just too vague. Luckily i could figure it out as i have used Selenium for a while but too a new user i think they may struggle with it.
Having said that there are some good tips in the book but in my opinion he needs to rewrite this with stronger exercises and with the solutions!!!! It was beneficial to me as i have used Selenium before!
Having said that there are some good tips in the book but in my opinion he needs to rewrite this with stronger exercises and with the solutions!!!! It was beneficial to me as i have used Selenium before!
Most Helpful Customer Reviews on Amazon.com (beta)
Amazon.com:
6 reviews
3 of 3 people found the following review helpful
Uh...did anyone edit this?
18 May 2011
Format:Paperback|Amazon Verified Purchase
I have not reviewed a single book on Amazon up until now, but feel compelled to do so for this book. After reading "JUnit in Action", "Head First Java", and "Professional Android Application Development" (all excellent), this book felt like it was written by people who had never read a book on programming or software, nor hired any editorial staff whatsoever.
Although they do cover many of the main topics of Selenium and it is an introduction to the testing framework, that's where its resemblance to a textbook ends. The language is unclear. Examples are poorly explained and contain errors. The general layout of the book is not intuitive. They do not go into any depth with each main concept at all. In sections of the book they restate the previously explained points or include duplication of code for the sake of lengthening the book - seriously. It's as if they were writing a secondary school paper that had to be 200 pages long and they just made it. It could have been 50 pages shorter.
Like the Selenium project, this book should be open source. I would rather have my money back, be able to read it online for free, and submit edits. Everyone would benefit. If you are new to programming, read up on Javascript and read all online Selenium documents before reading this book, otherwise it may be a waste of time - or worse, scare you away from using Selenium at all. If you already know Selenium pretty well and are a novice programmer, you'll get useful information from it, but be saddened by it's lack of quality. I wish there were something better. Maybe I should start writing.
Although they do cover many of the main topics of Selenium and it is an introduction to the testing framework, that's where its resemblance to a textbook ends. The language is unclear. Examples are poorly explained and contain errors. The general layout of the book is not intuitive. They do not go into any depth with each main concept at all. In sections of the book they restate the previously explained points or include duplication of code for the sake of lengthening the book - seriously. It's as if they were writing a secondary school paper that had to be 200 pages long and they just made it. It could have been 50 pages shorter.
Like the Selenium project, this book should be open source. I would rather have my money back, be able to read it online for free, and submit edits. Everyone would benefit. If you are new to programming, read up on Javascript and read all online Selenium documents before reading this book, otherwise it may be a waste of time - or worse, scare you away from using Selenium at all. If you already know Selenium pretty well and are a novice programmer, you'll get useful information from it, but be saddened by it's lack of quality. I wish there were something better. Maybe I should start writing.
3 of 3 people found the following review helpful
Already dated
5 May 2011
Format:Paperback|Amazon Verified Purchase
The problem with this book is on Selenium 1, and it apparently came out just when Selenium 2 was coming out. Fortunately Selenium 2 seems to be pretty well backwardly compatible, so you can use what is presented in the book, but the bad news is that it contains only a tiny bit of Selenium 2 content, so it is already pretty dated. I think the publisher should have just waited a month or two and made it a Selenium 2 book.
4 of 5 people found the following review helpful
Selenium 1.0 Test Tools: Beginners Guide
20 Mar 2011
Format:Paperback
Selenium 1.0 Testing Tools: Beginners Guide is exactly that. It is a book that is aimed at those who are beginners with the technology (not necessarily beginners to testing or coding). Overall, David Burns has written a good book here. The conversational style is helpful; you feel like you are talking to a team-mate who is explaining the system to you in a friendly and engaging manner. The exercises selected are of a level that you are eased into working with the technology and the tools. The first five chapters are dedicated to the Selenium IDE, which for many testers is all they will ever see of Selenium, and for many testers who want to automate front end tests on Firefox, it may be all they ever need. If that's the case, the first five chapters will give you a lot of practical information and give you some solidly ninja levels skills to write tests and make them robust and solid. They will be limited to the Selenese format, but even with that limitation, there's a lot of cool things that a tester can do, from declaring and using variables, calling JavaScript events, and managing for examining objects and creating robust tests to help enhance testing.
The second half of the book deals with Selenium Remote Control (RC) and here is where some deviation takes place, at least for me. First off, I did not have the exact environment described in this book. I was close, but I had some set-up differences that caused some headaches. A number of the examples in the book just flat out would not work for me. Since my environment was different than that recommended (a Windows 7 machine on a 64-bit Athlon processor), I can't hold David responsible for my roadblocks. It does, however, show a critical issue with the Learn by Doing format of this book. If everything is the same, the format is terrific, and the first 6 chapters I was able to accomplish most of the project objectives and practice using the tools as listed. When I found myself stuck, there was little I could do to get around the issues. Be aware of that going in, your mileage may vary with the examples shown in the book.
Another frustration I had was specifically in Chapter 7, which dealt with writing your own scripts in Selenium RC. The chapter is structured around using the IntelliJ Idea Java IDE. In and of itself, this is not a bad practice, but when things start to not line up due to environments being different, adding an IDE into the mix can add even more complications and details to keep track of. While I appreciated the clean nature of integrating JUnit and the Selenium libraries under one roof, it added another layer that I personally felt might have been better handled by not including another tool. Agreed, CLI's are not sexy and they require repetition that the IDE doesn't, but I would have appreciated more specific examples and more complete examples. As it is, to get around the behaviors I was seeing, I generated tests in the IDE, saved the structure as a separate file, and then loaded that file to write my tests.
Again, these criticisms are actually pretty minor, and they are colored because my own environment had trouble with the examples (of which David states that 64 bit environments will have issues). Overall, this is a great first effort in describing the tools and the methods involved in loading, installing, and working with the Selenium stack. As the technology becomes more well known and solidifies, I'd like to see what David does with a future Selenium treatment. There's a lot of gold in here, and a few pieces of pyrite (and again, I have to take responsibility for my own panning), but all in all it fills a void for documentation for Selenium with a continuity that a beginner can appreciate and get productive with quickly.
The second half of the book deals with Selenium Remote Control (RC) and here is where some deviation takes place, at least for me. First off, I did not have the exact environment described in this book. I was close, but I had some set-up differences that caused some headaches. A number of the examples in the book just flat out would not work for me. Since my environment was different than that recommended (a Windows 7 machine on a 64-bit Athlon processor), I can't hold David responsible for my roadblocks. It does, however, show a critical issue with the Learn by Doing format of this book. If everything is the same, the format is terrific, and the first 6 chapters I was able to accomplish most of the project objectives and practice using the tools as listed. When I found myself stuck, there was little I could do to get around the issues. Be aware of that going in, your mileage may vary with the examples shown in the book.
Another frustration I had was specifically in Chapter 7, which dealt with writing your own scripts in Selenium RC. The chapter is structured around using the IntelliJ Idea Java IDE. In and of itself, this is not a bad practice, but when things start to not line up due to environments being different, adding an IDE into the mix can add even more complications and details to keep track of. While I appreciated the clean nature of integrating JUnit and the Selenium libraries under one roof, it added another layer that I personally felt might have been better handled by not including another tool. Agreed, CLI's are not sexy and they require repetition that the IDE doesn't, but I would have appreciated more specific examples and more complete examples. As it is, to get around the behaviors I was seeing, I generated tests in the IDE, saved the structure as a separate file, and then loaded that file to write my tests.
Again, these criticisms are actually pretty minor, and they are colored because my own environment had trouble with the examples (of which David states that 64 bit environments will have issues). Overall, this is a great first effort in describing the tools and the methods involved in loading, installing, and working with the Selenium stack. As the technology becomes more well known and solidifies, I'd like to see what David does with a future Selenium treatment. There's a lot of gold in here, and a few pieces of pyrite (and again, I have to take responsibility for my own panning), but all in all it fills a void for documentation for Selenium with a continuity that a beginner can appreciate and get productive with quickly.
Were these reviews helpful?
Let us know
Listmania!
Look for similar items by category
Look for similar items by subject
Feedback
- Would you like to update product info or give feedback on images?
- I am the Author, and I want to comment on my book.
- I am the Publisher, and I want to comment on this book.
|
