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

  • A gift to company executives

    For automation for quality (a superset of/fix for what is often called “test automation”) MetaAutomation provides trustworthy detail and transparency on what the SUT is doing and how fast to all … more

  • Ruby has lost its sparkle

    Ruby is very popular as an automation tool.

    Ruby’s creator, Yukihiro Matsumoto, had what seemed like great ideas: programmer productivity and fun, and that (to quote Wikipedia, quoting Matsumoto)

    “ … more

  • Make your automation sit up and pay attention

    One of the problems with the phrase “test automation” is that it implies that what a manual tester can do can also be automated, and even that it is automated when someone automates a manual test … more

  • The limits of AI testing

    Artificial intelligence (AI, or more accurately called machine learning) is all over public discussions about software testing. It seems like the next big thing! Many imply that it will take over the … more