Introduction To Twister and Adding Support for Hardware Runners
summary
Twister automates discovery build execution and reporting through a six-stage pipeline and outputs XML, JSON, HTML reports for CI; this work adds an XSDB runner implemented as a Python runner class plus CMake metadata so boards can dump ELFs and run on Versel and Verselet Gen2 RPU/APU targets. Integration links Zephyr build outputs to real hardware, registers a subclass of Zephyr binary runner, requires a board config for load addresses, and currently runs one runner per twister instance with per-test flashing so turnaround time improves but flashing frequency remains.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 1:25What is Twister
- 3:12Twister’s six-stage pipeline
- 7:07Hardware runners in Twister
- 9:13Custom hardware runner steps
- 11:27Q&A
related talks
35mTwister: A Test Utility for Contributors
49mHarnessing the Twister: Zephyr Data-Driven Testing and Insights- 49mHarnessing the Twister: Zephyr Data-Driven Testing and Insights
43mPytest Tests in Twister
43mPytest Tests in Twister
23mTwister V2: New Framework for Testing Based on Pytest. Overview & Current Status
46mZephyr Application Development Using TDD: Getting Started
44mLevel Up Your Embedded Testing Game