- Taschenbuch: 446 Seiten
- Verlag: Microsoft Press; Auflage: 01 (10. Dezember 2008)
- Sprache: Englisch
- ISBN-10: 0735624259
- ISBN-13: 978-0735624252
- Größe und/oder Gewicht: 18,5 x 2,8 x 22,9 cm
- Durchschnittliche Kundenbewertung: Schreiben Sie die erste Bewertung
- Amazon Bestseller-Rang: Nr. 158.843 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
How We Test Software at Microsoft (PRO-best Practices) (Englisch) Taschenbuch – 10. Dezember 2008
|Neu ab||Gebraucht ab|
Kunden, die diesen Artikel gekauft haben, kauften auch
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Discover how Microsoft implements and manages the software-testing process company-wide with guidance and insights direct from its test managers. Organizing any testing program the people, processes, and tools can be challenging and resource intensive. Even when the necessary tradeoffs are made, no development team can test every scenario. This book explains how a worldwide leader in software, services, and solutions staffed with 8,000 testers implements and manages its testing process effectively company-wide. Whether you re a tester or test manager, you ll gain expert insights on effective testing techniques and methodologies including pros and cons of various approaches. To add interesting context, the book also shares such facts as the number of test machines at Microsoft, how the company uses automated test cases, and bug statistics. It answers key testing questions, such as who tests what, when, and with what tools. And it describes how test teams are organized, when and how testing gets automated, testing tools, and feedback with illuminating insights for software-development organizations of all kinds.
Über den Autor und weitere Mitwirkende
Alan Page is Director of Test Excellence where he oversees technical training and provides consulting for Microsoft testers. He's one of Microsoft's first Test Architects and has worked on various versions of Windows and Windows CE.
Ken Johnstonis Group Manager for the Microsoft Office Internet Platform and Operations team. He is a former Test Lead, Test Manager, and Director of Test Excellence.
Bj Rollison is a Test Architect on the Engineering Excellence team. Rollison worked on numerous product releases and later became Director of Test. He s also a trade-journal writer and conference speaker, and teaches testing at the university level."
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
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.
I understand this is a "how we do testing a Microsoft" book, but I at least expected a few real code samples, unit tests, test automation scripts, or test plan samples. Instead, code samples were obviously simple functions thrown together by the author, and in-depth testing samples are nowhere to be found.
Instead, this book mostly comes off as an HR manual. MS's testing career path is documented in agonizing detail, and the author tries too hard to suck up to his bosses. Seriously, he actually tells the reader to search for Steve Balmer speeches on Live.com to become inspired.
Once they actually start talking about testing, it is incredibly vague and buzzword laden. There are a few good pieces of advice here, but nothing you won't find in a far better book.
The key question of how software is tested at MS is never really answered. For example:
1. Linux maintainers use Coverity on the Linux Kernel. Does MS use such tools on their Kernel?
2. What sort of scripting languages are used for automation testing of Office or Windows or any other MS product?
3. What sort of Unit Testing software do MS developers use? CppUnit? NUnit? The Unit testing feature in VS2008? What do some of these unit tests look like?
4. What does the typical test plan at MS look like?
5. What sort of white-box testing do developers perform? There are a few vague references to unit testing, but what about performance and coverage testing? What specific tools do they use? What do their result reports look like?
After reading this book, I'm hard pressed to answer any of these.
I would strongly advise people new to testing to avoid this book; otherwise they will be discouraged. Testing can actually be fun and interesting--this book is not.
P.S., I notice the high reviews of this book are from Microsoft employees. Conflict of interest, anyone?
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.