Paradigm Shifts

MetaAutomation challenges quality practitioners to three Paradigm Shifts...

Paradigm Shift 1: Data from driving and measuring the SUT is valuable.

The data of driving and measuring the system, and the results, are all valuable information to the business. Conventional practices sacrifice trust by ignoring or hiding this data, or simply dropping nearly all of it on the floor. MetaAutomation enables the shift towards preserving all this information with high trustworthiness, enabling compelling quality value within MetaAutomation, and improving complementary quality practices.

Paradigm Shift 2: Quality should be transparent to the larger team.

With the new transparency and trustworthiness that MetaAutomation enables, automation to drive the system for quality enables direct benefits to more than just the QA role. With all the product data preserved in structured form, it is available to do some powerful and role-appropriate things for anybody on the team who cares about quality, especially for devs, leads, manual test role and QA itself.

Paradigm Shift 3: Dependency and tier relationships must be verified early.

Every year, applications are more interconnected, and the quality risk of isolating a system from dependencies grows. Conventional quality practices often hide the larger ecosystem for automation speed and stability, but with MetaAutomation, this is no longer needed; speed is optimized, and stability issues are cleverly mitigated. Any check can do actions and make measurements on multiple tiers. Reports include trustworthy details from all dependencies and all tiers and present to everybody on the team with clarity and trustworthiness, from business-facing layers to technology-facing ones.

Sign up here for emails with bites of wisdom on quality automation and MetaAutomation

Recent Blog Posts

  • The differences: Manual Test vs. quality automation

    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

  • The two halves of quality automation

    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

  • Fixing the false negative problem

    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

  • Fixing the false positive problem

    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