Using Docker in test automation
summary
System describes recovering a crashed build node that used to take two weeks to restore and contrasts that with having regular backups that cut recovery to a day. Shows replacing hundreds of handcrafted Windows VMs and a 10‑hour, 20,000‑test bottleneck with Docker containers that spin up in 30 seconds to a minute, run Selenium nodes from Dockerfiles, use docker‑compose for multi‑service stacks, integrate Jenkins + GitHub via a Docker CI workflow, and runs 11 teams on four Linux nodes (4 CPU, 16 GB).
AI-written summary · about
chapters (8)
- 0:00Start
- 0:47Design Patterns for Selenium
- 1:33Motivation
- 7:06Practice Disaster Recovery
- 9:55Introduction to a Docker File
- 10:43Dr Selenium Project
- 20:19Docker for Windows
- 22:12Docker Compose
related talks
49mIn Silicon Valley, Engineers Deploy-and-Tell: Stories About Dockerizing an Application
24mFrom Zero to a Full Docker Based IT Teams
30mUsing Docker & Compose to Simplify Integration Testing
42mUse Docker to test microservices
54mUsing Docker in CI
13mBuilding reproducible dev environments with Docker
45mDev and Test Agility for your Database with Docker
01h 18mEmbracing Docker simplicity - while harnessing platform power