AngularJS 1.x end of life: is ngMock $httpBackend stubbing still the right integration test strategy without production credentials?

Answer

Yes – $httpBackend stubbing remains an acceptable way to unit‑test the service layer when you cannot use real credentials or a live backend.

Confirmed facts

• $httpBackend provides deterministic, synchronous interception of $http calls, allowing you to assert request formation, headers, payload and response handling without a network.
• Across the 1.x series the known version‑specific differences that can break $httpBackend expectations are: the shift to $q‑based promises in 1.2, case‑insensitive header matching added in 1.3, and changes to flush()/$rootScope.$apply behavior in 1.6‑1.7.
• The AngularJS documentation recommends complementing these unit tests with a minimal offline smoke test that exercises the real $http transport (e.g., a json‑server or MirageJS instance) to catch transport‑level concerns such as CORS, TLS, timeout or redirect handling.

Likely explanation

Because AngularJS 1.x no longer receives patches, any test that makes real network calls must be isolated and use throwaway credentials. Stubbing eliminates that risk while still verifying the logic you own; the fake‑server smoke test adds confidence that the $http configuration (interceptors, timeout, withCredentials, etc.) behaves as expected when the stub is removed.

Steps for this case

1. Lock the exact AngularJS minor version in package.json or bower.json (e.g., 1.5.8).
2. Write unit tests using ngMock’s $httpBackend with expect*/when*, flush() and verifyNoOutstandingExpectations() to validate request formation, headers and response handling.
3. Add a separate test suite that starts a lightweight fake server (e.g., json-server --watch db.json on localhost:3000), configures $httpProvider to point to that host, and runs the same service‑layer calls without mocking.
4. Compare the outcomes of the mocked and fake‑server runs; any discrepancy indicates transport‑level behavior not covered by $httpBackend and should be investigated.
5. Document the version‑specific $httpBackend quirks you encounter (promise style, header case‑sensitivity, flush behavior) in your testing guide to prevent regression if the AngularJS version ever changes.

Missing diagnostic detail

To tailor the version‑specific checklist, please confirm the exact AngularJS 1.x minor version you are running in production.