Automated Testing for Embedded Development: Next Generation Board Farming
summary
Company runs 120 slots across eight 19 inch racks and uses labgrid for hardware abstraction and pi-test for test cases with Jenkins (evaluating GitLab) for CI. Current pain points are flaky USB hubs, serial servers dropping characters, and power switches that refuse to toggle, costing remote hands time. Plan is one ARM SoC test automation controller per DUT with integrated Ethernet switch, PoE, GPIO, CAN and a power switch to eliminate shared USB buses; prototypes exist and software validation is scheduled for fall.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:01Why Do We Need To Talk about Bot Farming
- 3:36Topics
- 4:13What Do You Need To Control an Embedded Linux Device
- 7:36Main Use Cases for Board Farming
- 10:09Common Infrastructure
- 13:14Wi-Fi Access Point
- 16:10Continuous Testing and Continuous Integration
- 17:21How Infrastructure Is Built
- 20:55What Are Problems in Our Current Lab
- 26:36What Are Potential Solutions for this Problem
- 28:34The Architecture
related talks
40mBoF: Automated Testing and Board Farming
35mTest Harness: Continuous Testing on Hardware
43mAutomated Testing & Board Farming
36mFarming Together
44mAutomation beyond Testing and Embedded System Validation
40mAutomated Full System Testing on Hardware with OpenQA
41mUnveiling the Test Champions: Comparing Testing Automation Systems for Embedded...
42mAutomated Testing Laboratory for Embedded Linux Distributions