The MetaAutomation blog is about applying automation to quality measurement, storage, and communication, in order to ship higher-quality software faster. Better transparency and communication across roles and geographies make happier teams, too!
Why “MetaAutomation?” The short answer is: I had to call the pattern language something.
The slightly longer answer is that it is about the quality automation space, and the “meta” is about looking … more
I start with a definition: quality automation is the problem space between driving and measuring the SUT on the technology-facing side, and information the people and processes of the business on the … more
Test cases have served teams well as a tool to enable measures of quality over time, over many runs of those test cases, so the team knows (or should) roughly whether quality is getting better, worse, … more
Last month I posted here about the false positive problem.
Here is a specific example that I learned from a friend at Microsoft, where the false positive caused a defect escape:
Imagine a shopping … more
Manual test is when a person does the actions and observations and decides whether some aspect of SUT behavior is reportable as a bug (or, other action item). This is true whether or not the tester … more
In my last post I describe out the two kinds of automation that fit in the quality automation space.
People who do quality automation (at least, the part of quality automation that drives and … more
Quality automation is the domain (or problem space) of driving the SUT, measuring and recording data on SUT behavior and communicating that data to the business. I also use “quality automation” to … more
False negatives happen when these three things happen in order:
Operations (ops) promotes the software to the next level, or ships it to end-users
Someone (or, some automated process) discovers a … more
With all the quality automation that is your responsibility, a run of a check failed. It is your job to check it out.
After 30 minutes or so of investigation, you find that the failure happened … more
Last week I contributed at the annual global patterns conference, aka Pattern Languages of Problems or PLoP.
The site is here https://www.hillside.net/plop/2018/
We met this year in Portland Oregon. … more