angular.js/test/ngMock, branch g3_v1_2 test(ngMock): workaround issue with negative timestamps 2014-03-19T04:31:20+00:00 Brett Porter 2014-03-18T04:36:00+00:00 d4ac25496aaace2b85aa9f5e5232e5eabeb40c63 In some specific timezones and operating systems, it seems that getTimezoneOffset() can return an incorrect value for negative timestamps, as described in #5017. While this isn't something easily fixed in the mock code, the tests can avoid that particular timeframe by using a positive timestamp. Closes #5017 Closes #6730 
In some specific timezones and operating systems, it seems that
getTimezoneOffset() can return an incorrect value for negative timestamps, as
described in #5017. While this isn't something easily fixed in the mock code,
the tests can avoid that particular timeframe by using a positive timestamp.

Closes #5017
Closes #6730
fix(ngMock): return false from mock $interval.cancel() when no argument is supplied 2014-02-05T00:41:25+00:00 Daniel Luxemburg 2014-02-04T01:04:46+00:00 dd24c78373b5d24ecb3b9d19e61e1b3b6c74d155 Closes #6103. Closed #6099. 
Closes #6103.
Closed #6099.
fix(mocks): always call functions injected with `inject` with `this` set to the current spec 2014-02-04T06:25:30+00:00 Wes Alvaro 2014-02-04T00:53:52+00:00 3bf43903397c703aa2e9ba1e1a48dbc9e8286ee2 Currently when a function is injected inside of a test we set the context to undefined which is a bug. Closes #6102 
Currently when a function is injected inside of a test we set the context to undefined which
is a bug.

Closes #6102
test(ngMock): fix the tests to not use global msie 2014-01-07T03:08:05+00:00 Vojta Jina 2014-01-07T03:08:05+00:00 affcbad501ad5e17b8cb30ad8a2c0d1de6686722 My bad when merging 7e916455b36dc9ca4d4afc1e44cade90006d00e3. These tests are run with compiled Angular and then the msie is not defined. 
My bad when merging 7e916455b36dc9ca4d4afc1e44cade90006d00e3.

These tests are run with compiled Angular and then the msie is not defined.
 fix(ngMock window.inject): Remove Error 'stack' property changes 2014-01-07T01:47:06+00:00 Andrew C. Greenberg 2013-11-20T06:53:33+00:00 7e916455b36dc9ca4d4afc1e44cade90006d00e3 Recent browsers, particularly PhantomJS 1.9.2 and Safari 7.0 treat the stack property as non-configurable and unwritable. Because window.inject captures the stack at the time of the inject, and attempts to insert it into a captured throw from the injected function by modifying e.stack, a meaningless error message and stack is thrown instead. This commit inserts two tests exposing the problem, and implements a proposed solution that builds a new error-like object that mimicks the old Error object, but with the additional stack information, and captures the toString function from the Error object prototype. This appears to work for the browsers suppoerted here. 
Recent browsers, particularly PhantomJS 1.9.2 and Safari 7.0
treat the stack property as non-configurable and unwritable.

Because window.inject captures the stack at the time of the inject,
and attempts to insert it into a captured throw from the injected
function by modifying e.stack, a meaningless error message and
stack is thrown instead.

This commit inserts two tests exposing the problem, and implements
a proposed solution that builds a new error-like object that mimicks
the old Error object, but with the additional stack information, and
captures the toString function from the Error object prototype.  This
appears to work for the browsers suppoerted here.
 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.