ALWAYS use when writing tests for Angular applications, including unit tests, component tests, service tests, or E2E tests with Jasmine, Karma, Vitest, or Cypress.
Scanned 9/9/2026
Install to Claude Code
npx -y skills add Lord1Egypt/awesome-skill-forge --skill skills-sh_oguzhan18_angular-ecosystem-skills_angular-testing --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Skills Sh Oguzhan18 Angular Ecosystem Skills Angular Testing?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/lord1egypt-skills-sh-oguzhan18-angular-ecosystem-skills-angul-8a227d3e)More formats (shields.io, HTML) on the badges page.
---
name: angular-testing
description: "ALWAYS use when writing tests for Angular applications, including unit tests, component tests, service tests, or E2E tests with Jasmine, Karma, Vitest, or Cypress."
metadata:
version: 21.0.0
generated_by: oguzhancart
generated_at: 2026-02-19
---
# Angular Testing
**Version:** Angular 21 (2025)
**Tags:** Testing, Jasmine, Karma, Vitest, Cypress, Jest
**References:** [Testing Guide](https://angular.dev/guide/testing) • [Testing API](https://angular.io/api/core/testing) • [Angular Blog](https://blog.angular.dev)
## API Changes
This section documents recent version-specific API changes.
- NEW: Vitest as default — Angular 21+ uses Vitest instead of Jasmine/Karma [source](https://loiane.com/2025/12/angular-v21-template-coverage-testing/)
- NEW: Template coverage — Coverage reports now include HTML templates [source](https://loiane.com/2025/12/angular-v21-template-coverage-testing/)
- NEW: Component input testing — Test component inputs directly with `Component输入`
- NEW: Functional interceptors for testing — Easier to test HTTP interceptors
- DEPRECATED: Karma test runner — Migrate to Vitest for modern Angular
## Best Practices
- Use TestBed for component testing
```ts
import { TestBed } from '@angular/core/testing';
import { MyComponent } from './my.component';
describe('MyComponent', () => {
let component: MyComponent;
let fixture: ComponentFixture<MyComponent>;
beforeEach(async () => {
await TestBed.configureTestingModule({
imports: [MyComponent]
}).compileComponents();
fixture = TestBed.createComponent(MyComponent);
component = fixture.componentInstance;
});
it('should create', () => {
expect(component).toBeTruthy();
});
});
```
- Use AAA pattern (Arrange-Act-Assert)
```ts
it('should calculate total correctly', () => {
// Arrange
const service = new CalculatorService();
// Act
const result = service.add(2, 3);
// Assert
expect(result).toBe(5);
});
```
- Use `fakeAsync` and `tick` for async operations
```ts
import { fakeAsync, tick } from '@angular/core/testing';
it('should fetch data after delay', fakeAsync(() => {
service.getData();
tick(1000);
expect(component.data).toBeTruthy();
}));
```
- Use spies for mocking
```ts
it('should call service', () => {
spyOn(service, 'getData').and.returnValue(of({ name: 'Test' }));
component.loadData();
expect(service.getData).toHaveBeenCalled();
});
```
- Use `by.css` for querying DOM elements
```ts
import { By } from '@angular/platform-browser';
it('should display title', () => {
fixture.detectChanges();
const el = fixture.debugElement.query(By.css('.title'));
expect(el.nativeElement.textContent).toBe('Hello');
});
```
- Test behavior, not implementation
```ts
// ❌ Bad - tests implementation details
expect(component['privateMethod']).toHaveBeenCalled();
// ✅ Good - tests behavior
expect(fixture.nativeElement.querySelector('.result')).toContain('expected');
```
- Use `provideHttpClient` for HTTP testing
```ts
TestBed.configureTestingModule({
providers: [
provideHttpClient(withInterceptors([authInterceptor]))
]
});
```
- Use mock services for dependencies
```ts
const mockAuthService = {
isAuthenticated: jasmine.createSpy().and.returnValue(true),
getToken: jasmine.createSpy().and.returnValue('fake-token')
};
TestBed.configureTestingModule({
providers: [{ provide: AuthService, useValue: mockAuthService }]
});
```
- Test form validation
```ts
it('should show error for invalid email', () => {
component.form.controls.email.setValue('invalid');
component.form.controls.email.markAsTouched();
fixture.detectChanges();
expect(fixture.nativeElement.querySelector('.error')).toBeTruthy();
});
```
- Use `detectChanges` appropriately
```ts
// After changing component properties
component.value = 'new value';
fixture.detectChanges();
// For async operations
fixture.detectChanges();
await fixture.whenStable();
fixture.detectChanges();
```
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!