Building the Traceability for Design and Testing in Zephyr
summary
Zephyr adds a traceability layer that links requirements, design docs and tests, harvesting existing Doxygen/Sphinx output and generating a traceability matrix. Tools include breathe and mls_traceability glued into docsgen and Sphinx, Twister plus jsn2 for test reports, and automation that maps XML objects to visual matrices. Work-in-progress ties ~10,000 test cases to requirements and computes coverage (example shows 98% test coverage), with upstreaming planned.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:28Enjia Mai Introduction
- 1:34What is traceability
- 3:54Why traceability
- 5:20Best practices
- 6:36Building traceability
- 7:28Documentation generation
- 8:15Requirement documentation
- 9:20Test specification documentation
- 10:21Final work product
- 11:17Traceability matrix
- 12:17Python module
- 14:45Test automation
- 15:43Conclusion
related talks
44mTest Strategy for Zephyr- 44mTest Strategy for Zephyr
46mZephyr Application Development Using TDD: Getting Started
46mZephyr Application Development Using TDD: Getting Started
40mGenerate, Develop and Visualize Zephyr Platforms and Apps with Visual System Desig...
49mHarnessing the Twister: Zephyr Data-Driven Testing and Insights
44mModel-Based Testing for the Zephyr RTOS
43mZephyr Documentation BoF