Testing, a Journey from Testing Kernels to Testing Debian and Yocto
summary
Pipeline builds kernels and Debian/Yocto images in GitLab CI (cross‑compile for multiple architectures with GCC 11/12/13), boots real boards (RPI4, MIPS ci20) with LAVA and runs graphical checks with OpenQA, combining them via a LAVA→OpenQA handoff so desktop, mouse and SSH are validated nightly. Debian Sid images come from vmdb2 builds; images are flashed to USB and swapped into the Pi with an open‑source USB switch (AT commands) so U‑Boot is exercised too. Yocto images use poky with a small layer adding qad for KMS screenshots; caching drops build time from ~75 to ~7 minutes.
AI-written summary · about
chapters (13)
- 0:00Testing journey
- 1:02Kernel testing with LTS
- 3:35LAVA for hardware testing
- 5:44OpenQA for GUI testing
- 8:12LAVA and OpenQA combined
- 10:00Debian unstable on Pi
- 13:52Automating USB flashing
- 14:34QAD for remote control
- 17:25GitLab pipeline for Debian
- 17:48Yocto testing with Poky
- 21:35Summary and improvements
- 24:24Live pipeline demo
- 26:47Q&A
related talks
29mTesting, a Journey from Testing Kernels to Testing Debian and Yocto
39mTesting Your Yocto Proj: from Ptest & Testimage to LAVA
26mLAVA + OpenQA = Automated, Continuous Full System Testing
48mLiving on Master: Using Yocto Project, Jenkins and LAVA for a Rolling Release
41mDebian & Yocto: State of the Art
40mAutomated Full System Testing on Hardware with OpenQA
41mReducing Friction in Testing Using QEMU and Labgrid for Yocto-based Products
32mBuilding and Testing an Automotive Platform - How Automotive Grade Linux is Built and Tested