BoF: Quality and Testing Processes for Zephyr + Discussion
summary
Proposal centers on building a distributed testing framework that aggregates results from many companies' hardware ranges while honoring proprietary secrecy, plus automating submissions into the existing test results repo. It argues for more emulation before hardware to catch logic bugs cheaply, identifies the need to define failure criteria and fault-tolerant boards, and asks for minimal actionable metrics (how many boards fail, coverage gains, surprising cross‑platform breaks) and a budgeted plan so dependability work can scale.
AI-written summary · about
chapters (14)
- 0:00Testing and quality in Zephyr
- 2:10Testing levels in Zephyr
- 4:18Distributed hardware testing
- 7:47Emulation vs hardware testing
- 9:56Optimizing CI and cloud
- 13:28Community testing involvement
- 16:41Automating test results
- 19:53Verification beyond testing
- 21:21Governance and dependability
- 22:46Emulation vs hardware challenges
- 24:37Test failure interpretation
- 27:46Bug triage with test data
- 29:11Strategic hardware coverage
- 31:20Closing remarks
related talks
44mTest Strategy for Zephyr- 44mTest Strategy for Zephyr
40mBoF: Automated Testing and Board Farming
46mZephyr Application Development Using TDD: Getting Started
46mZephyr Application Development Using TDD: Getting Started
40mZephyr Off-Chip Peripheral Emulation
40mTesting Zephyr Bluetooth Devices at Scale- 40mTesting Zephyr Bluetooth Devices at Scale