How Google Tests Software

O livro tinha duas pontas com as folhas ligeiramente dobradas.

I wish my company had the same approach towards test automation! Very good book that inspires and shows that 'it can bo done'! Many practical examples of how testers work, what problems they solve and how their job contribute to the quality improvement policy.

It is so exciting being part of an industry that is rapidly changing and won't be the same in 5 years or 10 years. Change means opportunity...opportunity not just to "fix" the pervasive misconceptions of what test is and how it should be done, but opportunity to cross into uncharted territory and come up with solutions that no one has ever tried before. That particular point - the idea of the future of test being open and uncharted - is incredibly cool. The book promotes ideas that are radical now but that eventually will become the norm - or they will be tossed as failures and replaced with something better. But the point is that opening up the discussion gives people license to think and experiment, to implement new things that could become great successes or massive failures. Either way, it's a step in the right direction, because test needs a lot of experimentation and empirical thinking right now to go from where it is to where it could be. I enjoyed the practicality of the book - it provided examples of real issues and how they were approached and solved, or not solved. I also enjoyed the lack of dogmatic "this is the only way to do it" mentality. I felt reading it that the authors were simply opening up and sharing, and that if someone was to come up with a great new idea to try, they'd give it a shake. Great pioneers and scientists care only about progress in their field, not about who gets the glory for the progress, and I felt like that's what this book was after - progress. Great book to get you thinking and learning, and where there are gaps or open-ended questions, this is the territory for opportunity.

Written by Googlers for new Googlers -- This disclaimer needs to be stamped on the book cover. I wasn't a big fan of this book. The forward and intro started very strong. I was elated with the little bit in the beginning that talks about good "Code Hygene", but then there's the admission that Google uses this book for "Noogler orientation" (why is this not noted on the book synopsis?), and the last half of the book is padded with several interviews with Googlers that just seemed to add more opinion than fact at the back of the book. Fluff. Lots of it. It's not all bad though. If you are working at the scale of Google, this book explains the org chart and relationship of SWE, SET, TE, TEM's. I found this interesting (the first couple chapters), but I'm working with teams of 20, not 200! As a long-time developer already performing automated testing, there was nothing in this book that I can take and apply in my daily work.

Quite interesting for anyone involved in SQA activities, at any level, from technical to management and business. And on top of that, it's easy reading...