The Power of Atomic Automated Tests
summary
Talk claims clear, runnable practices: isolate tests so one failure pinpoints one feature, seed or update databases with SQL instead of slow snapshots, and bypass UI by setting cookies or localStorage after an auth API call. It gives tool-level examples—Selenium, Postgres, Java, CI on Amazon—and surprising scale numbers: 7,500 Selenium tests in 40 minutes, 2,500 tests in two hours via 30 parallel runners. It shows concrete scripts: fast CSV import for static data, API-created fixtures, and SQL toggles to verify accounts.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:31Atomic automated tests
- 2:36Efficiency in automation
- 5:46Benefits of atomic tests
- 8:01Atomic vs non-atomic examples
- 10:11Parallel execution importance
- 13:23CI quick feedback
- 15:33Parallel execution requirements
- 17:20Test data management
- 19:50Database seeding
- 25:37JavaScript UI automation
- 29:14API test data prep
- 31:19Converting UI tests
- 36:21Summary
related talks
26mThe Power of Atomic Automated Tests: Our experience of Improved Test Efficiency...
21mThe Essential Pillars of Automation Testing for Success
23mAdaptive Testing
25mTest Craftsmanship: Clean code practices for Test Automation
47mThe Valley of Success
21mTest Kitchen: A Recipe for Good Tests
41mFunctional Tests (Selenium) in Practice
57mAdvanced Testing Techniques: Tips from the trenches