How to Manage Your Test Data for Successful Test Automation
summary
Compares concrete methods for preparing test data for automated tests: creating data through the UI versus calling APIs with Swagger-generated clients, inserting directly into databases using DbUnit or SQL scripts, or shipping prebuilt snapshots as Docker images in an artifact registry for fast environment resets. Covers practical techniques and pitfalls such as using Redis counters for unique names, background pools that precreate users, cache-invalidation issues, and Liquibase migration hooks, and presents speed tradeoffs with parallel preparation plus runnable tooling examples to evaluate what approach is worth adopting.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 3:46Test components
- 5:54Dependent tests
- 9:05UI data management
- 13:39UI testing pros/cons
- 17:51API test data
- 21:06API stability
- 23:54Direct DB control
- 27:03DB pros/cons
- 30:17DataSet basics
- 33:28DataSet for MongoDB
- 36:20DB dump management
- 40:16Docker with dumps
- 42:00Docker test data pool
- 44:45Live data testing
- 45:48Summary
related talks
44mBro, Manage Test Data Like a Pro!
29mManaging the Test Data Nightmare
29mManaging the Test Data Nightmare
49mManaging Testing Data
23mCreating data for Functional Tests with the Test Data Builder Pattern
47mTest Data Key to Effective Test Coverage
09mTechTalk "Preparing Data for Integration and E2E System Testing"
33mTest Automation in the Database: Unit Tests and Data Providers