Dave talks with Justin Collier, Vice President of Product Management at SmartBear, about the need for AI testing to mature, to keep pace with AI-generated code. About 69% of surveyed U.S. software experts said AI writes or accelerates at least 41% of their code, while only about 46% validate specifications before AI generates code.

Code coverage remains important, but it is not sufficient by itself. Teams should identify critical tests early and target tests to changed code and release risks, since running every regression test may not keep pace with frequent changes.

AI-generated tests need to verify software intent and should not simply let AI grade its own work. Teams need traceable records of test authorship and execution, release decisions, changes, and the rationale for shipping or holding software.

In this episode, Dave speaks with Christian Bremeau, founder and CEO of Meta Integration as a nearly 30-year-old metadata technology provider whose components support lineage and metadata harvesting across data integration, catalog, modeling, and BI products.

Version 12 is now generally available after nearly two years of development and about six months of pre-release deployment. It includes multiple MCP servers, AI-assisted metadata search and question-answering, and the MetaKarta product brand.

Semantic Hub

• The Semantic Hub reuses existing BI metrics, KPIs, lineage, and semantic models to provide context for AI rather than requiring organizations to start from scratch.
• It compiles governed definitions into database semantic or metric views and BI tools including Tableau and Power BI, enabling AI agents and BI users to receive the same answers.
• Christian emphasized deterministic SQL generation from compiled semantic models instead of relying on AI to generate SQL at runtime, reducing AI cost and hallucination risk.

Dave discusses npm version 12’s decision to disable lifecycle scripts by default to improve security while potentially shifting malicious-package execution from installation time to runtime. Joining him is Darren Meyer , security leader at Checkmarx. Darren explained that lifecycle scripts, including post-install scripts, have been a common way for attackers to execute malicious code in development environments. With scripts disabled by default, attackers may move deployment and infection code into module-loading behavior, such as execution during require or import. The change is a useful barrier, but it does not eliminate the underlying threat.