This book is one of the best books i've ever read. it has lot of good information, not only related to Microsoft way of testing, but also general concepts and guidelines.

The print job is miss-aligned, there are graphics that cover text and you have to guess what they're trying to say. I am very surprised this made it past their QC checks.

In "How We Test Software at Microsoft", Alan Page, Ken Johnston, and Bj Rollison provide a terrific mix of insight into Microsoft, along with in-depth explanations of practical test processes.

From the introduction:

"This book is for anyone who is interested in the role of test at Microsoft or for those who want to know more about how Microsoft approaches testing. This book isn't a replacement for any of the numerous other great texts on software testing. Instead, it describes how Microsoft applies a number of testing techniques and methods of evaluation to improve our software."

I would also add that this book is for anyone who wants to learn some extremely useful, real-world approaches to both typical and complex testing situations.

This is a very good book - one I highly recommend to all current and would-be testers.

Delivered as promised. Holy Guacamole this is a boring book!

Good

Interesting if it's an introduction to the concept.

i like it

This book has given me new views of testing that I have not considered in the past. I would highly recommend this book to any software quality assurance professional that is just getting started and for those that want to learn something new. This book showed that my team was not testing in the most efficient manner and we have taken many suggestions from this book to improve our software testing strategies.

great

Worth a read, not worth the price. They talk about unnecessary stuff, just tell us how you test software at MS.

It certainly does what it says on the tin - it is a wealth of knowledge on how Microsoft test software. You can enjoy reading this without entirely agreeing with it (I personally disagree with having a separate SDET role, for example) - but that doesn't prevent the book being useful.