| Share this post! | Vote this! |
|
There is one question I get more than any other. Regardless of the country I am visiting or the conference I am attending, this one question never fails to surface. Even Nooglers ask it as soon as they emerge from new employee orientation: How does Google test software?
I am not sure how many times I answered that question, or even how many different versions I gave, but the answer kept evolving the longer I spent at Google and the more I learned about the nuances of our various testing practices. I had it in the back of my mind that I would write a book and when Alberto, who likes to threaten to turn testing books into adult diapers to give them a reason for existence, actually suggested I write such a book I knew it was going to happen.
Still, I waited. My first problem was that I was not the right person to write this book. There were many others who preceded me at Google and I wanted to give them a crack at writing it first. My second problem was that I as Test Director for Chrome and Chrome OS (a position now occupied by one of my former directs) I had insights into only a slice of the Google testing solution. There was so much more to Google testing that I needed to learn.
More...
0 comments:
Post a Comment