- Paperback: 258 pages
- Publisher: Pragmatic Bookshelf; 1 edition (October 2, 2016)
- Language: English
- ISBN-10: 9781680501834
- ISBN-13: 978-1680501834
- ASIN: 1680501836
- Product Dimensions: 7.5 x 0.5 x 9.2 inches
- Shipping Weight: 1.7 pounds (View shipping rates and policies)
- Customer Reviews: 15 customer reviews
- Amazon Best Sellers Rank: #312,227 in Books (See Top 100 in Books)
The Way of the Web Tester: A Beginner's Guide to Automating Tests 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
See the Best Books of 2019
Browse the Amazon editors' picks for the Best Books of 2019, featuring our favorite reads in more than a dozen categories.
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Frequently bought together
Customers who viewed this item also viewed
From the Publisher
About this Book
Be warned—this isn’t your typical deep dive tutorial book. We aren’t going to spend hundreds of pages walking you through how to set up this kind of test framework or that. The technology changes too quickly.
Instead, we are going to focus on the fundamentals. Those things that simply don’t change. These you will be able to take with you and apply to any project—regardless of which automated test framework or platform you choose to use.
And it is good to see you because automated testing is one of the greatest levers we’ve got for scaling the most valuable asset any software project has—you.
You see, you’re kind of a big deal. We need more of you. We need more of your critical thinking. We need more of your creativity. And we need more of your time. And by learning how to write automated tests, that’s really what you are giving yourself and the others on your team. More time.
If you are a traditional software tester who has little or no programming experience, this is the perfect book for getting started. Together we are going to start from the ground up and give you everything you need to create and start writing your very own automated tests today.
If you are a developer, but haven’t thought a ton about how automated testing works, this is your crash course on how to move fast without breaking stuff. That means more time working on fun things, like adding new features, and less time working on the boring stuff, like fixing old bugs.
And if you are a team lead, this is your Rosetta Stone. This book will not only help you bridge the gap between traditional testers and developers, it will give you and your team the time, the language, and the framework to set your automated tests up right, while avoiding much of the duplication and wasted effort that usually comes to teams when they are just starting out.
This is a book about how to write automated tests for the web. It’s a book for anyone who has ever wanted to learn:
- How automated testing on the web works
- What the different kinds of automated tests are
- And, most importantly, how to get started writing them, even if you have little or no programming background or experience
About the Author
Jonathan is the author of "The Agile Samurai." An experienced programmer, Jonathan has helped some of the world's leading software companies find better ways of working and playing together. When not cycling to work in the throes of winter you can find him developing software and coaching teams at Spotify.
15 customer reviews
There was a problem filtering reviews right now. Please try again later.
_Web Tester_ reminds me of the book that helped me learn Ruby, Brian Marick's _Everyday Scripting with Ruby_. I can work through the examples as I go, and that's the way I learn best. I get anxious when trying to master new coding skills, and the author's lighthearted and fun tone helps me remember it's ok to make mistakes. I can also learn from his own "war stories", which is better than living through them myself!
Everyone on a software delivery team will get value from reading this book. Automation, especially at the UI level, is a continual challenge. Even highly experienced teams like my current team can fall over the cliffs of despair trying to maintain fragile tests that give false results. If you're new to automation, this is a perfect place to start learning. If you've been doing it for years, this is a great opportunity to refresh your skills. Grab a mug of tea, a pencil and a keyboard and start enjoying!
Although this book is focused on testing for web applications, it should prove useful for people using other technologies, such as mobile development. The details are not the same, but the underlying principles about the nature of UI, integration and unit tests don't change.
This is a book about testing, not about Test-Driven Development; the latter is discussed in the final chapter. While testing is useful for both programmers and testers, TDD is mostly useful for programmers. For this reason, I suggest programmers to read more about TDD after this book. I suggest Kent Beck's "TDD By Example."
Full disclosure: I was a reviewer of the book before it was finalized.
The book starts with an introduction of the testing pyramid and it's levels: UI, integration and unit tests. The rest of part one goes on to break these levels down, explaining how to test at each level and the advantages and disadvantages of doing so. These explanations are interspersed with explanations of web technologies and the web in general which is great if you are unfamiliar with these things and are easy to skip if you are familiar with them. Part one ends with a great section on how to apply the test pyramid, the commonly seen inverse pyramid and how to deal with flakey tests.
Part two goes into more detail starting with a brief introduction to development for those readers without a background in development. This is followed by a chapter on how to organise your tests which is more important than you'd think (ever had to find the test that proves that X works when there's a large suite of tests?). The next chapter, called Effective Mocking, is my personal favourite and not only explains mocking but how it relates to coupling in your tests and how best to manage that coupling. The book finishes up with a chapter on writing tests first and the test-code-refactor cycle of TDD.
As I said at the start of the review this book is not just aimed at developers but instead carefully balances the concerns of both developers and testers. This not only broadens the books appeal but gives some insight into how "the other side" thinks about the topics covered.