Choosing between HTTP-layer mocking and service stubbing in Angular integration tests

Question

HTTP-layer vs service-layer mocking in Angular

When testing services that make HTTP calls, Angular provides HttpClientTestingModule with HttpTestingController to intercept requests at the HTTP layer. This approach mocks the backend responses without requiring production credentials or network access.

Alternatively, developers can stub the service itself by creating a mock implementation that returns predefined observables. This tests different layers of the application stack.

The unresolved decision centers on what integration behavior each approach actually covers. HTTP-layer mocking validates how the service processes responses and handles errors, but does not verify the service's internal logic or contract adherence. Service stubbing may miss HTTP-specific behaviors like interceptor effects, request cancellation, or timing issues.

Which integration concerns should be validated in unit tests versus integration tests, and how does the choice between HttpTestingController and service stubbing affect test coverage and maintenance burden?

Tasadduq Burney · Answer

Answer
Use HTTP-layer mocking with HttpTestingController when you need to assert the actual HTTP request (URL, method, headers, body) or verify that Angular interceptors, cancellation, or timeout logic are exercised. Stub the service itself when you only care about how consumers react to the observable output and want to keep tests fast and isolated.
When to choose HTTP-layer mocking

Provide HttpClientTestingModule in the test bed.
Inject the service under test and HttpTestingController.
Trigger the method that makes the HTTP call.
Call expectOne (or match) to assert request details.
Flush with a mock response or error.
Call verify to ensure no unexpected requests remain.

When to choose service stubbing

Create a mock class that implements the service’s public methods, returning of(mockData) or throwError(() => new Error(...)).
Override the service provider in the test bed with { provide: RealService, useClass: MockService }.
Inject the component or service under test.
Subscribe to the returned observable and assert the consumer’s behavior.

Missing diagnostic detail
Do you need to validate that Angular HTTP interceptors (e.g., auth header addition, logging, or error transformation) are applied to the request? If yes, HTTP-layer mocking is required; otherwise service stubbing suffices.

Choosing between HTTP-layer mocking and service stubbing in Angular integration tests

HTTP-layer vs service-layer mocking in Angular

1 answer

Answer

When to choose HTTP-layer mocking

When to choose service stubbing

Missing diagnostic detail

Your perspective belongs here.

0 question comments