LAVA + OpenQA = Automated, Continuous Full System Testing
summary
Automated continuous full‑system testing glues LAVA and OpenQA into GitLab CI so build artifacts become installer ISOs and then openqa.gnome.org jobs that compare screenshots (needles) and run SSH checks; LAVA dispatches to physical boards and QEMU workers. A backend lets OpenQA control a Raspberry Pi target over VNC, flashing kernels from kernelci branches (including 4.19 LTS) and reporting green 100% desktop matches for basic flows. Planned work adds more tests, kernelci integration and extra backends beyond VNC.
AI-written summary · about
chapters (9)
- 0:00Automated system testing
- 1:28Maintainability challenges
- 4:54Upstream versus downstream gap
- 8:03Automated continuous testing
- 9:51LAVA and OpenQA tools
- 12:59OpenQA with GNOME CI
- 18:38Tests on physical hardware
- 21:04Live demo and results
- 23:08Future plans and community
related talks
40mAutomated Full System Testing on Hardware with OpenQA
41mAutomated Full System Testing on Hardware With OpenQA
38mopenQA - end to end testing of operating systems
40mIntroduction to LAVA, the Linaro Automated Validation Architecture
39mTesting Your Yocto Proj: from Ptest & Testimage to LAVA
07mOniro CI/Testing integration with LAVA
29mTesting, a Journey from Testing Kernels to Testing Debian and Yocto
38mGrowing a Lab for Automated Upstream Testing: Challenges and Lessons Learned