Tag Archives: QA

May QASIG Meeting

MetaAutomation presented by: Matt Griscom

See Matt’s book on Amazon.com

Regression testing automation provides an important measure of product quality and can keep the quality moving forward.  Unfortunately, automation can take a long time to run, and automation failures generally must be debugged and triaged by the test automation team before any action item can be considered or communicated to the broader team.  The resulting time lag and uncertainty greatly reduces the value of the automation, and increases time cost and quality risk.

MetaAutomation is a language of five patterns that provides guidance to new and existing automation efforts, supplies fast and reliable regression testing of expected business behavior for a software solution, speeds quality communication around the team, and reduces latency and resource cost.

The five patterns, Atomic Check, User Pool, Parallel Run, Smart Retry and Automated Triage, form a sequence, representing an order in which the patterns would apply, and a network of dependencies from the more dependent to the less dependent patterns.

For an existing automation project, the least dependent pattern, Atomic Check, can be applied in whole or in part to run the automation faster and create results that are more actionable.  If enough of Atomic Check is followed, the dependent patterns can then be applied to further speed, direct and enhance the value of communications resulting from the automation.

About our speaker:  Matt Griscom has 20 years’ experience creating software including test automation, harnesses and frameworks.  Two degrees in physics primed him to seek the big picture in any setting.  This comprehensive vision periodically puts Matt in the vanguard.  Matt loves helping people solve problems with computers and IT.

March 2015 QASIG Meeting

Low-Tech Acceptance Test Driven Development
Presented by Kevin Klinemeier

“The customer does not like what we made this week” is a bigger problem than “The customer does not like what we made this morning”. But the natural inclination of programmers is to program until they are out of one of the following: time, features, or food and water. Much of the Acceptance Test Driven Development (ATDD) literature talks about tools for automation, for example Cucumber, Robot Framework, or RSpec. These tools can be a means to an end, but are not required and may be more of a hindrance than help especially when a team is just starting ATDD.

This low-tech ATDD approach is especially applicable to two kinds of transitions a team may be in. The first are those who are taking the first steps to moving away from a big-handoff approach and toward a continuous testing approach. The second are teams that are attempting to work more closely with their business stakeholders. Generally, this approach is useable for both legacy projects as well as new-development. It is appropriate in both the Scrum and Lean paradigms, making no assumptions about when the planning takes place.

About our speaker: Kevin Klinemeier has almost 20 years of software development experience as developer, team lead, software architect, and agile technical consultant. As a consultant, he has used this approach with teams as small as three to as large as twenty. He has worked in industries including telecommunications, global logistics, healthcare, and finance.