Primer: Testing Your Embedded System - What is a ptest, Lava, Fuego and...?
summary
Quick tour of concrete tools and tradeoffs: Yocto Ptest packages unit tests and already has 64 ptest packages available but full runs can take five hours or more; Fuego compiles tests on the host and ships a large suite (Fuego: 100+ tests) with strong parsers; Lava orchestrates board farms with a master/worker model and ships Lava: 150 device templates for parallel jobs; labgrid enables single-board reservation and R4D exposes racks via libvirt so boards appear as R4D -> libvirt executors.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:45Who uses a ptest
- 1:48What is a ptest
- 2:42What are ptest
- 4:34How ptest works
- 10:24Fuego
- 16:49Lava
- 23:49Kernel CI
- 29:19LabGrid
- 33:03ForDev
- 37:26Other systems
- 39:11Conclusion
- 40:36Questions
related talks
39mTesting Your Yocto Proj: from Ptest & Testimage to LAVA
41mUnveiling the Test Champions: Comparing Testing Automation Systems for Embedded...- 41mUnveiling the Test Champions: Comparing Testing Automation Systems for Embedded...
41mTesting with Volcanoes - Fuego+LAVA Going Distributed
44mAutomation beyond Testing and Embedded System Validation
41mReducing Friction in Testing Using QEMU and Labgrid for Yocto-based Products
34mFrom Zero to First Test in Your Own LAVA Laboratory in less than 45 minutes)
40mAutomated Full System Testing on Hardware with OpenQA