Surviving the AI Code Tsunami [Testμ 2026]

At Testμ Conf 2026, Appsfactory Group QA Director Mathias Strziga presented an internal AI-driven development lifecycle built around roughly 82 skills, nine agents, and more than six workflows, arguing that as agents make code generation cheaper, specification and verification become the costlier and more important parts of delivery. His model replaces conventional sprints with heavily specified three-to-four-day “bursts” followed by verification, and separates build agents from independently derived QA challenge agents so their conclusions can converge without sharing assumptions prematurely. Central to the approach is treating every failed test as a classification problem rather than automatically as a bug: product, behavior, specification, test, infrastructure, and harness issues are reevaluated within the workflow, while unknown results stop the chain for human judgment. Validation is framed as checking intent through contracts that define the target, oracle, observations, and permitted actions, while event systems such as issue trackers and test tools help prevent repositories from overwhelming agents with irrelevant changes. Strziga argues that QA roles will shift away from lower-discretion tasks toward governance, learning, risk assessment, and accountable decisions, with humans occupying a “pilot” role, although the presentation provides no customer outcomes, defect-rate evidence, or detailed performance metrics to substantiate the framework’s impact.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.