Designing Hardware-independent Testing Laboratory API
summary
A modular testing lab called SLAV implements separate layers — test manager (minimal, runs semi‑compatible LAVA plans), test scheduler (declares capabilities and reservations), and data controller (device actions via scripts) — written in Go with an HTTP REST API and provided clients and shell helpers. Custom SD‑MUX and MUX‑Pi boards unify access and move I/O from USB to Ethernet, but deployments never advance much past about 100 devices and initial hardware setup is hard; source code and build files are on GitHub.
AI-written summary · about
chapters (6)
related talks
22mHardware in the loop pipelines for testing - for everyone!
44mAutomation beyond Testing and Embedded System Validation
40mAutomated Full System Testing on Hardware with OpenQA
33mAutomated Testing for Embedded Development: Next Generation Board Farming
41mAutomated Full System Testing on Hardware With OpenQA
43mAutomated Testing & Board Farming
41mUnveiling the Test Champions: Comparing Testing Automation Systems for Embedded...
38mGrowing a Lab for Automated Upstream Testing: Challenges and Lessons Learned