More thoughts from me on testing

I’ve been working on integrating a set of code scanning tools into our build system. Test code needs to be trustworthy – when test code fails, it should indicate a product failure. More importantly, when tests pass, they better indicate that the functionality under test works. One part of increasing quality is getting rid of…

Since last week, I’ve been to Helsinki and back – but still found a few things I think are interesting. This presentation on Increasing Engineering Tempo at Splice is all about accelerating the achievement of shippable quality. I’m reading Agile and Lean Program Management by Johanna Rothman – like her other books, it’s practical, easy…

Happy Friday everyone – read on for some potential interest… That’s all for this week, and that’s all for March 2024. Hope to see some of you (virtually) Wednesday night.

When I meet new people, they often ask, “what do you do?” The answer I give initially, and the one I hope to get away with is, “I work at Microsoft.” It rarely works. They inevitably follow up with, “what do you do there?” – which, for better or for worse is a much more…

In 2003, Brian Marick introduced the concept of “Agile Quadrants” to describe the scope of testing[1] (later expanded on by Lisa Crispin and Janet Gregory[2]). Several people (including me) have expanded and elaborated on the quadrants to describe the scope and activities of testing. Here’s a version of the testing quadrants. One challenge I’ve seen…

Once again – here are five things I found worth sharing this week. Steve Denning investigates The Hidden Heart Of 21st-Century Management Dawid Dylowicz wrote a fine blog post on what it’s like Joining A Startup As The First QA I’m sure you’re all aware of the recent malicious dependency issue that was blazing the internet. If…