run-tests
Runs the Isaac Lab-Arena pytest suite across its three required phases (no-cameras, with-cameras, with-subprocess) inside the running isaaclab_arena Docker container. Use when the user asks to run the tests, test their changes, verify the test suite passes, check whether a change broke anything (e.g. "did I break anything", "do the tests still pass", "is everything still working"), run only one specific phase (e.g. "run Phase 1", "run only the no-camera tests", "skip the camera and subprocess tests"), or run coverage for a specific module.
适合你，如果你需要快速验证 Isaac Lab-Arena 的代码变更是否通过测试
npx oh-my-skill add isaac-sim/isaaclab-arena/run-testscurl -fsSL https://oh-my-skill.com/install.sh | bash -s -- isaac-sim/isaaclab-arena/run-testsnpx oh-my-skill verify isaac-sim/isaaclab-arena/run-tests怎么用
商店整理自技能原文 · 版本 62a5339 · 表述以原文为准装上后，Claude 会在 Docker 容器中运行 Isaac Lab-Arena 测试套件的三个阶段（无相机、有相机、有子进程），并依次报告结果。若某阶段失败，会停止并告知第一个失败的测试文件、函数和错误。
当你说“运行测试”、“检查是否弄坏了什么”、“只运行 Phase 1”等要求时触发。
技能原文 SKILL.md
Run Tests
Default (no argument): run all three phases in order. phase1: no-cameras, no-subprocess only. phase2: with-cameras only. phase3: with-subprocess only.
The three phases run mutually exclusive sets of tests (selected via different pytest marker filters) and must be invoked separately. For a full pre-PR run, every phase must pass before moving on to the next.
All commands run inside the already-running container via docker exec. Each clone of the repo on the host system has its own container, so at the start of a session resolve the one mounting this clone into ARENA_CONTAINER (empty = none running — use the dev-container skill first):
ARENA_CONTAINER=$(docker ps --filter "volume=$(git rev-parse --show-toplevel)" --format '{{.Names}}' | head -1)
Run the phase commands below in that same shell so $ARENA_CONTAINER stays set (or substitute the literal name).
Phase 1 — no cameras, no subprocess
The fastest of the three. Useful on its own when iterating on changes that don't touch rendering or subprocess paths.
docker exec "$ARENA_CONTAINER" su $(id -un) -c \ "cd /workspaces/isaaclab_arena && \ /isaac-sim/python.sh -m pytest -sv \ -m 'not with_cameras and not with_subprocess' isaaclab_arena/tests"
Phase 2 — with cameras
docker exec "$ARENA_CONTAINER" su $(id -un) -c \ "cd /workspaces/isaaclab_arena && \ /isaac-sim/python.sh -m pytest -sv \ -m 'with_cameras and not with_subprocess' isaaclab_arena/tests"
Phase 3 — with subprocess
docker exec "$ARENA_CONTAINER" su $(id -un) -c \ "cd /workspaces/isaaclab_arena && \ /isaac-sim/python.sh -m pytest -sv \ -m 'with_subprocess' isaaclab_arena/tests"
Run a single test file or function
# single file docker exec "$ARENA_CONTAINER" su $(id -un) -c \ "cd /workspaces/isaaclab_arena && \ /isaac-sim/python.sh -m pytest isaaclab_arena/tests/test_asset_registry.py" # single function docker exec "$ARENA_CONTAINER" su $(id -un) -c \ "cd /workspaces/isaaclab_arena && \ /isaac-sim/python.sh -m pytest isaaclab_arena/tests/test_asset_registry.py::test_default_assets_registered"
On failure
- Report the failing phase and the first failing test (file, function, and one-line error).
- Stop. Do not run later phases until the failure is investigated.
- If the failure looks unrelated to recent changes, run the same test in isolation to confirm.
A run is "all green" only when all three phases pass with no failures or errors.