Test Automation – Get the BEAM into an Organization
summary
Argues that test automation is the practical on‑ramp for BEAM adoption by showing a telecom case where common_test and Erlang replace a fractured C and Ruby test stack, wired into Jenkins CI to produce daily automated runs. It takes about 3 months to standardize hardware, automate builds and land initial coverage; subsequent iterations add hardware variants, swap Ruby tests to Erlang in weeks per developer, improve observability and lead to BEAM being chosen for new control logic.
AI-written summary · about
chapters (8)
- 0:00Test automation intro
- 3:55Why test automation
- 7:50Underserved value
- 9:13Systems that benefit
- 11:22Legacy telecom case study
- 19:53BEAM adoption outcomes
- 21:20Where to apply BEAM
- 23:45Summary
related talks
55mShifting the Testing Role Pendulum
46mSoftware Devs in Test Automation - Dream or Reality in Agile Software Dev?
32mWhy testing is a developer's problem
38mDo We Really Need A Test Automation Engineer?
45m12 years supporting Software Architecture teaching with BEAMs
49mHow to Optimize Automated Testing with Everyone's Favorite Butler
19mBusiness Impact Delivery Using Test Automation
15mThe Tester I Was and the Tester I Could Be