メニュー
Use when needing to run tests locally in flutter_rust_bridge, or when debugging test failures before pushing
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/fzyzcjy/flutter_rust_bridge --skill frb-testコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Review a flutter_rust_bridge PR before treating it as ready, including subagent checks for correctness and test weakening.
Update flutter_rust_bridge CHANGELOG.md for a new release by collecting merged PRs since the previous version tag, mapping them to the target release section, and formatting entries to match the existing changelog style. Use when writing or refreshing a release section in CHANGELOG.md.
Use when modifying Rust API, codegen, or example code in flutter_rust_bridge to determine which generation commands to run
SKILL.md を表示中
SOC 職業分類に基づく
| name | frb-test |
| description | Use when needing to run tests locally in flutter_rust_bridge, or when debugging test failures before pushing |
Note: Check your user-level
remote-testingrules before running commands. Tests may require remote execution.
Maps change types to local test commands. Tests run on CI by default, so local testing is optional but useful for debugging.
| Change Type | Command |
|---|---|
| All Rust packages | ./frb_internal test-rust |
frb_rust/ | ./frb_internal test-rust-package --package frb_rust |
frb_codegen/ | ./frb_internal test-rust-package --package frb_codegen |
| Specific Rust package | ./frb_internal test-rust-package --package <path> |
frb_dart/ | ./frb_internal test-dart-native --package frb_dart |
| Dart example | ./frb_internal test-dart-native --package frb_example/<name> |
| Flutter example | ./frb_internal test-flutter-native --package frb_example/flutter_<name> |
| Web test | ./frb_internal test-dart-web --package frb_example/<name> |
Web tests compile Dart tests to WebAssembly and run in a headless browser. Some individual web test cases are flaky; rerun the failed web test job or command before treating the failure as deterministic.
frb_dartfrb_example/dart_minimalfrb_example/pure_dartfrb_example/pure_dart_pdewasm32-unknown-unknown target: rustup target add wasm32-unknown-unknown --toolchain nightly-2025-02-01rust-src component: rustup component add rust-src --toolchain nightly-2025-02-01wasm-pack: curl https://rustwasm.github.io/wasm-pack/installer/init.sh -sSf | shWhen running web tests in Docker containers, puppeteer needs --no-sandbox flag. The test runner auto-detects Docker environment via /.dockerenv.
Run: Debugging test failure, developing new tests, verifying fix before push
Skip: Documentation only, CI will catch it, just checking compilation
CI is slow and often queues for a long time. Before pushing a non-trivial FRB change, run meaningful local tests in the appropriate development environment and understand the result locally first. Scale the local test scope with the risk and blast radius of the change. Do not use CI as the first feedback loop for changes that can be verified locally.
Choose tests by blast radius:
After pushing to a PR branch, monitor GitHub Actions until the run reaches a terminal state. If CI fails, inspect the failing job logs and either fix the issue or clearly report why it is unrelated or flaky. Do not leave a PR in an unknown queued or in-progress state when the user asked for CI validation.
Before treating a non-trivial PR as ready, run the review gate in frb-pr-review; local tests alone do not check correctness review or test weakening.