ngMock $httpBackend does not support numeric timeouts

[bourey]

ngMock's $httpBackend service appears to support promised-based timeouts, but not numeric ones. Example test demonstrating the issue:

it('should abort requests after numeric timeout', inject(function($timeout) {
  hb.expect('GET', '/url1').respond(200);

  hb('GET', '/url1', null, callback, null, 200);
  $timeout.flush(300);

  expect(callback).toHaveBeenCalledWith(-1, undefined, '');
  hb.verifyNoOutstandingExpectation();
  hb.verifyNoOutstandingRequest();
}));

[pkozlowski-opensource]

@bourey I'm not sure I understand what you mean - I was trying to put your scenario under a test but there are way too many missing pieces to understand what is your real issue.

Could you please provide more details in a plunk that shows your exact code? I've started this one http://plnkr.co/edit/D7ZmwIEWts1OTV0p5I8a?p=preview but as I've said there is just not enough info to move forward on this one.

[pkozlowski-opensource]

Oh, I think I know what you mean - your test is the one that should go to https://github.com/angular/angular.js/blob/master/test/ng/httpBackendSpec.js, right?

[pkozlowski-opensource]

OK, so this is kind of valid in the sense that mock $httpBackend doesn't behave the same way as the real one (that accepts both numeric timeouts as well as promises) which means that people can simulate timeouts in their tests: http://plnkr.co/edit/D7ZmwIEWts1OTV0p5I8a?p=preview