Tag: Michael Bolton
Page 1 of 1
Is “QA” too narrow?
Twice this week, with different people, I had a conversation about what to call the category of work that I’ve been focusing on lately around integrating automated tests into CI/CD pipelines and making releases as smooth and easy as possible. As part of the discussions, I floated the idea of it all being under the… Read more
If you didn’t test it, it doesn’t work
Gary Bernhardt has a great talk online from 2012 called Boundaries, about how design patterns influence, for better and worse, the testing that can be done. In particular he advocates a “core” and “shell” model, having many independent functional cores and one orchestrating shell around them. The idea is that each functional core can be… Read more
10,000+ synonyms for Quality Assurance
I recently had a conversation with my team about what we should call the status between when work is passed “code review” but not yet “done”. The one thing I didn’t want to call it was “In QA”. One of the developers on my team had another idea that I decided to run with: Let… Read more
The Greg Score: 12 Steps to Better Testing
Ok, I’ll admit right off the bat that this post is not going to give you 12 steps to better testing on a silver platter, but bear with me. A while back, I was trying to figure out a way for agile teams without a dedicated tester or QA expert on their team to recognize… Read more
Tests vs Checks and the complication of AI
There’s a lot to be made in testing literature of the differences between tests and checks. This seems to have been championed primarily by Michael Bolton and James Bach (with additional background information here), though it has not been without debate. I don’t have anything against the distinction such as it is, but I do think… Read more
Page 1 of 1