Write Angular component tests using TestBed, ComponentHarness, and HttpTestingController with proper signal input handling. Use when writing component tests, mocking HTTP calls, or testing signal inputs.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
[WEB-TEST-01] Tripartite Naming & AAA Cadence: Test names must follow Method_Scenario_ExpectedBehavior and adhere strictly to Arrange-Act-Assert.[WEB-TEST-02] Accessible Harnesses & User Actions: Query UI components via ComponentHarness (e.g. MatButtonHarness) or accessible queries; strictly ban raw CSS class selectors or arbitrary DOM traversal.[WEB-TEST-03] Ban on Component Private State & Property Inspection: Never inspect component private state or internal properties directly. Assert on visible DOM state, output events, or harness query outcomes.[WEB-TEST-04] HTTP Boundary Mocking: Intercept HTTP requests at the boundary using provideHttpClientTesting() + HttpTestingController rather than mocking internal services or methods. Tests must verify true component data flow.[WEB-TEST-05] Bug-First Regression Lock: Every PR resolving a bug ticket or with title fix(...) must introduce a test reproducing the defect prior to the fix.[WEB-TEST-02]): Use ComponentHarness (e.g. MatButtonHarness) not CSS selectors. loader.getHarness(MatButtonHarness) + await button.click(). Never query by CSS class. See harness pattern.[WEB-TEST-04]): Intercept with provideHttpClientTesting() + HttpTestingController rather than manual mocks. Call expectOne, .flush(mockData), and verify() in afterEach.[WEB-TEST-03]): Use fixture.componentRef.setInput('name', value) + fixture.detectChanges(), not direct assignment. Signals sync — no fakeAsync needed for most signal-driven tests.@angular/build:unit-test (faster, native ESM, no Karma). Configure in angular.json. Jasmine/Karma still supported. Standalone: import directly in TestBed.configureTestingModule({ imports: [StandaloneComponent] }).[WEB-TEST-01] Vague test names: Banish non-descriptive names or mixed AAA phases; follow Method_Scenario_ExpectedBehavior.[WEB-TEST-02] Raw CSS selectors / DOM traversal: Query via ComponentHarness or accessible roles, not CSS class strings.[WEB-TEST-03] Testing private state: Never inspect internal properties or use direct @Input() assignment; use setInput().[WEB-TEST-04] Manual HttpClient mocks: Always mock the network boundary with provideHttpClientTesting() + HttpTestingController.[WEB-TEST-05] Bug fix without reproduction test: Ban bug fix PRs lacking defect regression tests.When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:
Never query by CSS class
native ESM
Additional task-grounded exact anchors: ComponentHarness
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.
日本語の概要は準備中です。原文の説明を表示しています。
Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their specific skills.
日本語の概要は準備中です。原文の説明を表示しています。
Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.
日本語の概要は準備中です。原文の説明を表示しています。
Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.
日本語の概要は準備中です。原文の説明を表示しています。
Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.
日本語の概要は準備中です。原文の説明を表示しています。
Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test recipes to their specific skills.
日本語の概要は準備中です。原文の説明を表示しています。