How do you test Angular components and services?

Question

Accepted Answer

Angular ships a full testing setup (Jasmine + Karma by default, though many teams use Jest). It provides **`TestBed`** to configure a testing module and instantiate components/services with their dependencies — leveraging DI to inject mocks.

## Testing a service (simplest)

```ts
describe("UserService", () => {
  let service: UserService;
  let httpMock: HttpTestingController;

beforeEach(() => {
    TestBed.configureTestingModule({
      imports: [HttpClientTestingModule], // mock HttpClient
      providers: [UserService],
    });
    service = TestBed.inject(UserService);
    httpMock = TestBed.inject(HttpTestingController);
  });

it("fetches users", () => {
    service.getUsers().subscribe(users => expect(users.length).toBe(2));
    const req = httpMock.expectOne("/api/users"); // assert the request was made
    req.flush([{ id: 1 }, { id: 2 }]);             // provide a fake response
  });
});
```

`HttpClientTestingModule` + `HttpTestingController` let you assert requests and supply fake responses without hitting a real server.

## Testing a component

```ts
describe("CounterComponent", () => {
  let fixture: ComponentFixture<CounterComponent>;
  let component: CounterComponent;

beforeEach(() => {
    TestBed.configureTestingModule({ imports: [CounterComponent] }); // standalone
    fixture = TestBed.createComponent(CounterComponent);
    component = fixture.componentInstance;
    fixture.detectChanges(); // trigger initial change detection
  });

it("increments on click", () => {
    const button = fixture.nativeElement.querySelector("button");
    button.click();
    fixture.detectChanges();                     // update the view
    expect(component.count).toBe(1);
    expect(button.textContent).toContain("1");   // assert the rendered DOM
  });
});
```

The `ComponentFixture` gives access to the component instance **and** its rendered DOM; you must call `fixture.detectChanges()` to run change detection after interactions.

## Mocking dependencies via DI

```ts
TestBed.configureTestingModule({
  providers: [{ provide: AuthService, useValue: mockAuthService }], // inject a fake
});
```

Angular's DI makes mocking trivial — provide a fake implementation for any dependency.

## Async testing

```ts
it("loads async", fakeAsync(() => {
  component.load();
  tick();                  // simulate passage of time / flush microtasks
  fixture.detectChanges();
  expect(component.data).toBeDefined();
}));
```

`fakeAsync`/`tick` (or `waitForAsync`) control async timing deterministically.

## Testing levels

```text
Unit:        services, pipes, isolated component logic (fast, most numerous)
Integration: component + template + child components via TestBed
E2E:         full user flows (Cypress, Playwright) — separate from unit tests
```

## Why it matters

Testing is a first-class concern in Angular, and its DI architecture makes it especially testable — you inject mocks for any dependency.

Knowing `TestBed` (configure + inject), `ComponentFixture` (instance + DOM + `detectChanges`), `HttpClientTestingModule` for HTTP, and async helpers (`fakeAsync`/`tick`) covers writing reliable unit and integration tests — essential for the large, long-lived enterprise apps Angular is built for.