Facebook Twitter Pinterest <Einbetten>
  • Alle Preisangaben inkl. MwSt.
Auf Lager.
Verkauf und Versand durch Amazon. Geschenkverpackung verfügbar.
How We Test Software at M... ist in Ihrem Einkaufwagen hinzugefügt worden
Gebraucht: Sehr gut | Details
Verkauft von gerhoff
Zustand: Gebraucht: Sehr gut
Kommentar: unbenutzt, leichte Lager-/Transportspuren, Knick an der Ecke auf der Rückseite - Rechnung mit ausgew. MwSt.. - kostenloser Versand durch Amazon.de
Möchten Sie verkaufen?
Zur Rückseite klappen Zur Vorderseite klappen
Hörprobe Wird gespielt... Angehalten   Sie hören eine Hörprobe des Audible Hörbuch-Downloads.
Mehr erfahren
Alle 3 Bilder anzeigen

How We Test Software at Microsoft (PRO-best Practices) (Englisch) Taschenbuch – 10. Dezember 2008

Alle Formate und Ausgaben anzeigen Andere Formate und Ausgaben ausblenden
Neu ab Gebraucht ab
Kindle Edition
"Bitte wiederholen"
"Bitte wiederholen"
EUR 37,99
EUR 34,98 EUR 3,19
5 neu ab EUR 34,98 9 gebraucht ab EUR 3,19
click to open popover

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.

  • Apple
  • Android
  • Windows Phone

Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.

Jeder kann Kindle Bücher lesen — selbst ohne ein Kindle-Gerät — mit der KOSTENFREIEN Kindle App für Smartphones, Tablets und Computer.




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.



Es gibt noch keine Kundenrezensionen auf Amazon.de
5 Sterne
4 Sterne
3 Sterne
2 Sterne
1 Stern

Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)

Amazon.com: 4.2 von 5 Sternen 17 Rezensionen
1 von 3 Kunden fanden die folgende Rezension hilfreich
4.0 von 5 Sternen Highly recommended for all current and would-be testers. 24. Juli 2009
Von Joseph S. Strazzere - Veröffentlicht auf Amazon.com
Format: Taschenbuch Verifizierter Kauf
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.
41 von 54 Kunden fanden die folgende Rezension hilfreich
2.0 von 5 Sternen Beuacratic and vague, few examples of any real testing 5. April 2009
Von B. Madden - Veröffentlicht auf Amazon.com
Format: Taschenbuch Verifizierter Kauf
Spoiler Alert: Software is tested at Microsoft with mind-numbing bureaucracy and buzzwords.

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?
2 von 4 Kunden fanden die folgende Rezension hilfreich
4.0 von 5 Sternen Good book on Software Testing 6. Juni 2009
Von Amazon Customer - Veröffentlicht auf Amazon.com
Format: Taschenbuch
This book is one of my favorities on Software Testing. I would recommend this book to every one who wants get a fresh perspective on software testing/SQA. My best pick from the book is the chapter on "A practical approach to Test Case design", Authors have tremendously succeeded in explaining the principles with great real life examples in a very lucid style. Personally, it helped to improvize the test planning efforts at my work place and also to explain & emphasize the need for desigining "practical" test scenarios to my students. Chapter on "Test Automation" provides very good insights on how to take best advantage of automation tools. Book is neatly organized and will be a great reading for beginners and for experienced QA professionals as well.
3 von 3 Kunden fanden die folgende Rezension hilfreich
3.0 von 5 Sternen Great information and content but poor quality printing 30. Januar 2013
Von Mama Birdy 64 - Veröffentlicht auf Amazon.com
Format: Taschenbuch Verifizierter Kauf
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.
6 von 10 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen An outstanding resource for software testers 29. Januar 2009
Von Sally Foster - Veröffentlicht auf Amazon.com
Format: Taschenbuch
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.
Waren diese Rezensionen hilfreich? Wir wollen von Ihnen hören.