- Author: [[James A. Whittaker, Jason Arbon, Jeff Carollo]] - Full Title: How Google Tests Software - Tags:: books [[inbox]] - ![](https://images-na.ssl-images-amazon.com/images/I/41Y8zQUls9L._SL400_.jpg) - ### Highlights first synced by [[Readwise]] [[2020-09-03]] - Google often builds the “minimum useful product” as an initial version and then quickly iterates successive versions allowing for internal and user feedback and careful consideration of quality with every small step. Products proceed through canary, development, testing, beta, and release channels before making it to users. ([Location 637](https://readwise.io/to_kindle?action=open&asin=B007MQLMF2&location=637)) - The ongoing effort to automate to within the “last inch of the human mind” is currently the design spec for the next generation of test-engineering tools Google builds. ([Location 715](https://readwise.io/to_kindle?action=open&asin=B007MQLMF2&location=715))