Matt Griscom
Matt Griscom
Member for
7 years 7 monthsMatt Griscom has 30 years’ 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. The MetaAutomation blog started in 2011, but Matt published his 3rd edition book on the topic in September 2018.
Company
MetaAutomation
Job Function
General Management
Job Title
Principal
Industry
Computer Software - SaaS
Interests
Architecture
Business Analysis
DevOps
IT Operations
Leadership
Quality Assurance
Test Automation
Country
United States
All Articles by Matt Griscom
All Stories by Matt Griscom
|
Improving Product Quality throughout the Software Development LifecycleGood, 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 AutomationWhat 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 ChecksImagine 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 RespectThe 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 AstrayThe 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. |