The evolution of a system integration test process
summary
Process evolution follows measurable changes: a 2-hour test window with focused cases yields only ~2–3% environment failures, then a branch-integration path lets stakeholders request new firmware, and a risk-based cap limits test scope. A pre-release firmware flow plus a 24-hour fix SLA forces high-priority bug turnaround. Builds, tests and evaluations become automated into a near-CI pipeline (some manual gating remains), two engineers operate the loop, and after one year the system delivers earlier feedback, greater stability and scalablity.
AI-written summary · about
chapters (7)
- 0:00System integration testing intro
- 3:21Early integration flaws
- 6:31Pre-build firmware testing
- 10:45Parallel firmware/software testing
- 14:58Improved process benefits
- 17:44Current state and future
- 18:09Q&A
related talks
55mQuality Engineering Evolution: What Lies Ahead in
38mEvolutionary Testing Strategy
36mHow to defuse a bomb Wait, I mean a bug
01h 09mScaling up with Embedded Testing
36mHow programmers & testers can be productive
26mThe Impact of Testing on a DevOps Pipeline
36mFrom Waterfall to Agile: 7 tips for Transforming Test Organization
32mClimbing the Mountain of CI/CD: A Tester’s Tale