菜单
Use when: adding or extending Flutter integration/E2E tests for Beacon with fake backend, ProviderScope overrides, and reusable test robots.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | integration-test-skill |
| description | Use when: adding or extending Flutter integration/E2E tests for Beacon with fake backend, ProviderScope overrides, and reusable test robots. |
Viết integration test deterministic cho các flow nhiều màn hình của Beacon mà không gọi API/realtime/notification/storage thật, trừ khi task yêu cầu test environment riêng.
integration_test/..agents/copilot-instructions.md.agents/instructions/project-context.md.agents/instructions/architecture-rules.mddocs/integration-tests.mdlib/core/providers/providers.dartlib/core/config/app_routes.dartlib/core/config/app_router.dartlib/features/<feature>/Nếu GitNexus index stale, chạy npx gitnexus analyze trước. Trước khi sửa production symbol, chạy impact analysis theo AGENTS.md.
integration_test/
<feature>/
<flow>_test.dart
config/
fakes/
helpers/
robots/
Không tạo cây thư mục rỗng. Chỉ tạo file/folder khi flow cần.
integration_test/config/.integration_test/robots/.pumpAndSettle() trên màn có timer/animation lặp lại. Dùng pumpUntilFound, pumpUntilTextFieldCount, hoặc helper có timeout rõ ràng.MyApp thật trong ProviderScope.dotenv.testLoad(fileInput: 'APP_ENV=production\n').SharedPreferences.setMockInitialValues({}) cho mỗi test.main() trong integration test; tự khởi tạo dependency cần thiết trong harness.flutter analyze integration_testflutter test --no-pub integration_test\<feature>\<flow>_test.dart -r expandedflutter test nếu thay đổi có nguy cơ ảnh hưởng unit/widget test hiện cógitnexus_detect_changes(scope: "all") trước commitUse when: any task involves Flutter UI, UX, animation, motion, redesign, image-to-code, or mobile visual implementation quality.
Use when: planning or implementing Flutter local database, cache, offline-read, local datasources, repository cache orchestration, stale data handling, and deterministic tests.
Use when: selecting Flutter test levels, planning unit/widget/integration coverage, and creating verification checklists for risky or cross-layer changes.
Use when: starting a task and loading Beacon source-of-truth context before writing code.
Use when: documenting architecture decisions, tradeoffs, impacts, and rollback guidance after important changes.
Use when: integrating or modifying backend APIs, endpoint contracts, request/response mapping, and business error-code handling in Beacon.