There are many books about software testing, but Quality Code is among the best that I have read. It presents a philosophy about software testing that has been mine in my previous life as a software developer: the programmer is the main person responsible for the quality of its code.
Software Testing Books: Load Testing, Unit Testing, Functional Testing
Acceptance tests are defined in this book as the test created by the customer in collaboration with the developer and the tester prior to implementation. They are not the traditional user acceptance tests performed after implementation. Although acceptance tests can be used at different development stages, Ken Pugh proposes mainly in this book an approach where all project stakeholders will collaborate to create tests that validate business requirements.
The “More Agile Testing” book is the sequel to the book Agile Testing written by Janet Gregory and Lisa Crispin. This book continues to explore the topic of software testing in an Agile context.
Apache JMeter is an open source load and performance testing tool developed by the Apache Foundation that has become a major asset in software testing, being also used as a solution for many online commercial load testing services. The book “Master Apache JMeter From load testing to DevOps” provides an impressive amount of knowledge on how to successfully use JMeter, from your first steps with the tool to its integration in a DevOps approach.
In his preface of the book “Common System and Software Testing Pitfalls”, Donald G. Firesmith writes “You can think of this book as a catalog and repository of testing antipatterns: the pitfalls to avoid, how to mitigate their negative consequences if you can’t avoid them, and how to escape from them once you’ve fallen in. Like a naturalist’s field guide to wild animals, let this be your guidebook to the dangerous world of testing mistakes and its denizens – the many creative ways people have discovered to botch testing.”
Like many Agile approaches, the principles of Test-Driven-Development (TDD) and its Red-Green-Refactor cycle seem deceptively simple. As often, things are more complicated in practice and this is why Jason Gorman wrote a 200 pages book about TDD that explores the multiples dimensions of this approach.
A Coach’s Guide to Agile Testing is part of the nice series proposed to Agile coaches by Samantha Laing and Karen Greaves. This book provides a complete plan to run a workshop where members of a Scrum team can understand and learn the concepts behind Agile Testing.