Test Strategy for Zephyr
summary
A concrete test strategy lays out objectives—stability and reliability, effectiveness, transparency and traceability—and the rules that produce them: PR/main/nightly/weekly triggers with dynamic scoping so the smallest useful test set runs early, Twister + ZTest/pytest as the runners, GitHub Actions for CI, coverage collected from emulators and dashboards in Elastic/Codecov. Vendors own on-target hardware testing; project focuses on tier zero emulators and a curated tier one. The repo holds tests, there are >1,000 platforms and a million possible configurations, so selection and measurable automation matter.
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
23mTwister V2: New Framework for Testing Based on Pytest. Overview & Current Status