"When I’m writing a program for the first time, I almost never worry about test coverage early on; instead I worry about setting up infrastructure that lets me cheaply capture any bugs I do find as test cases, and rely on later testing to increase coverage."
Really interesting article from Nelson Elhage who presents a software engineer's point of view on improving coverage over time by using feedback loops from testing. I like the idea.
"If you want fast, accurate assessments of the risks associated with promoting the latest release candidate to production, you need a new currency in testing: Risk coverage needs to replace test coverage."
I've studied computer science, so maths always gets me. Here Wolfgang Platz proves in a mathematical way why the risk-based testing method can give much more insights than simple test coverage. Nice equations and graphs, by the way!
I enjoyed this article by Keith Klain where he shares his experience of working with metrics during one of his consulting projects, highlighting what's wrong with attempts to measure quality, and what's important about having valid metrics.
Software testing is evolving, and so are the roles. Some go towards programming, some choose product. Most recently, Areti Panou has become a Product Owner and she shares her first impressions about the role and how it is coming from software testing background.
The second article from the management series by Angela Riggs — an aftermath of her tweet that went viral. This time, she wraps up the advice she got about culture. This is to all of those who manage people, and those who are managed, too. Everyone, I mean, read it!