Angular Testing Agent Skill
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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill angular-testingWhat comes with it
6 017 bytes besides the instructionThe instruction itself
9 sections, as written by the authorTesting
Priority: P1 (HIGH)
1. Query via Component Harnesses
- Use
ComponentHarness(e.g.,MatButtonHarness) not CSS selectors — stable across DOM changes. loader.getHarness(MatButtonHarness)+await button.click(). Never query by CSS class.
See harness pattern for ComponentHarness examples.
2. Mock HTTP with HttpTestingController
provideHttpClientTesting()not manual HttpClient mocks.- Call
expectOne,.flush(mockData),verify()inafterEach.
See harness pattern for HttpTestingController examples.
3. Test Signal Inputs Correctly
fixture.componentRef.setInput('name', value)— not direct assignment.fixture.detectChanges()aftersetInput().- Signals sync — no
fakeAsyncneeded for most signal-driven tests.
4. Choose Your Test Runner
- Angular v20+: Vitest via
@angular/build:unit-test— faster, native ESM, no Karma. Configure inangular.json. - Jasmine/Karma still supported for existing projects.
- Standalone: import directly in
TestBed.configureTestingModule({ imports: [StandaloneComponent] }).
Anti-Patterns
- No DOM CSS selectors: Query via
ComponentHarness, not CSS class strings. - No manual HttpClient mock: Use
provideHttpClientTesting()+HttpTestingController. - No direct @Input() assignment: Use
fixture.componentRef.setInput()for signal inputs.
References
- Harness Pattern
Canonical response anchors
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
Other skills for the same job
different authors, same section of the catalogue
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when implementing any feature or bugfix, before writing implementation code
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.
Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.
This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.
How to use it
Take hoangnguyen0403/angular-testing from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.