Streamlining Testing with Generic Tests and Emulators
summary
Generic tests plus a standardized emulator backend API claim to cut driver test work by letting one test exercise many devices; Zephyr implements set_channel and get_sample_range on emulators, uses q31 fixed‑point with a shift value for precision, and samples five interpolated points across each channel. The generic test runs in native_posix CI, is live in Zephyr with a few sensors already using it, and adding an emulator plus backend typically takes about half to one day while validating the data path end to end.
AI-written summary · about
chapters (11)
- 0:00Zephyr emulation and testing intro
- 1:47Zephyr emulators overview
- 4:13Emulation testing for sensor drivers
- 8:10Standardizing emulator APIs
- 10:18Backend API structure
- 13:51Fix-point numbers in sensors V2
- 19:33AKM9918C sensor backend
- 24:46Generic test in Zephyr
- 29:02Benefits and call to action
- 30:26References and closing
- 31:08Q&A
related talks
37mStreamlining Testing with Generic Tests and Emulators
40mZephyr Off-Chip Peripheral Emulation
13mZephyr Unit Tests and Emulators at Google
44mTest Strategy for Zephyr
46mZephyr Application Development Using TDD: Getting Started- 44mTest Strategy for Zephyr
32mUsing Customerized QEMU Co-simulation for Development and Test of Zephyr Applications
47mThe Native Simulator and Zephyr