What is better to use for fake requests to the server?

Question

Angular

There is a large single page app. Angular on the frontend. The development of new features begins with a prototype, which defines the request interface to the server. Because at the time of the development of the new feature, there is no server yet, then we use requests for the prepared json as a fake response. I suggested that the guys switch to the $httpBackend mock to write real requests and when the backend is ready, just turn off the fake. The señor disagrees and says more fuss. Now I sit and think: if this were the case, then why use a mock at all?

Answer 1

$httpBackend is used in unit tests, that's all. Not in E2E (although sometimes there) even, only in unit tests. That's why he's wet.
I usually make my own wrapper over $http for a project purely for my needs. That is, in principle, I try not to work directly with $http, there are many problems if several APIs are used. And already at the service level, you can stabilize the data. Just always return a resolved promise with data. Well, in any case, saving / loading data from the API should be taken out to some kind of service.

Answer 2

A normal solution with a mock, quite. I don’t know why you have such a beech señor.

Answer 3

https://github.com/a85/POSTMan-Chrome-Extension