I have pre-ordered the How Google Tests Software hoping that it would be as good as a read as How We Test Software at Microsoft. I have completed reading in a week and I didn’t see any common content. Both books talk about different things and How We Test Software at Microsoft is still my favorite. While How We Test Software at Microsoft identifies various formal techniques or approaches for testing, the How Google Tests Software is more about the Google perspective of quality assurance, how it is different and why they approached it that way. It has lots of interviews with the Google’s TD (Test Director), TM (Test Manager), TE’s (Test Engineer), SET’s (Software Engineer in Test) and SWE’s (Software Engineer). Anyways below are some of the key take aways
- Quality is everyone’s responsibility.
- Hiring practices should change so that resources with programming skills are hired.
- Automate wherever possible so that most of the resource time can be spent testing usability etc.
- Exploratory testing and crowd sourcing.
- Software can never be bug free so release often to limited user base for better feedback.
- Author tests in the language the application is written.
- Do not enforce enterprise wide standards as that would limit innovation. (But I believe this is only true for companies whose hiring practices makes sure that skilled resources are hired).
- Opportunity given to resources to work 20% of their time on the projects they are passionate about.
- Open rotation policy. Resource is free to move to any project within Google after 18 months.
- New hires encouraged to start with testing.
- And of course continuous integration.
My Country, My People (Jhansi Fort in 1857)