Matt Griscom

Matt Griscom has twenty years of experience creating software including innovative test automation, harnesses, and frameworks. Two degrees in physics primed him to seek the big picture in any setting. This comprehensive vision and love of solving difficult and important problems led him to create the MetaAutomation pattern language to enable more effective software automation for quality measurement. He started his MetaAutomation blog in 2011, but in 2014 Matt published the ground-breaking and definitive description of the MetaAutomation pattern language in book form. Matt loves helping people solve problems with computers and IT. Email Matt at [email protected].

Connect with Me

All Stories by Matt Griscom

Improving Product Quality throughout the Software Development Lifecycle

Good, efficient communication is an important asset to the team. With focused, pure, and structured data on product quality, including all of the self-documenting steps of a given check, it’s clearly known what’s working and what the verifications are. Matt Griscom shows how you can get this level of clarity.

Handling a Check Failure in Test Automation

What happens on your team when a check (what some call “automated test”) fails? Regression tests or checks that are effective toward managing quality risk must be capable of sending action items outside the test/QA team quickly. How do you provide fast, trustworthy quality communications from your team?

Stronger, Faster Quality with Simple, Focused Checks

Imagine focusing on prioritized business requirements at the software layer closest to where those business items are implemented. Writing just one check—that is, a programmed verification—per business requirement makes for simple, focused checks, supporting stronger, faster quality around the team.

Test Automation Gets No Respect

The conventional approach to software automation for quality creates a losing situation for the people doing the work. When tests are reliable or take more time than first estimated, management and the rest of the team lose confidence. How can you produce consistently quick, quality information?

The Word “Automation” Has Led Us Astray

The misunderstanding that automation for software quality is just doing what humans do (i.e., manual testing), but faster and more often, causes business risk. Unless you’re very clear, the quality measure is incomplete. The word automation distracts from the real value: measuring quality.

TechWell Insights To Go

(* Required fields)

Get the latest stories delivered to your inbox every month.

Email *

Country *

Leave this field blank