run-tests
Skill240 starsChanged 20 days agoMITView on GitHub
piper-plus の各言語ランタイムのテストを実行します。引数 python/rust/cs/go/js/cpp/all で対象を選択。未指定なら git diff から自動判定。
48 other projects use a version of this.
Adopted by
Most recently taken up by
- utopia-rise/fmod-gdextensiontheir own version, first seen Nov 9, 2026
- Pubx-ai/skillstheir own version, first seen Nov 8, 2026
- coralogix/cx-clitheir own version, first seen Nov 8, 2026
- DataDog/dd-trace-pytheir own version, first seen Nov 1, 2026
- busycaesar/Harnesstheir own version, first seen Nov 1, 2026
- NumericalEarth/Breeze.jltheir own version, first seen Oct 17, 2026
Used with
Projects with it also use release and code-review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillrelease
Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).
Also in 5 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 5 projects that use this
Other versions48 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 48
- netbox-community/netbox★ 22ksame name
- yagop/node-telegram-bot-api★ 9.2ksame name
- gitextensions/gitextensions★ 8.6ksame name
- ethereum/consensus-specs★ 4ksame name
- dotnet/sdk★ 3.2ksame name
- ComplianceAsCode/content★ 2.8ksame name
- idaholab/moose★ 2.4ksame name
- CliMA/Oceananigans.jl★ 1.4ksame name
- microsoft/testfx★ 1.1ksame name
- serenedb/serenedb★ 965same name
38 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- bump-depsSkill
- check-cross-runtimeSkill
- check-loanwordSkill
- check-new-runtime-assetSkill
- check-pr-readySkill
- check-puaSkill
- check-review-backlogSkill
- check-runtime-paritySkill
- commitSkill
- create-prSkill
- precheckSkill
- prepare-releaseSkill
- publish-modelSkill
- release-prepSkill
- reply-reviewSkill
- skill-healthSkill
- sync-docsSkill
- watch-ci-patternsSkill
- watch-prSkill
The file
Files
piper-plus テスト実行
各言語ランタイムのテストを CI と同じ条件でローカル実行します。
変更ファイル
!git diff --name-only HEAD 2>/dev/null | head -20
ターゲット選択
$ARGUMENTS:
python→ Python 全体rust→ Rust workspacecs→ .NET solutiongo→ Go modulejs→ JS/WASM (npm-package)cpp→ C++ (cmake build + ctest)all→ 上記すべて (順次、失敗しても次に進む)- (空) →
git diff HEADの結果から判定 (複数該当ならそれら全部)
各ターゲットの実行コマンド
Python
cd src/python_run
uv run pytest tests/ -o addopts="" -v --tb=short
cd ../..
# G2P 単体テスト (もし対象なら)
cd src/python/g2p
uv run pytest -o addopts="" -v --tb=short
cd ../../..注意:
- pytest.ini の
--covを-o addopts=""で上書き (pytest-cov が無い環境向け) - 学習・ベンチマーク系テストは除外 (
-m "unit and not training and not benchmark"も可)
Rust
cd src/rust
cargo test -p piper-plus --no-fail-fast
cargo test -p piper-plus --features naist-jdic --no-fail-fast
cd ../..C# (.NET)
dotnet test src/csharp/PiperPlus.sln -c Release --nologo --verbosity minimalGo
cd src/go
go vet ./... ./phonemize/...
go test -race -count=1 ./... ./phonemize/...
cd ../..JavaScript / WASM
cd src/wasm/openjtalk-web
npm run test:npm-package:all
cd ../../..C++
# Build がまだなら先にビルド
if [ ! -f build/CMakeCache.txt ]; then
cmake -S . -B build -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTS=ON
fi
cmake --build build --config Release
ctest --test-dir build -C Release --output-on-failure結果報告
各ターゲット完了後、以下の形式で報告:
## テスト実行結果
| ランタイム | Pass | Fail | Skip | 時間 |
|----------|------|------|------|------|
| Python (pytest) | 212 | 0 | 20 | 22s |
| Rust (cargo test) | 145 | 0 | 0 | 1m |
| ... | ... | ... | ... | ... |
### 失敗詳細
(失敗があった場合のみ、最初の 3 件まで)
- `test_xxx` (ファイル:行): エラー要約失敗時のヒント
- Python ImportError →
uv syncで依存をインストール - Rust feature not found →
cargo buildで先にビルドを通す - C# build failed →
dotnet restore src/csharp/PiperPlus.slnを実行 - WASM ImportError →
cd src/wasm/openjtalk-web && npm install - C++ ctest failed →
cmake --build build --verboseでビルドエラーを再確認
注意
- 失敗しても他のターゲットを続行する (
all時) - 単一ターゲット時は失敗即停止
- 環境依存テスト (espeak-ng 等) はスキップされる場合あり
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

