angular.js/test/ngMock, branch v1.2.6 fix(angular-mocks): use copy of mock data in $httpBackend 2013-12-11T23:18:45+00:00 Karl Seamon 2013-12-06T19:35:34+00:00 f69dc16241c8b631123ad0b09674f0a5e0ff32fe Copy mock data returned from the mock $httpBackend. This prevents modifications to the response from affecting future responses. Previously, this misbehavior was being mitigated by the deep copy in $resource, but that no longer exists. 
Copy mock data returned from the mock $httpBackend.
This prevents modifications to the response from affecting future responses.
Previously, this misbehavior was being mitigated by the deep copy in $resource, but that no longer exists.
fix(ngMock): fixes httpBackend expectation with body object 2013-11-22T06:57:15+00:00 Corey Burrows 2013-11-14T14:42:35+00:00 4d16472b918a3482942d76f1e273a5aa01f65e83 Fixes an issue with httpBackend expectations where a given body object may not match the actual request body if its keys are serialized in a different order. Closes #4956 
Fixes an issue with httpBackend expectations where a given body object
may not match the actual request body if its keys are serialized in a
different order.

Closes #4956
fix(tests): Correct tests for IE11 2013-11-22T05:53:09+00:00 Tobias Bosch 2013-11-21T22:30:50+00:00 579242346c4202ea58fc2cae6df232289cbea0bb Some tests were wrong. However, src/* did not contain problems. Fixes #5046 
Some tests were wrong. However, src/* did not contain problems.

Fixes #5046
fix(modules): stop leaking global variables in tests 2013-10-10T18:58:15+00:00 Pete Bacon Darwin 2013-10-10T08:11:21+00:00 07272608d8ae39a5dd220cdb5637b1439342d5c3 The routeUtils.js file was declaring a number of functions that were leaking into other modules such as ngMocks causing tests to pass incorrectly. Closes #4360 
The routeUtils.js file was declaring a number of functions that were
leaking into other modules such as ngMocks causing tests to pass
incorrectly.

Closes #4360
feat($interval): add a service wrapping setInterval 2013-10-07T20:45:40+00:00 Julie 2013-09-13T19:47:05+00:00 2b5ce84fca7b41fca24707e163ec6af84bc12e83 The $interval service simplifies creating and testing recurring tasks. This service does not increment $browser's outstanding request count, which means that scenario tests and Protractor tests will not timeout when a site uses a polling function registered by $interval. Provides a workaround for #2402. For unit tests, repeated tasks can be controlled using ngMock$interval's tick(), tickNext(), and tickAll() functions. 
The $interval service simplifies creating and testing recurring tasks.
This service does not increment $browser's outstanding request count,
which means that scenario tests and Protractor tests will not timeout
when a site uses a polling function registered by $interval. Provides
a workaround for #2402.

For unit tests, repeated tasks can be controlled using ngMock$interval's
tick(), tickNext(), and tickAll() functions.
fix(*): protect calls to hasOwnProperty in public API 2013-10-07T16:01:13+00:00 Peter Bacon Darwin 2013-10-05T09:49:09+00:00 7a586e5c19f3d1ecc3fefef084ce992072ee7f60 Objects received from outside AngularJS may have had their `hasOwnProperty` method overridden with something else. In cases where we can do this without incurring a performance penalty we call directly on Object.prototype.hasOwnProperty to ensure that we use the correct method. Also, we have some internal hash objects, where the keys for the map are provided from outside AngularJS. In such cases we either prevent `hasOwnProperty` from being used as a key or provide some other way of preventing our objects from having their `hasOwnProperty` overridden. BREAKING CHANGE: Inputs with name equal to "hasOwnProperty" are not allowed inside form or ngForm directives. Before, inputs whose name was "hasOwnProperty" were quietly ignored and not added to the scope. Now a badname exception is thrown. Using "hasOwnProperty" for an input name would be very unusual and bad practice. Either do not include such an input in a `form` or `ngForm` directive or change the name of the input. Closes #3331 
Objects received from outside AngularJS may have had their `hasOwnProperty`
method overridden with something else. In cases where we can do this without
incurring a performance penalty we call directly on Object.prototype.hasOwnProperty
to ensure that we use the correct method.

Also, we have some internal hash objects, where the keys for the map are provided
from outside AngularJS. In such cases we either prevent `hasOwnProperty` from
being used as a key or provide some other way of preventing our objects from
having their `hasOwnProperty` overridden.

BREAKING CHANGE: Inputs with name equal to "hasOwnProperty" are not allowed inside
form or ngForm directives.

Before, inputs whose name was "hasOwnProperty" were quietly ignored and not added
to the scope.  Now a badname exception is thrown.

Using "hasOwnProperty" for an input name would be very unusual and bad practice.
Either do not include such an input in a `form` or `ngForm` directive or change
the name of the input.

Closes #3331
 feat(ngMock.$timeout): remove flushNext method 2013-10-02T22:59:49+00:00 Vojta Jina 2013-09-05T19:01:31+00:00 fc8034b352121f8f057dbd5e3837eeb17e1df580 






feat(ngMock): allow passing an object literal as shorthand to module
2013-09-03T21:22:12+00:00

Merrick Christensen

2013-08-26T05:45:58+00:00

f737c97df02918eb5b19bf5c8248fa3e20f9b361












revert: feat(mocks): make $timeout#flush throw an exception when empty
2013-08-28T00:23:36+00:00

Igor Minar

2013-08-28T00:20:30+00:00

4114f9c21bec5a396e59954dfc42d2c96527ac3d

This reverts commit cbf06a5d64aba537f0e2679a194d3998d8365493.

This turned out to be a bad idea because it allow us to fast-forward
the wall clock time (see previous commit).





This reverts commit cbf06a5d64aba537f0e2679a194d3998d8365493.

This turned out to be a bad idea because it allow us to fast-forward
the wall clock time (see previous commit).







revert: fix(mocks): $timeout#flush should not update time when empty
2013-08-28T00:21:11+00:00

Igor Minar

2013-08-28T00:20:04+00:00

70b44ad32a79e0746e19a74bde35f49c79f89942

This reverts commit 42af8eada2803a54a98b4f792e60feb480d68a0c.

This turned out to be a bad idea as it prevents us from moving the
time forward and asserting that the component state didn't change
due to the scheduled task executing too early.





This reverts commit 42af8eada2803a54a98b4f792e60feb480d68a0c.

This turned out to be a bad idea as it prevents us from moving the
time forward and asserting that the component state didn't change
due to the scheduled task executing too early.