Runnable Sample Solutions with Reusable Code

There are three samples on GitHub repositories to demonstrate implementations of the Hierarchical Steps and Atomic Check patterns and how the revolutionary quality value that these deliver also enable the rest of the MetaAutomation pattern language.

In addition, there is a Visual Studio extension project that eases coding your checks in C# with the Hierarchical Steps pattern, and that works with any of the three samples.

These projects are downloadable with GitHub tools or as simple compressed files.

MetaAutomation Sample 1

This sample is very simple to build and run, and it illustrates valuable and sophisticated concepts for doing quality automation that, unlike conventional practices, does not drop most of the business value on the floor.

The solution includes instructions, detailed documents to help with modification and code reuse, and a tutorial.

The GitHub project for sample 1 is here.

MetaAutomation Sample 2

Sample 2 does everything that Sample 1 does, plus it enables checks to run across any number of processes.

For learning and using the code samples, it's recommended to start with Sample 1 and the included tutorial.

The GitHub project for sample 2 is here.

MetaAutomation Sample 3

Sample 3 does everything that Sample 2 does, plus it enables checks to run across any number of machines and processes. A single check can run across any number of tiers for IoT quality verifications!

For learning and using the code samples, I recommended starting with Sample 1 and the included tutorial.

The GitHub project for sample 3 is here.

Check Step Editor

This Visual Studio extension makes it very easy to work in C# with self-documenting hierarchical steps. It works with all the MetaAutomation samples, and is explicitly used with the tutorial that comes with Sample 1.

The GitHub project is here.

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