dart-test — Claude Code skill: unit and integration tests
Skill for writing and debugging DART tests. Provides commands for unit tests, integration tests, CI validation, and visual verification of simulations.
BSD-2-Clause 1 installs ★ 1,232 updated 2026-10-29
npx skills add dartsim/dart --skill dart-test -a claude-codeWhat dart-test does
Includes Pixi commands: pixi run test for quick checks, pixi run test-all for full C++/Python build and test aggregate, pixi run test-gui for GUI tests. Tests are organized by type—unit in tests/unit/, integration in tests/integration/, regression in tests/regression/.
Uses GoogleTest framework. Before submitting a PR, run pixi run lint, pixi run test-all, and pixi run -e gazebo test-gz when Gazebo compatibility could be affected. Debugging starts with pixi run test to isolate the failure, then check CI logs via gh run view.
Key gotcha: pixi run build compiles libraries only, not test binaries. Run pixi run build-tests first, or build the specific test target. GUI tests requiring a graphics device are skipped in test-all but included in test-gui. For changes to scene structure, dynamics, or Filament rendering, also load dart-verify-sim.
What it helps with
- run unit tests for the DART project via Pixi
- validate integration tests before submitting a PR
- debug a failing test using CI logs
- test GUI changes and visual rendering output
- verify Gazebo compatibility when collision code changes
Example prompts for the agent
- Run quick validation with
pixi run test - Execute full lint and test suite before PR:
pixi run lintandpixi run test-all - Test GUI changes with
pixi run test-gui
How to install dart-test
1Skills CLI (Vercel)
npx skills add dartsim/dart --skill dart-test -a claude-code2Manually: put the files in place
~/.claude/skills/dart-test/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/dart-test/
1Skills CLI (Vercel)
npx skills add dartsim/dart --skill dart-test -a codex2Manually: put the files in place
.agents/skills/dart-test/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add dartsim/dart --skill dart-test -a cursor2Manually: put the files in place
.cursor/skills/dart-test/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install dartsim/dart .claude/skills/dart-test2Manually: put the files in place
.github/skills/dart-test/SKILL.md1Skills CLI (Vercel)
npx skills add dartsim/dart --skill dart-test -a gemini-cli2Platform CLI
gemini skills install https://github.com/dartsim/dart --path .claude/skills/dart-testManually: put the files in place
.devin/skills/dart-test/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add dartsim/dart --skill dart-test -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about dart-test
How do I install dart-test in Claude Code?
Run npx skills add dartsim/dart --skill dart-test -a claude-code, then open ~/.claude/skills/dart-test/SKILL.md.
What does dart-test do?
Provides Pixi commands to run unit tests, integration tests, CI validation, and visual debugging for DART simulations. Includes GoogleTest configuration and paths to test directories.
Why load dart-verify-sim alongside dart-test?
When changes affect scene structure, dynamics, collisions, Filament rendering, or visual examples, dart-verify-sim adds a text-first oracle and DebugOverlay capture tools for verification.
Source text
SKILL.md · BSD-2-Clause
--- name: dart-test description: "DART Test: unit tests, integration tests, CI validation, and debugging" --- # DART Testing Load this skill when writing or debugging tests. ## Quick Commands ```bash pixi run test # Quick test run pixi run test-py # Python tests pixi run test-all # Build defaults and run C++/Python tests pixi run test-gui # GUI tests except native-window tests; needs a graphics device pixi run -e gazebo test-gz # Gazebo/gz-physics compatibility gate ``` ## Full Documentation For complete testing guide: `docs/onboarding/testing.md` For CI/CD troubleshooting: `docs/onboarding/ci-cd.md` ## Test Organization - Unit tests: `tests/unit/` - Integration tests: `tests/integration/` - Regression tests: `tests/regression/` (start from `test_Issue000Template.cpp`) ## Writing Tests 1. Follow existing patterns in the test directory 2. Use GoogleTest framework 3. Name tests descriptively, in the style of the neighboring tests in that file ## CI Validation Before submitting PR: ```bash pixi run lint # Must pass pixi run test-all # Default build plus C++/Python runtime aggregate pixi run -e gazebo test-gz # Must pass when Gazebo/gz-physics compatibility could be affected ``` ## Debugging Test Failures ```bash # Run the smallest existing Pixi test task that covers the failure pixi run test # Get CI logs gh run view <RUN_ID> --log-failed ``` ## Simulation And Visual End-to-End Checks When a failure or change depends on scene structure, dynamics, collision/contact, simulation stepping, Filament output, or a visual example, also load `dart-verify-sim`. Use its text-first oracle and then an assessed, claim-tied capture through `DebugOverlay`. Record a concrete no-visual reason only when capture is unavailable or not applicable. ## Gotchas - `pixi run build` builds libraries only, NOT every test binary. If you run `ctest` directly, build the relevant test target first; `pixi run build-tests` builds the branch test targets. - `pixi run test-all` builds the default CMake `ALL` graph. The branch config pins `BUILD_TESTING=ON`, so that graph also runs CTest and pytest. Pair it with `pixi run lint`; use `pixi run test` or `pixi run test-py` for focused reruns and clearer failure attribution. - `pixi run test`, `test-py`, and `test-all` build the GUI but skip tests that need a graphics device (CTest label `gui-device` and the Python GUI rendering tests). Device-free GUI tests remain in the default gates; the `gui` label covers all GUI tests. GUI, Filament, and `dartpy.gui` changes also need `pixi run test-gui`, which selects `-L gui -LE filament-native` in the same `build/<env>/cpp/Release` tree. Native-window tests need a desktop session or Xvfb: `ctest --test-dir build/<env>/cpp/Release -L filament-native` (`ctest --test-dir build/<env>/cpp -C Release -L filament-native` on Windows). - For package, collision, constraint, or dependency changes that could affect downstream users, run `pixi run -e gazebo test-gz`.
© dartsim · BSD-2-Clause · dartsim/dart