ワンクリックでManusで任意のスキルを実行

good-testing

スター4

フォーク0

更新日2026年7月14日 07:53

Guides testing changes in this ROS2 workspace. Use when modifying, adding, or reviewing tests, pytest files, QML assertions, Nav2/SLAM config tests, or patrol/UI backend test coverage.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

liaojingwu20041031

liaojingwu20041031/electric-power-inspection-robot

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Good Testing

Before adding or changing tests in this repository, read docs/好测试规范.md.

Rules

Protect real failures: safety, map semantics, patrol state, command routing, schemas, and public UI/backend contracts.
Do not chase test count. Prefer one existing focused test over a new duplicate.
Test behavior and contracts, not incidental wording, layout dimensions, or component order.
For Nav2/SLAM values, lock exact numbers only when they are safety boundaries or file-format semantics. Otherwise check presence, positivity, range, or cross-parameter consistency.
Keep fakes tiny. Implement only methods the tested path calls.
Do not add hardware requirements to default pytest runs.

When Editing Existing Tests

Keep emergency stop, control lock, velocity/direction, footprint, map unknown, schema, route preview, and patrol state-machine coverage.
Relax brittle UI text/layout assertions unless the text is an API.
Merge same-file duplicate assertions only when it clearly reduces noise.
Do not touch runtime code just to satisfy a test cleanup.

このリポジトリの他の Skills

同じリポジトリ

robot-motion-test-boundary

liaojingwu20041031/electric-power-inspection-robot

Use when handling real YLHB robot hardware, patrol routes, Nav2 goals, teleoperation, or runtime testing that could cause physical robot movement.

2026-07-114

ros2-practice-first

liaojingwu20041031/electric-power-inspection-robot

Debugs and fixes ROS2 robot runtime problems with logs, dependency order, and real-device verification. Use for Nav2, AMCL, TF, lifecycle, launch sequencing, patrol startup, sensors, actuators, CAN, serial, cameras, SLAM, and Jetson deployment. Prevents mock-heavy or test-count-driven overengineering.

2026-07-104

name	good-testing
description	Guides testing changes in this ROS2 workspace. Use when modifying, adding, or reviewing tests, pytest files, QML assertions, Nav2/SLAM config tests, or patrol/UI backend test coverage.

Good Testing

Before adding or changing tests in this repository, read docs/好测试规范.md.

Rules

Protect real failures: safety, map semantics, patrol state, command routing, schemas, and public UI/backend contracts.
Do not chase test count. Prefer one existing focused test over a new duplicate.
Test behavior and contracts, not incidental wording, layout dimensions, or component order.
For Nav2/SLAM values, lock exact numbers only when they are safety boundaries or file-format semantics. Otherwise check presence, positivity, range, or cross-parameter consistency.
Keep fakes tiny. Implement only methods the tested path calls.
Do not add hardware requirements to default pytest runs.

When Editing Existing Tests

Keep emergency stop, control lock, velocity/direction, footprint, map unknown, schema, route preview, and patrol state-machine coverage.
Relax brittle UI text/layout assertions unless the text is an API.
Merge same-file duplicate assertions only when it clearly reduces noise.
Do not touch runtime code just to satisfy a test cleanup.