angular.js/src/ngMock, branch v1.2.0-rc.3 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
fix(ngMock.$interval): should use angular.isDefined 2013-10-09T19:12:26+00:00 Mark J. Titorenko 2013-10-09T15:31:51+00:00 9bbd62f4543ad8760deec08170c674cc028772cc The newly introduced `$interval` mock service for ngMock calls `isDefined` in the global namespace which fails when used within unit tests. This change adds the missing `angular.` prefix to such `isDefined` calls. Closes #4334 Closes #4353 
The newly introduced `$interval` mock service for ngMock calls `isDefined`
in the global namespace which fails when used within unit tests.

This change adds the missing `angular.` prefix to such `isDefined` calls.

Closes #4334
Closes #4353
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 






docs(mocks): fix syntax error in example
2013-09-28T19:23:18+00:00

Rob Culliton

2013-09-27T19:37:40+00:00

1618adfab1bfc3478786798fa55e8a767f52043f

Closes #4183





Closes #4183







docs(mock.inject): fix typo
2013-09-09T07:44:12+00:00

Pete Bacon Darwin

2013-09-09T07:44:12+00:00

01a7ec086604aba82d1c59727cd25a4a8fe172c4












docs(mock.inject): document underscore wrapping syntax
2013-09-05T13:34:40+00:00

JasonM23

2013-08-16T10:04:55+00:00

e12e584ca8db306dce8e0f4d3a212d77fbae966c

Add a summary describing the ignored underscore syntax sugar helper,
with a simple use case example.

Closes #3621





Add a summary describing the ignored underscore syntax sugar helper,
with a simple use case example.

Closes #3621







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












fix(ngMocks): $logProvider should not use internal APIs
2013-08-29T19:06:30+00:00

Adam de Baugh

2013-08-29T03:30:32+00:00

baaa73ee1ef25fa506ff7aaab3159d710acdafdb

angular.mocks.$LogProvider $logProvider.debugEnabled(false) is crashing
with undefined when run inside karma/jasmine test runner:

angular.module('foo', []).config(['$logProvider', function ($logProvider) {
  $logProvider.debugEnabled(false);
}]);

Closes #3612




angular.mocks.$LogProvider $logProvider.debugEnabled(false) is crashing
with undefined when run inside karma/jasmine test runner:

angular.module('foo', []).config(['$logProvider', function ($logProvider) {
  $logProvider.debugEnabled(false);
}]);

Closes #3612