القائمة
Run BartonCore C/C++ unit tests. Use when the user wants to run unit tests, verify code changes pass tests, run a specific test, or list available tests. Covers ctest commands, test filtering, CMocka (C) and Google Test (C++) frameworks, and test source locations.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Run and interact with the BartonCore reference application. Use when the user wants to start the reference app, commission devices, execute/read/write resources, or troubleshoot runtime issues. Covers CLI flags, interactive commands, isolated session management, and known pitfalls.
Format C/C++ code in BartonCore. Use when the user wants to format source files, understand formatting conventions, or fix formatting issues. Covers clang-format usage, the diff-only rule, manual blank-line conventions that clang-format cannot enforce, and the pre-commit hook.
Validate SBMD (Spec-Based Matter Driver) v4 specification files. Use when the user has edited .sbmd.js files, wants to check schema conformance, or verify driver structure. Covers the validation script, JSON schema, spec file locations, and automatic build-time validation.
Build BartonCore from source. Use when the user wants to compile the project, rebuild after code changes, reconfigure CMake options, or understand the build system. Covers the build.sh convenience script, incremental cmake builds, CMake configuration flags, and the development build profile.
Debug BartonCore applications and tests. Use when the user needs to set breakpoints, step through code, inspect state, or diagnose crashes. Covers three workflows — gdb for the C/C++ reference app and unit tests, pdb/debugpy for Python integration tests, and gdb-with-Python for debugging C code called from Python tests.
Work with Matter test devices in BartonCore. Use when the user wants to start Matter sample apps, use chip-tool to commission or control devices, work with matter.js virtual devices for integration testing, or create new custom virtual device types. Covers pre-built sample apps, chip-tool commands, and the matter.js sideband API.
| name | run-unit-tests |
| description | Run BartonCore C/C++ unit tests. Use when the user wants to run unit tests, verify code changes pass tests, run a specific test, or list available tests. Covers ctest commands, test filtering, CMocka (C) and Google Test (C++) frameworks, and test source locations. |
| license | Apache-2.0 |
| compatibility | Requires the BartonCore Docker development container and a completed build. |
| metadata | {"author":"rdkcentral","version":"1.0"} |
The project must be built before running tests. If not yet built, run:
cmake --build build
ctest --output-on-failure --test-dir build
This runs all registered unit tests and prints output only for failing tests.
Filter by name pattern:
ctest -R <pattern> --output-on-failure --test-dir build
Examples:
ctest -R deviceService --output-on-failure --test-dir build
ctest -R matter --output-on-failure --test-dir build
ctest -R "sbmd.*validator" --output-on-failure --test-dir build
ctest -N --test-dir build
This lists all test names without running them. Useful for finding the right filter pattern.
BartonCore uses two unit test frameworks:
bcore_add_cmocka_test().bcore_add_cpp_test() with auto-discovery via gtest_discover_tests().| Area | Location |
|---|---|
| Core library tests | core/test/ |
| Device library tests | libs/device/descriptors/c/test/, libs/device/philipsHue/c/test/ |
| C API tests | api/c/test/ |
Test files are typically prefixed with test or suffixed with Test.
For more detail on all tests (not just failures):
ctest --output-on-failure --test-dir build -V
If ctest fails with a command-not-found error:
/.dockerenv existscmake --build build