How to Optimize Automated Testing with Everyone's Favorite Butler
summary
Shows how Jenkins plus tooling and conventions trim test noise: use naming conventions and mirror test code to application components so subsets run independently; label tests for team/use case and post-process results (FitNesse, Cucumber, JMeter, Gatling examples). Advocate radical parallelization via throwaway VMs/containers, Jenkins Job DSL / Workflow / MultiJob and copy-artifact fingerprinting to keep runs consistent. Targets faster feedback (aim ~30 minutes), avoids running 50,000+ suites every commit, and treats flaky tests and 800-result security scans as distinct analysis problems.
AI-written summary · about
chapters (34)
- 0:00Introduction
- 2:23Agenda
- 3:30Me Me Me
- 4:10Labs
- 10:12Safety Net
- 10:24Manual Testing
- 14:02Challenges
- 16:44Which subset of tests matter
- 18:24Jenkins User Conference
- 18:38Butler Stretch
- 19:18Speed only is risky
- 20:49CD is not just execution
- 21:23Homework
- 21:50Testing tiers
- 22:48Integration
- 27:01Slicing and Dicing
- 28:23Radical Parallelization
- 31:49Keeping it manageable
- 33:51Whats next
- 34:09Jenkins Tilt the Pyramid
- 34:32Start Simple
- 36:23Keep Jenkins Jobs Simple
- 38:26Unit Tests
- 39:09Environments
- 39:51Test Setup
- 40:11Test Drops
- 40:40Jenkins Workflow View
- 41:16No Go Decisions
- 42:11Executing Tests
- 43:23The Ultimate Question
- 43:49Quick Examples
- 44:52Pipeline
- 46:11Homebrew
- 47:59Summary
related talks
21mScaling Test Automation: Building Reusability for 10x Speed and Efficiency
23mAdaptive Testing
42mUse testing to Develop Better Software Faster
46mA Practical Guide to Testing in DevOps
47mThe Valley of Success
33mIntentional and Unintentional Compromises in Test Automation
37mSo You're Automated...Now Let's Make It Fast!
41mContinuous Integration Tips & Tricks