Creating data for Functional Tests with the Test Data Builder Pattern
summary
Argues that replacing brittle SQL fixtures with a Test Data Builder that calls real APIs or WebDriver eliminates schema maintenance, allows logical isolation via generated unique keys (MD5 or random), and returns created IDs for Selenium lookups. Builders chain to create whole entity graphs, factories provide version-specific families, and tests run concurrently — the team reports runs 8 tests concurrently in practice. Proven tradeoffs: no per-test cleanup, optional suite-level purge, and creates unique project IDs via the Test Data Builder pattern.
AI-written summary · about
chapters (4)
related talks
47mManaging Testing Data
49mManaging Testing Data
29mManaging the Test Data Nightmare
47mHow to Manage Your Test Data for Successful Test Automation
41mA Cookbook for Testing Data
47mTest Data Key to Effective Test Coverage
24mModernising J-Unit with Test Data Generators
44mBro, Manage Test Data Like a Pro!