How avoiding SQL migrations in tests sped up a Go test suite by 2x

Summary

The article discusses a performance optimization technique for test suites that require pristine databases. The author explains how running SQL migrations at the start of each test is extremely CPU-intensive, especially when thousands of migrations have accumulated over time. By restructuring tests to avoid re-running migrations for every test case, the author achieved a 2x speedup in the test suite. The approach involves setting up the database schema once and then resetting only the data between tests, rather than reapplying all migrations from scratch.