Practices of “test automation” drop the most quality knowledge on the floor. This problem brings opportunity costs for quality risk and for the software business: software flaws entering the code repository, wasted work by the QA role, automation that takes too long to run, inefficient managing of quality risk, rework for performance measurements, and effectively hiding quality information from team members who care about it but don’t have their fingers in the code every day. This talk presents multiple strategies to preserve and communicate quality knowledge and address each of these opportunity costs, with increasing levels of challenge and reward for the team. I will also show the quality automation view and how to persist and communicate all of the quality knowledge from driving and measuring the SUT using a familiar pattern, and how this enables the MetaAutomation pattern language approach towards shipping software faster, at higher quality, transparency, and trustworthiness.
February 25 @ 13:15
13:15 — 14:00 (45′)