Testing Your Yocto Proj: from Ptest & Testimage to LAVA
summary
Compares three concrete stacks: testimage + qemu or SSH for quick image system tests, ptest packages + ptest-runner for packaged unit tests, and LAVA for automated, multi‑device scheduling including multinode device tests; provides a junit tool that converts testresults.json into JUnit XML so GitLab CI displays results; shows network‑boot LAVA job descriptions, remote‑artifacts tokens for hiding credentials, and that a running LAVA lab scales well after initial setup.
AI-written summary · about
chapters (9)
- 0:00Testing Yocto projects
- 2:53Testimage framework
- 8:12Ptest framework
- 12:27JUnit results visualization
- 16:46LAVA introduction
- 21:44LAVA architecture
- 27:43LAVA job submission
- 30:30LAVA multinode testing
- 33:21Q&A
related talks
56mLAVA for LITE Platforms and Tests
07mOniro CI/Testing integration with LAVA
41mAutomated Full System Testing on Hardware With OpenQA
55mBest practices for getting devices in LAVA
40mI heart the Yocto Project
31mBootloader testing in LAVA
42mYocto Project Autobuilders and the SWAT Team
01h 03mGetting started with Yocto Project