Although test driven development can help document how code behaviors and facilitate engineering best practices, testing SQL is challenging. Although dbt enables developers to define assertions about the transformed data, most users run these tests on production data after the transformations are applied instead of on a dedicated test database. Michael Kaminsky describes why this approach is slow and describes the need for a tool that quickly generates useful and anonymized test data based on pathological examples from the production database.