This book is for everyone who needs to test the web. As a tester, you'll automate your tests. As a developer, you'll build more robust solutions. And as a team, you'll gain a vocabulary and a means to coordinate how to write and organize automated tests for the web. Follow the testing pyramid and level up your skills in user interface testing, integration testing, and unit testing. Your new skills will free you up to do other, more important things while letting the computer do the one thing it's really good at: quickly running thousands of repetitive tasks.
This book shows you how to do three things:
How to write really good automated tests for the web.
How to pick and choose the right ones.
* How to explain, coordinate, and share your efforts with others.
If you're a traditional software tester who has never written an automated test before, this is the perfect book for getting started. Together, we'll go through everything you'll need to start writing your own tests.
If you're a developer, but haven't thought much about testing, this book will show you how to move fast without breaking stuff. You'll test RESTful web services and legacy systems, and see how to organize your tests.
And if you're a team lead, this is the Rosetta Stone you've been looking for. This book will help you bridge that testing gap between your developers and your testers by giving your team a model to discuss automated testing, and most importantly, to coordinate their efforts.
The Way of the Web Tester is packed with cartoons, graphics, best practices, war stories, plenty of humor, and hands-on tutorial exercises that will get you doing the right things, the right way.
Most helpful customer reviews
3 of 3 people found the following review helpful.
Loads of learning for every experience level!
By Lisa Crispin
There aren't many tech books I'd like to curl up with for a snowy weekend, but I definitely plan to spend some weekends with this book. Yes, it's "web test automation 101" and I've been automating web tests for a couple of decades, but I want to keep my skills up to date and build better habits, and I find this book does that so well.
_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!
2 of 2 people found the following review helpful.
An excellent guide to automated testing!
By P. Michael Holland
Anyone who works with software development in some form should read this book. Not only does it explain what and how to test but why we shouldn't try to test everything with UI or unit tests.
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.
2 of 2 people found the following review helpful.
See all 12 customer reviews...
Comprehensive, well explained, very useful for programmers and testers
By Matteo Vaccari
This is a very useful book; it will get programmers and testers up to speed with current thinking and practices of agile testing. One important topic that is discussed is the Testing Pyramid, invented by Mike Cohn. It is a model that helps you make sense of different kinds of tests you could write: from the tests that are closer to the user, to the tests that are closer to the code. The Pyramid reminds you that unit, integration and UI tests are useful in different ways, and have different strengths and weaknesses. All of this is discussed at length in the book.
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.