ngMock - why does $httpBackend match the first and not the last mock definition?

[szimek]

Is there any reason why $httpBackend matches the first and not the last mock definition? If it worked the other way around (i.e. $httpBackend.when added new mock definitions to the beginning of definitions array instead of the end of it) it would be much easier to overwrite already mocked requests.

I've got some default mock definitions common for almost all tests that are loaded before each test and would like to be able to easily overwrite them in some specific tests.

I wanted to prepare PR that changes this, but there's even a unit test that explicitly checks for this behavior.

EDIT: In ngMock module unit tests like should match headers if specified or should match data if specified, the first mocks are more specific than the later ones. In a real app, I'd expect something opposite - one would create general mocks for most tests and then define more specific ones in selected tests.

[petebacondarwin]

I think this sounds like a good idea, but of course it would be quite a breaking change to applications.
Let's see if the rest of the team agrees and if so then aim to put it into 1.5

[drewzh]

This is actually a really annoying feature when it comes to E2E testing with Protactor, as currently there's no module available that will allow you to keep reference to the promise returned by the mock $httpBackend to re-purpose the redirect after it's already been set (I'm currently using https://www.npmjs.com/package/http-backend-proxy to allow interaction with $httpBackend from my Protractor tests).

So essentially, it's impossible to test a success response and then immediately test a failure from the same API endpoint without having to do a full browser refresh to clear down the intercepts.

Allowing the option of matching the last added regex instead of the first would make this kind of testing trivial. But essentially for me at the moment, integrating Protractor into my tests is impossible due to the high number of tests that can't be changed easily.

[szimek]

@petebacondarwin Are there still any chances this could land in 1.5, as there already were 2 beta releases?
How does it work in Angular 2? Is there the same problem?

[yogeshgadge]

Why don't we just add something like resetDefinitions() along the lines of resetExpectations() ? This will at-least help in setting new definitions.

[szimek]

You could also add it as an option that would default to the current code, so it would be backwards compatible. It's really just a matter of changing push to unshift in one place (which we do ourselves after every release of Angular 1.x 😉 )