Testing in the world of IoT
summary
Claims that testing IoT needs end-to-end automation get grounded: a tester-only team builds a low-cost lab with Raspberry Pi fetching OTA firmware, a vision matrix camera to verify bulb state, and code in Python and physical devices driving switches. Surprises include burned debug hardware, 4s Bluetooth latency per state change, camera buffer contention and flashing timeouts. The concrete deliverable is a running orchestrator that aggregates microservice signals, decides pass/fail, and pushes results to dashboards and CI.
AI-written summary · about
chapters (6)
- 0:00Start
- 10:58Let's imagine a simple test scenario.
- 12:06Test scenario flow
- 19:04Module Flashing
- 20:23Switch Control
- 34:52Takeaway...
related talks
46mMobile & IoT Integration Testing
24mTesting of IoT and related technologies
50mCommon Strategy to Test IoT for Different Industries
43mContinuous Integration in IoT world - "Mission Impossible" or "A last hope"?
46mTesting The Next Generation Of Technologies: IoT
35mTest Automation for Bluetooth Connected IoT Devices
32mWhich kind of testing is needed in the age of IoT?
44mThe Future of Test Automation
