diff options
| -rw-r--r-- | src/ngMock/angular-mocks.js | 13 |
1 files changed, 6 insertions, 7 deletions
diff --git a/src/ngMock/angular-mocks.js b/src/ngMock/angular-mocks.js index c9f31431..413e0aae 100644 --- a/src/ngMock/angular-mocks.js +++ b/src/ngMock/angular-mocks.js @@ -960,13 +960,12 @@ angular.mock.dump = function(object) { * * # Flushing HTTP requests * - * The $httpBackend used in production always responds to requests with responses asynchronously. - * If we preserved this behavior in unit testing we'd have to create async unit tests, which are - * hard to write, understand, and maintain. However, the testing mock can't respond - * synchronously because that would change the execution of the code under test. For this reason the - * mock $httpBackend has a `flush()` method, which allows the test to explicitly flush pending - * requests and thus preserve the async api of the backend while allowing the test to execute - * synchronously. + * The $httpBackend used in production always responds to requests asynchronously. If we preserved + * this behavior in unit testing, we'd have to create async unit tests, which are hard to write, + * to follow and to maintain. But neither can the testing mock respond synchronously; that would + * change the execution of the code under test. For this reason, the mock $httpBackend has a + * `flush()` method, which allows the test to explicitly flush pending requests. This preserves + * the async api of the backend, while allowing the test to execute synchronously. * * * # Unit testing with mock $httpBackend |