angular.js/test/ngScenario
Woody Peterson 64e7b7774e test($browser): correct false positive in ApplicationSpec.js
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.
2013-09-11 22:19:24 +01:00
..
e2e fix(scenario): Adding meta tag to avoid cache issues 2012-08-30 15:36:42 -07:00
output fix(scenario): include error messages in XML output 2013-02-07 04:09:52 -08:00
ApplicationSpec.js test($browser): correct false positive in ApplicationSpec.js 2013-09-11 22:19:24 +01:00
DescribeSpec.js chore(module): move files around in preparation for more modules 2012-03-28 11:16:35 -07:00
dslSpec.js fix(ngScenario): select().option(val) should prefer exact value match 2013-07-12 10:05:23 +01:00
FutureSpec.js refactor(fromJson): always use native JSON.parse 2012-03-28 16:30:38 -07:00
matchersSpec.js chore(module): move files around in preparation for more modules 2012-03-28 11:16:35 -07:00
mocks.js chore(module): move files around in preparation for more modules 2012-03-28 11:16:35 -07:00
ObjectModelSpec.js chore(module): move files around in preparation for more modules 2012-03-28 11:16:35 -07:00
RunnerSpec.js chore(module): move files around in preparation for more modules 2012-03-28 11:16:35 -07:00
ScenarioSpec.js feat(scenario): expose jQuery for usage outside of angular scenario 2013-07-31 15:50:12 -07:00
SpecRunnerSpec.js fix(scenario-runner): support data-ng and x-ng based attributes 2012-10-31 13:58:13 -07:00