Automation Lessons Learned
summary
Built internal tools like Windmill, Mausmo, Flex Pilot and prototypes Jellyfish and Sauce Builder, with Mausmo and Flex Pilot finding real use. Start automation grassroots on stable features, instrument the money path test first so payment failures alert immediately, require IDs and a simple API not an IDE, keep few moving parts and VMs, store tests in version control, split unit/UI tests by directory, make running tests a one-liner, track weekly stats showing bugs caught and dollars saved, celebrate wins and iterate.
AI-written summary · about
chapters (6)
- 0:00Start
- 2:40What Is the Best Way To Start an Automation Effort at My Organization
- 7:52Expectation Setting
- 12:43Community
- 14:09Tips
- 16:03Running Tests Must Be Trivial
related talks
38mScaling Automated Testing & Architecture from Startup to Enterprise
32mLiving on Crotches or UI Automation Antipatterns
36mLiving on crotches or UI Automation antipatterns
21mMindful Automation Testing Software Builds and Streamlining Processes
33mBuilding an Automated Test System from Scratch
52mHow to win with automation and influence people
37mSo You're Automated...Now Let's Make It Fast!
57mRise of the Machines - Automate Your Development
