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 at the bigger picture to define where the value is… and then going to get it.
Why a pattern language? Isn’t that kind of complicated?
The structure of a pattern language helps simplify by breaking the problem (how to measure and deliver comprehensive knowledge on behavior of the SUT, fast) down into smaller problems. It also puts each of those problems and the solutions into simple relationships with each other.
Why quality automation? Didn’t “test automation” work just fine?
No, test automation never worked very well and I write about this extensively elsewhere and in my book, but the problem here is that it didn’t describe anything about how to deliver the knowledge to the business. “Test automation” was just about describing value to what the test/QA role can do for measuring quality with automation, not communicating it.
The page here shows the MetaAutomation pattern map.
The four First Principles are here.