Continuous Integration in IoT world - "Mission Impossible" or "A last hope"?
summary
A concrete CI pipeline for constrained IoT devices emerges: a local farm of Raspberry Pi flashing rigs plus cameras and mobile devices, orchestration in Python-based test arbiter, image checks from a vision matrix 3x3, REST calls to cloud and OTA flows. It takes about three years to build (3 → 15 people), firmware images exceed 100 MB, prototypes often die (10 → 6–7), production fault rate ≈ 0.8% and OTA updates remain the single biggest systemic risk.
AI-written summary · about
chapters (13)
- 0:00Start
- 5:26Testing Scope & Challenges
- 7:03Pains of "high tech" companies
- 8:47Test scenario flow
- 11:00Let's make it step by step!
- 12:20Big picture
- 13:27Requirements of loTE2E Test Environment
- 14:13Let's prototype!
- 14:41Module Flashing
- 17:042 Switch Control
- 17:423 Vision System
- 20:08Set parameters considerably!
- 25:35Takeaways...
related talks
46mMobile & IoT Integration Testing
41mTesting in the world of IoT
49mImplementing Modern CI in an IoT Medical Device
24mTesting of IoT and related technologies
50mCommon Strategy to Test IoT for Different Industries
24mThe evolution of a system integration test process
46mTesting The Next Generation Of Technologies: IoT
36mInternet of Things Quality Assurance