Hello, today I’d like to share some useful books for QA Professionals. Grab your cup of coffee and take some notes and tips from this software testing books.
1 – Testing Computer Software, by Cem Kaner, Hung Q. Nguyen, Jack Falk
This is a book that should be read by all specialists, starting at the Junior level. The book can is a real classic. It is large in volume, written in a difficult language, but in no way outdated. It differs from others primarily in its attachment to the conditions of the real world, using the example of well-known Silicon Valley development companies. The authors thoroughly consider a wide range of issues: from the organization of the Quality Assurance process to the actual testing of documentation, code, projects, etc. If you are new to software testing, or have some experience, but no formal training, this book will provide you with the right way to approach software testing, and will give insights that would take years to learn on your own.
True, that missing in this book and not describe by authors the testing processes for agile development methods. Also it’s very difficult to focus on what it’s trying to say without being distracted/put off by the outdated examples However, in everything else, it is a real must read for every QA specialist.
2 – Testing Computer Software, by Lee Copeland
The book will be useful for QA specialists of various levels. The book is quite narrowly focused: it only talks about the design of tests and does not consider issues of planning and organization of the testing process. However, here you can find both new methods and an in-depth description of already known ones. So, for example, the book describes seven approaches to testing using the “black box” method and several “white box” methods. There is nothing superfluous here, only useful and practical examples with tables and diagrams, a clear description of techniques and additional tips. A big plus is the availability of conclusions and a list of other authors’ works on the topic under consideration. Recomended for preparing for professional certification.
The book gives the best account that I have found of pairwise testing, with or without using orthogonal arrays. It is very detailed, and has examples of where significant testing advantage has been gained by using this technique. The test coverage that can be achieved with well chosen pairwise test cases seems too good to be true. Copeland states that there also needs to be an element of tester prudence used, to augment the technique if necessary with some commonly occurring combinations that were not selected by the two tools that support the technique.
3 – How Google Tests Software, by James Whittaker, Jason Arbon, Jeff Carollo
Oriented more on Senior Engineers, this book will show how the best of the best QA Specialists conduct their testing. The book overviews the approach Google takes to testing software followed by chapters dedicated to the two test engineering roles at Google which are the Software Engineer in Test (SET) and Test Engineer (TE) roles and finally the Test Engineering Manager responsibility. Throughout the book there are sections and interviews from many other Googlers with the final chapter being dedicated to some of the thoughts on the direction of testing at Google.
Note that just because something works well at Google, doesn’t mean it will work well at some other company making some other type of product. Even Google could have made some different choices for some of their testing solution and have been equally successful.
4 – Lessons Learned in Software Testing, by Cem Kaner, James Bach, Bret Pettichord
The book is organized with lessons which are a paragraph to a couple pages long.
It’s a fabulous collection of tips and hints and techniques for both the new and the experienced person working in a software test department. It covers obvious areas testing techniques, automated testing (the material about what automated testing can’t do is very high grade material), documenting testing, and managing a test project.
Book starts with with the role a tester has. The next chapter relates to how to think as a tester. It provides interesting references in completely different knowledge areas which might help testers become better. Another chapter covers different testing techniques.
Also there are about writing bugs. Test automation and mention about documenting testing. As a logical conclusion from the focus on the role of tester.
The next three chapters relate to working with other persons.
5 – Agile Testing: A Practical Guide for Testers and Agile Teams, by Lisa Crispin and Janet Gregory
This book tells you about using Agile testing quadrants to figure out what testing is required, who can perform the testing, and what tools can aid in it.
Readers will come away from this book understanding
- How to get testers engaged in agile development
- Where testers and QA managers fit on an agile team
- What to look for when hiring an agile tester
- How to transition from a traditional cycle to agile development
- How to complete testing activities in short iterations
- How to use tests to successfully guide development
- How to overcome barriers to test automation