1 | Book Name | Author/s | Publication Date | Review | TeStars | Full Review | Main audience | Purchase |
---|---|---|---|---|---|---|---|---|
2 | A Practical Guide to Testing in DevOps | Katrina Clokie | 2017 | Good introduction for testers and non-testers to DevOps culture. As an introduction, it covers all testing points in the DevOps pipeline from dev to production. It gives a wide angle, but it doesn't give you enough information on how to start to test. | ✮✮✮✮ | http://bit.ly/2DiIz8A | Newbies | https://leanpub.com/testingindevops |
3 | Hands-On Mobile App Testing | Daniel Knott | 2015 | The book contains a lot of practical information on how to test mobile apps, challenges, best tools in the market, etc. The editing though coule be improved. | ✮✮✮✮ | Hebrew: http://bit.ly/2T9piMf | All levels | https://amzn.to/2NkTx4l |
4 | More Agile Testing | Lisa Crispin, Janet Gregory | 2014 | As the authors say, this book carries on where the first book, Agile Testing, left off. But it also updates with new developments on topics from the first book. Also very detailed, had good advice but not as good as the first one. | ✮✮✮ | All levels | https://amzn.to/2QJhBM7 | |
5 | Explore It! | Elisabeth Hendrickson | 2013 | Although the title is Explore It, most of the information can be used for any testing. The book goes into the details about testing itself, for example, State Testing, Variable testing and much more. The book also includes exercises and is recommended. | ✮✮✮✮ | Hebrew: http://bit.ly/2EDK96m | All levels | https://amzn.to/2MM0eqJ |
6 | How Google Tests Software | James A. Whittaker, Jason Arbon, Jeff Carollo | 2012 | Although the word 'agile' doesn't appear even once in the book, the book depicts Google's version of Agile. It is interesting to see how the giant test software. | ✮✮✮✮ | Hebrew: Part 1: http://bit.ly/2Acg0YN Part 2: http://bit.ly/2rTs8JD | Intermediate and senior | https://amzn.to/2QDmbvo |
7 | Agile Testing | Lisa Crispin, Janet Gregory | 2009 | Very comprehensive easy to read book about the testing process with much useful advice. This book covers much more than Agile testing and contains a lot of information about testing in general. | ✮✮✮✮✮ | Hebrew: http://bit.ly/2SfDoeJ | All levels | https://amzn.to/2Dj3cDE |
8 | Exploratory Software Testing | James A. Whittaker | 2009 | The author was a testing manager in Microsoft and Google, and have an exciting strategy and tactics for exploratory testing as was done successfully in Microsoft. | ✮✮✮✮ | Hebrew: http://bit.ly/2AdD6hv | Intermediate and senior | https://amzn.to/2NkDraR |
9 | Lessons Learned in Software Testing: A Context-Driven Approach | Cem Kaner, James Bach and Bret Pettichord | 2002 | Written by some of the best experts. The book is divided into separated lessons, most of them are very valuable. Eady to read with a lot of practical knowledge on many testing and test managing aspects. An old book, pre-agile with some things that have changed. For the intended reader, someone with experience, it will be easy to distinguish what is relevant. | ✮✮✮✮ | http://bit.ly/2NZgl4Y | Intermediate and senior | https://amzn.to/2q85JYe |
10 | How to Break Software - a practical guide to testing | James A. Whittaker | 2002 | I think the book has interesting information. Even today there aren’t many books that are so detailed about finding bugs. But there are cheat-sheets and heuristics that can be found in abundance on the internet. The book is outdated, and there are many other books and articles on the internet I would recommend to read before this one. | ✮✮ | http://bit.ly/2V8tVbh | All levels | https://www.amazon.com/How-Break-Software-Practical-Testing/dp/0201796198 |
11 | Perfect Software and other illusions about testing | Gerald M. Weinberg | 2011 | The author states in the preface that "most professional testers will know most of what's in this book". Agreed. So if not for professionals, how about beginners? I wouldn't run to purchase it. It is a tedious and repetative book, with long stories that are not always clear or could be understood easily if he would just say what he meant to. There are a few interesting ideas, but other books have so much more. Yes, Gerald is very appreciated, yes, James Bach recommends the book. I say - don't bother. Read Sally Foster's review on the book page in Amazon to get a deeper view. | ✮✮ | Bored beginners | https://www.amazon.com/Perfect-Software-Other-Illusions-Testing-ebook-dp-B004J4VVE2/dp/B004J4VVE2/ref=mt_kindle?_encoding=UTF8&me=&qid= | |
12 | The Little book of Testing Wisdom | "25 friends of EuroStar". including Michael Bolton, Paul Gerrand et al. | 2018 | I must confess - I didn't read it all. The book contains short articles (in small fonts) about various subjects. From the few I read, I felt they either say the obvious (share the final test report structure with the stakeholders) or rename something to sound more... interesting? (instead of doing a professional job, let's call it "practice") etc. Not saying it is a complete waste of time, but it is vs. other books on QA you can read. By the way, one of the articles is a shameless promotion to EuroStar. I think I paid for this book, but the profits went to a good purpose, glad about that. Also, calling yourself "wise" is a little presumptuous. Last: the QR code at the last page doesn't work. | ✮✮ | All levels | ||
13 | Software Quality Assurance: From Theory to Implementation | Daniel Galin | 2003 | This book is a very detailed and systematic description of Software Testing aspects as quality plans, SQA components life cycle, and more. Two major problems: 1. The text is a little captured in the author's imagination - for example, he knows ahead what the client will ask for, etc. You might say, well - he knows what to expect. OK, but here it is so detailed it almost stated the customer's private name and shirt color. To make it more general: it is not context-driven but best-practice. Or, in other words, as a person that works as a software tester since 1998, in enterprise companies as well as start-ups and all in the companies in the middle, I never encountered most of the described situations. 2. It is outdated. Although published in 2003, the word Agile is not mentioned at all (Agile Manifesto is from 2001), not Exploratory Testing. So it is not in correspondence with today's world of QA. It is well written, very deep, thinks of a lot of scenarios, and useless. | ✮✮ | All levels | https://www.amazon.com/gp/product/0201709457/ref=x_gr_w_bb_sin?ie=UTF8&tag=x_gr_w_bb_sin-20&linkCode=as2&camp=1789&creative=9325&creativeASIN=0201709457&SubscriptionId=1MGPYB6YW3HWK55XCGG2 |