Level Up Your Embedded Testing Game
summary
Pipeline converts FRETish requirements (exported JSON) via an open-source CLI to executable Robot Framework suites, then runs them through a custom twister harness against Zephyr targets. Project captures ~750 requirements and yields ~600 automated test cases; implementations include a FRET keyword library and application-specific keywords using Zephyr shell (mqtt/CAN adapters planned). Code runs locally and on real hardware via a Zephyr fork/branch but is not merged upstream yet, and timing checks (e.g. within 200 ms) and traceability tags are produced.
AI-written summary · about
chapters (21)
- 0:00Embedded testing in medical devices
- 1:03Trust and safety in testing
- 2:29Regulatory requirements and V-model
- 3:35Managing thousands of requirements
- 4:18Requirements engineering with FRET
- 7:29FRET requirements structure
- 11:24FRET for requirements management
- 13:31Digital microscope FRET example
- 16:20Robot Framework introduction
- 17:51Robot keyword-driven tests
- 20:23Linking FRET to Robot tests
- 21:48Exporting FRET to JSON
- 24:20Robot with Zephyr Twister
- 25:45Zephyr Twister overview
- 27:29Robot harness limitations
- 28:13New Robot Framework harness
- 31:07Requirements to test execution
- 32:52Automation benefits
- 34:18Open-source tool benefits
- 36:05Future improvements
- 37:11Q&A
related talks
44mTest Strategy for Zephyr- 44mTest Strategy for Zephyr
49mHarnessing the Twister: Zephyr Data-Driven Testing and Insights- 49mHarnessing the Twister: Zephyr Data-Driven Testing and Insights
23mTwister V2: New Framework for Testing Based on Pytest. Overview & Current Status
46mZephyr Application Development Using TDD: Getting Started
13mZephyr Unit Tests and Emulators at Google
38mRoman Zakharov: Robot Framework: A Perfect Tool to Get Rid Of