Testing Your Yocto Proj: from Ptest & Testimage to LAVA
summary
Yocto's testimage runs system tests by booting QEMU or real hardware and produces a testresults.json; ptest packages and runs package test suites at compile time. A contributed result-tool subcommand converts that JSON to junit XML for GitLab CI, used here to show three demo tests (pass/skip/fail) in pipelines. For scale, LAVA handles job submission via lava-cli, network-boot + NFS root deploys, multinode sync signals and remote-artifact tokens; the setup operates and integrates with GitLab.
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
48mPrimer: Testing Your Embedded System - What is a ptest, Lava, Fuego and...?
29mTesting, a Journey from Testing Kernels to Testing Debian and Yocto
26mLAVA + OpenQA = Automated, Continuous Full System Testing
48mLiving on Master: Using Yocto Project, Jenkins and LAVA for a Rolling Release
34mFrom Zero to First Test in Your Own LAVA Laboratory in less than 45 minutes)
07mOniro CI/Testing integration with LAVA
38mGrowing a Lab for Automated Upstream Testing: Challenges and Lessons Learned
45mUpdate on LAVA Testing for bare metal systems