lijadora reviewed How Google Tests Software
Review of 'How Google Tests Software' on 'Goodreads'
3 stars
Nice overview of the state of testing at Google 2011-ish. It also motivates the choices clearly.
I would have liked to see some context as well - what is expected of a product owner? How do features get shape? Why did the test engineer need to create a functional overview (shouldn't that be available already)? Probably givens for Googlers, but not for me.
Even with that in mind it is a useful book. I particularly liked the interviews with the people that actually performed the roles. Easy to read and clarifying concepts explained earlier.
I was curious about the last chapter (improving how Google tests software). I like the vision laid out there: testing as a separate discipline will disappear, to be replaced by quality embedded in the process of developing software. I doubt, though, whether every company can do what Google is doing with 'outsourcing' user facing test efforts …
Nice overview of the state of testing at Google 2011-ish. It also motivates the choices clearly.
I would have liked to see some context as well - what is expected of a product owner? How do features get shape? Why did the test engineer need to create a functional overview (shouldn't that be available already)? Probably givens for Googlers, but not for me.
Even with that in mind it is a useful book. I particularly liked the interviews with the people that actually performed the roles. Easy to read and clarifying concepts explained earlier.
I was curious about the last chapter (improving how Google tests software). I like the vision laid out there: testing as a separate discipline will disappear, to be replaced by quality embedded in the process of developing software. I doubt, though, whether every company can do what Google is doing with 'outsourcing' user facing test efforts to dog fooders, beta testers etc
