Zephyr Testing & Debugging

SkillMonitoring & ops

Testing and debugging for Zephyr RTOS. Covers the Ztest framework for unit and integration tests, the Twister test runner for automated HIL/SIM validation, and advanced tracing/debugging techniques (SystemView, Thread Analyzer, Stack analysis). Trigger when writing unit tests, setting up CI/CD pipelines, or analyzing system performance and latency.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Zephyr Testing & Debugging skill

What this skill tells your AI

The instructions your AI receives, as published by beriberikix/zephyr-agent-skills in skills/testing-debugging/SKILL.md and read by ahel’s review.

Ensure code quality and system reliability using Zephyr's comprehensive testing framework and observability tools.

Core Workflows

1. Ztest Framework

Write robust unit and integration tests for native simulation and real hardware.

2. Twister Test Runner

Automate test execution across multiple platforms and generate professional reports.

  • Reference: twister_testing.md
  • Key Tools: twister script, testcase.yaml, hardware mapping.

3. Tracing & Debugging

Analyze system behavior, timing, and memory usage with advanced tracing tools.

Quick Start (Ztest)

#include <zephyr/ztest.h>

ZTEST_SUITE(basic_test, NULL, NULL, NULL, NULL, NULL);

ZTEST(basic_test, test_pass) {
    zassert_true(true, "Boolean evaluation failed");
}

Professional Patterns (Reliability)

  • Continuous Integration: Integrate Twister reports (twister.json) into CI/CD pipelines for automated regression testing.
  • HIL Validation: Use hardware maps to consistently run critical hardware tests on real devices during every release cycle.
  • Stack Safety: Always enable CONFIG_STACK_SENTINEL and the Thread Analyzer during development to catch memory issues early.

Automation Tools

Examples & Templates

Validation Checklist

  • twister executes selected test suites with no unexpected failures.
  • At least one ZTEST suite runs in simulation and reports pass/fail correctly.
  • Tracing or thread-analyzer output is captured and reviewed for hotspots.
  • CI artifacts include machine-readable reports (for example twister.json).

Resources

  • References:
    • ztest_framework.md: Writing tests with expectations and suites.
    • twister_testing.md: Using the test runner and metadata.
    • tracing_debugging.md: Tracing, stack analysis, and debugging backends.
  • Scripts:
    • twister_smoke.py: Lightweight Twister runner with summary output.
  • Assets:
    • testcase.yaml.template: Reusable testcase metadata template.

Signals

GitHub stars
63
Forks
15
Last commit
May 2026
Advanced
Catalog kind
skill
Gateway key
testing-debugging
Source
github.com/beriberikix/zephyr-agent-skills