one of the failing tests in http#18 is related to this.
Since we're just getting a TypeError, it makes it sort of tricky for the person writing tests to fix this, it would be useful to be a bit more informative.
In angular-mocks, trying to flush with no outstanding requests will cause a test to fail, so we probably do want to fail in this case, but it's probably a better idea to make the error explicitly about "no promises to flush" or something.
one of the failing tests in http#18 is related to this.
Since we're just getting a TypeError, it makes it sort of tricky for the person writing tests to fix this, it would be useful to be a bit more informative.
In angular-mocks, trying to flush with no outstanding requests will cause a test to fail, so we probably do want to fail in this case, but it's probably a better idea to make the error explicitly about "no promises to flush" or something.