angular.js/test/ngScenario, branch g3_v1_0 test($browser): correct false positive in ApplicationSpec.js 2013-09-11T21:21:12+00:00 Woody Peterson 2013-09-04T15:01:43+00:00 13f58447e239b29e576cdbf80629a32ba907ed2a Previously, the check that Application should return a new $window and $document had the arguments reversed in the first call to navigateTo; thus, the subsequent check of inequality of $window and $document in the next navigateTo call would always pass. This corrects the argument order, which makes this test not succeptible to false positives. 
Previously, the check that Application should return a new $window and
$document had the arguments reversed in the first call to navigateTo;
thus, the subsequent check of inequality of $window and $document in the
next navigateTo call would always pass.

This corrects the argument order, which makes this test not succeptible
to false positives.
chore: remove jstd leftovers 2013-06-28T23:29:09+00:00 Vojta Jina 2013-06-28T23:29:09+00:00 2fae296cbcd1eedac226f7bcda146426b8239322 






fix(scenario): include error messages in XML output
2013-02-07T12:10:17+00:00

Julie

2012-10-09T18:13:26+00:00

9a3a9b46e5d596811d85f11be16ac805ddfdc8f1

Fix the XML output of scenario tests so that it properly includes error
messages from failing specs.





Fix the XML output of scenario tests so that it properly includes error
messages from failing specs.







fix(scenario): don't trigger input events on IE9
2013-01-17T07:30:16+00:00

Igor Minar

2013-01-16T18:51:24+00:00

92c612a9deac6e311bc2c632d373d525bf9017a0

input.enter() should trigger 'change' rather than 'input' event on IE9 because
input events on IE9 are broken and angular doesn't rely on them





input.enter() should trigger 'change' rather than 'input' event on IE9 because
input events on IE9 are broken and angular doesn't rely on them







fix(jqLite): fire $destroy event via triggerHandler
2012-11-26T15:03:43+00:00

Igor Minar

2012-11-24T00:51:19+00:00

269fb43b3667c74b35980798fd54937d65b7b7de

in jQuery 1.8.x the data() data structure is changed and events are
not accessible via data().events. Since all we need is to trigger
all event handlers, we can do so via triggerHandler() api instead of
mocking with the internal jQuery data structures.

This fix was originally proposed by PeteAppleton via PR #1512.

Closes #1512





in jQuery 1.8.x the data() data structure is changed and events are
not accessible via data().events. Since all we need is to trigger
all event handlers, we can do so via triggerHandler() api instead of
mocking with the internal jQuery data structures.

This fix was originally proposed by PeteAppleton via PR #1512.

Closes #1512







fix(scenario-runner): support data-ng and x-ng based attributes
2012-10-31T21:10:26+00:00

Adam Macejak

2012-10-30T01:54:26+00:00

ad7ce0d40216cf3e0a721ef3a4815a03ae9f0bd9

Prefixed attributes like data-ng-model and x-ng-model were not being
found by the Selector. It was only looking at ng: and ng- prefixed
attributes.
Added a few tests as well to ensure the aforementioned prefixed
attributes are being matched properly.

Closes #1020





Prefixed attributes like data-ng-model and x-ng-model were not being
found by the Selector. It was only looking at ng: and ng- prefixed
attributes.
Added a few tests as well to ensure the aforementioned prefixed
attributes are being matched properly.

Closes #1020







fix(scenario): Adding meta tag to avoid cache issues
2012-08-31T04:34:42+00:00

German Galvis

2012-08-15T22:04:51+00:00

8bb3942453c5cc9c34affa689168c1bb46f0263e












fix(e2eRunner): $browser.location should delegate to apps $location
2012-04-12T09:36:03+00:00

Igor Minar

2012-04-12T09:15:36+00:00

df72852f3496d7640bb4f70837338e464b7ed69f

previously it would create a new instance which wasn't configured as the one in the app,
which resulted in incorrect values being returned in html5 mode with base url set





previously it would create a new instance which wasn't configured as the one in the app,
which resulted in incorrect values being returned in html5 mode with base url set







chore(ngSanitize): extract $sanitize, ngBindHtml, linkyFilter into a module
2012-04-11T22:50:47+00:00

Vojta Jina

2012-04-10T23:50:31+00:00

5bcd7198664dca2bf85ddf8b3a89f417cd4e4796

Create build for other modules as well (ngResource, ngCookies):
- wrap into a function
- add license
- add version

Breaks `$sanitize` service, `ngBindHtml` directive and `linky` filter were moved to the `ngSanitize` module. Apps that depend on any of these will need to load `angular-sanitize.js` and include `ngSanitize` in their dependency list: `var myApp = angular.module('myApp', ['ngSanitize']);`





Create build for other modules as well (ngResource, ngCookies):
- wrap into a function
- add license
- add version

Breaks `$sanitize` service, `ngBindHtml` directive and `linky` filter were moved to the `ngSanitize` module. Apps that depend on any of these will need to load `angular-sanitize.js` and include `ngSanitize` in their dependency list: `var myApp = angular.module('myApp', ['ngSanitize']);`







fix(scenario): dev secenario tests
2012-04-02T23:10:15+00:00

Mykhailo Kotsur

2012-04-01T16:08:44+00:00

59ae8adb3cfa635076b5cf64cc48b13a34bc04ad

closes #843

Fixed failed e2e test





closes #843

Fixed failed e2e test