How We Test Software at Microsoft

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.

This book was good but it obviously focuses on technologies that are specific to Microsoft. In my case I thought it was a great book since most of the things I work on are Microsoft so no major loss there. I do recommend it for those that work with .NET technologies and are wanting to look into testing and all the tools and practices that Microsoft has made available.

I would recommend this book not only for testers, but anyone involved somehow on development process. For managers, would help them to realize their own mistakes and compromises towards a decent final product and for developers, their own piece of guilty on the Q & A process. It is not a "Microsoft book" sharing only "appraisals" to Microsoft itself, but good on identifying several parts of the Q & A process. A good start if you want to stop creating "software on demand", like a fast foode counter order.

I have been a software tester, SDET, for over ten years, and while I stay current with the industry via books and websites, I learned a long time ago that software testing books rarely reflect the real world of software testing. It is a fact that testing comes in later in a software release cycle, and more often then not, well after the decision making. We start out at the wrong end of the problem, so to speak, and end up telling people too late, about issues that should have been addressed much earlier in the release cycle. I get tried of the standard solution to this problem that is presented in most test books and websites, which is `prove the approach doesn't work'. That is inevitability met with the response of upper management, 'keep the quality, but cut the test effort'. (Shoot the messenger) This book isn't going to waste your time with superficial solutions, or perfect world scenarios, this book is written from the trenches. I spent the first day reading it, nodding my head, and at times yelling "yes, that's it EXACTLY". The writers are drawing from experience, they understand testing software, and more importantly, they understand how to position a tester, and a test team, for success. This book goes far beyond Kaner's "Testing Computer Software", and is a must for any software tester who is passionate about shipping quality products.

Great insight into software testing, with a nice balance of stories, process, and test techniques. I now work at Microsoft as an SDET, after many years testing and developing at other software companies, but was still was eagerly awaiting this book. I'm fascinated by how testers learn their craft, how testing balances the pragmatic and theoretical, and how testers grow in their career. This book covered all that, as well as providing an insight into testing at Microsoft. For software testers, or anyone interested in software development, this book joins other books I'd recommend, including A Practitioner's Guide to Software Test Design, Testing Computer Software, How to Break Software, and (for security) Hunting Security Bugs.