Test Strategy for Zephyr
summary
A formal test strategy now codifies objectives (stability, effectiveness, transparency, traceability) and chooses concrete tooling and triggers: Twister, GitHub Actions, ZTest and pytest, Jenkins for vendor farms, emulators/simulators for tier‑0 and tier‑1. It counts >1,000 platforms and >1,000 test suites that create an untestable million configurations, sees ~100 daily commits (up to 8,000 per release), runs PR/main/nightly/weekly gates, publishes Elastic dashboards and coverage from four emulator platforms, and assigns on‑target hardware verification to vendors.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:24Zephyr needs test strategy
- 3:07Challenges in Zephyr testing
- 4:32Four objectives of test strategy
- 7:23Principles for stability
- 9:29Optimizing test resources
- 10:56Trigger-dependent test selection
- 14:07Transparency in testing
- 17:39Test documentation needs
- 19:25Testing frameworks
- 20:51Test management roles
- 21:35Risk and quality management
- 24:03Testing responsibilities
- 25:27Summary and future
- 26:51Q&A
related talks
44mTest Strategy for Zephyr
13mZephyr Unit Tests and Emulators at Google
46mZephyr Application Development Using TDD: Getting Started
46mZephyr Application Development Using TDD: Getting Started
49mHarnessing the Twister: Zephyr Data-Driven Testing and Insights
37mStreamlining Testing with Generic Tests and Emulators
32mBoF: Quality and Testing Processes for Zephyr + Discussion
44mLevel Up Your Embedded Testing Game