菜单
Use when: writing meshsa tests, fixing flaky async tests, preserving pytest coverage, using FakeClock, SeqIdFactory, LoopbackBus, fake Meshtastic, fake TAK, or bridge e2e tests.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | meshsa-test-conventions |
| description | Use when: writing meshsa tests, fixing flaky async tests, preserving pytest coverage, using FakeClock, SeqIdFactory, LoopbackBus, fake Meshtastic, fake TAK, or bridge e2e tests. |
| argument-hint | Code path under test and whether async, codec, transport, or config behavior is involved |
packages/meshsa/tests/ with test_*.py names.pytest-asyncio native async tests; the project config sets
asyncio_mode = "auto".FakeClock and SeqIdFactory from tests/conftest.py for deterministic
timestamps and message IDs.LoopbackBus and LoopbackTransport for in-process bridge behavior.python -m pytest for the final coverage gate.Envelope fields, payload values, registry
behavior, reconnect state, and delivery counts.packages/meshsa.packages/meshsa/tests/conftest.pypackages/meshsa/tests/test_node.pypackages/meshsa/tests/test_router.pypackages/meshsa/tests/test_router_codecs.pypackages/meshsa/tests/test_bridge_e2e.pyUse when: working in packages/jetson_yolo_gcs — adding a detector backend (YOLO/Hailo/ONNX/TensorRT), a tracker backend (Norfair/SORT), GStreamer camera/egress pipeline, the MAVLink LANDING_TARGET bridge, precision-landing safety, or the perception pipeline failure policy.
Use when: running pre-PR checks, performing regression testing, validating ruff linting/formatting, verifying mypy type safety, and checking test coverage before pushing.
Use when: working on the optional NVIDIA Nemotron inference bridge — meshsa.inference, NemotronClient/InferenceService/NemotronConfig, MESHSA_INFERENCE_* env vars, aiohttp session reuse, [AI Insight] feedback-loop filter, or the aioresponses test mocks.
Use when: adding or changing metrics/health export — RouterMetrics, render_prometheus, per-transport counters, the /metrics or /healthz route, HealthConfig fields, or a Grafana golden-signal dashboard.
Use when: touching the supervised two-way command path (Initiative C) — meshsa.command.*, flightctl/run_commander.py, arm/disarm/RTL/set_mode, COMMAND_INT/ACK, force-disarm, operator confirmation, command audit log, or arm preconditions.
Use when: starting a roadmap/initiative feature, new milestone work, a transport/codec/backend that adds behavior, or any change big enough to need a design. Author or update a spec under docs/specs first; code cites the spec by section.