Automated Full System Testing on Hardware With OpenQA
summary
Automated end-to-end hardware testing uses OpenQA plus LAVA to run the same screenshot-and-click tests on emulation and real boards, with a working open-source daemon called qad that exposes screenshots and input over HTTP. Teams build a USB switcher to automate 800+ USB insert/remove cycles and a CAN JSON mapper to simulate bus signals. “Testing in a box” packs gitlab runner, CAN, USB hub and peripherals into one deployable unit that already works on prototype rigs.
AI-written summary · about
chapters (19)
- 0:00Intro
- 1:01Introductions
- 1:21Outline of today's talk
- 1:56Background: software complexity
- 4:59Theory of Constraints
- 6:57Removing bottlenecks
- 7:37System Validation
- 12:57Mind the gap!
- 14:28Introduction to OpenQA
- 15:40What's a needle / test in this context?
- 21:27Q.A.D. as a remote access service
- 28:15Building OpenQA needles with Q.A.D.
- 30:06Q.A.D. - Planned future work
- 31:34Taking test automation further...
- 33:19USB Switcher - Further automation
- 34:38USB Switcher - Fully Open Testing
- 35:40Testing in a Box
- 36:35The solution so far..
- 40:00Summary
related talks
40mAutomated Full System Testing on Hardware with OpenQA
38mopenQA - end to end testing of operating systems
26mLAVA + OpenQA = Automated, Continuous Full System Testing
44mAutomation beyond Testing and Embedded System Validation
41mUnveiling the Test Champions: Comparing Testing Automation Systems for Embedded...
33mAutomated Testing for Embedded Development: Next Generation Board Farming
22mHardware in the loop pipelines for testing - for everyone!
05mOpenQA - life is too short for manual testing