The most complete book review of all time

After my presentation at PNSQC in October, I was giving away copies of How We Test Software at Microsoft, and Michael Larsen said that if I gave him a copy, he’d review it on his blog. I figured that was better than giving it to someone to sell on ebay, so I took a shot.

Michael responded with the most in depth multi-part book review ever. Seriously, it was pretty cool, and I owe Michael a copy of my next book (which I plan to start writing sometime in 2027).

If you missed it and want a nice recap of the book, here’s the full review index.

Chapter 1: Software Engineering at Microsoft

Chapter 2: Software Test Engineers at Microsoft

Chapter 3: Engineering Life Cycles

Chapter 4: A Practical Approach to Test Case Design

Chapter 5: Functional Testing Techniques

Chapter 6: Structural Testing Techniques

Chapter 7: Analyzing Risk with Code Complexity

Chapter 8: Model-Based Testing

Chapter 9: Managing Bugs and Test Cases

Chapter 10: Test Automation

Chapter 11: Non-Functional Testing

Chapter 12: Other Tools

Chapter 13: Customer Feedback Systems

Chapter 14: Testing Software Plus Services

Chapter 15: Solving Tomorrow’s Problems Today

Chapter 16: Building the Future

Afterward

Thanks again to Michael for the in-depth write up. I expect that anyone wanting the short version of hwtsam will be greatly appreciative.

Similar Posts

  • The Rise of the Customer

    I spoke recently on the topic of “Customer Focused Test Design” (synopsis: customers don’t really care how much functional testing testers do, or how many bugs they find. A test approach that favors scenarios, -ilities, and customer feedback is better; and a bunch of examples for emphasis/proof). Part of the approach I suggest (and have…

  • Ur doin it rong

    I’d like to offer a bit of advice for everyone in the world (but especially to software testers). In just about every thing you do, every day of your life, it is possible to do something wrong. My challenge to you is to think deeply about how you can do things “right”. Some examples: If…

  • |

    Five for Friday – December 8

    It’s the FfF Moscow edition (I’m here for the Heisenbug conference. As I approach my one year mark at Unity (and hopefully established a small bit of credibility), I’m beginning to push a bit harder on some topics. I’m reminded of this quote from Colin Powell, who says, “…leadership is sometimes about being willing to…

  • Oh the tests I’ll run

    Last week, Katrina Clokie (@katrina_tester) asked this question on twitter:   Has anyone dynamically ordered automated checks so that those most likely to fail are executed first, then the build can fail fast? — Katrina Clokie (@katrina_tester) February 24, 2017 I gave a few abbreviated answers based on my experience, and promised to write up…

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.