Taking CI and automated testing seriously
summary
Continuous integration for C++ game code uses a custom build monitor and a 35‑machine in‑office farm because a single Serious Sam build is ~20 GB and a head sync can be ~200 GB, and cloud options choke. Unit framework yields 80,000 unit tests but covers under 5% of code; functionality relies on record‑and‑replay bots that fast‑forward a 250‑hour run into 20 minutes and produce 15,000 hours of human testing equivalent. Artifacts stay machine‑local and an in‑game pin reporter captures reproducible bug context.
AI-written summary · about
chapters (9)
- 0:00Introduction to Croteam
- 5:26CI in game development
- 8:46Unit testing challenges
- 11:42Build monitor and infrastructure
- 15:34Functionality testing with bots
- 18:18Efficiency and fast-forward testing
- 20:30Bug reporting workflow
- 23:56Conclusion and game trailer
- 25:21Q&A session
related talks
56mAI Infrastructure as Part of CI/CD for Mobile Game Development
20mCI/CD Infrastructure for Efficient Mobile Game Development
40mAutomated Testing at Scale in Sea of Thieves
35mGame Development Infrastructure
59mMaking Testing C++ Binaries Practical @ Facebook Scale: A CI Story
30mA Deep Dive into a Cross-Platform Build Farm
01h 20mContinuous Integration for Large Scale C/C++ Projects With Conan2
43mEffective CI/CD for Large Systems