I think we should open a bug in github. If it's not deemed a bug, then it
should at least go into the "breaking changes" section. :)

On Wed, Mar 23, 2016 at 4:28 AM, Arto Chydenius <[email protected]>
wrote:

> Excluding route config from karma.conf.js seems to work for me too but as
> you said, it doesn't feel like a correct solution.
>
> I was thinking of making a bug report about this in Github, but I'm not
> sure whether this is really a bug. On the other hand I'd guess that this
> affects quite a lot of projects.
>
> On Tuesday, March 22, 2016 at 8:10:01 PM UTC+2, Alexandre Brasil wrote:
>>
>> Just a small correction: my current Angular version is 1.5.1, not 1.5.2.
>>
>> On Tuesday, March 22, 2016 at 3:02:09 PM UTC-3, Alexandre Brasil wrote:
>>>
>>> I'm experiencing the same problem since I updated my application from
>>> Angular 1.4 to 1.5.2.
>>>
>>> Whenever my tests hit a $scope.$apply() or $httpBackend.flush(), the
>>> default route ('/') is resolved and it tries to fetch its data from the
>>> backend. In my case, this route has a 'resolve' property that calls a rest
>>> service before trying to load the template. If I comment out the 'resolve',
>>> then it tries to fetch the route template. Since my tests don't specify
>>> those http expectations, those tests fail.
>>>
>>> I've managed to work around this issue by segregating the route config
>>> in another file and excluding it in my karma.conf.js config file, but I'd
>>> rather not have to do it. I'm still searching for a better (right?) way to
>>> do it, but no luck so far.
>>>
>>> On Tuesday, March 22, 2016 at 8:46:55 AM UTC-3, Arto Chydenius wrote:
>>>>
>>>> Hi everyone,
>>>>
>>>> I have an AngularJS project which has Jasmine tests that are run with
>>>> Karma. When upgrading from 1.5.0 to 1.5.1+ my tests start to fail since
>>>> they try to access my front page partial (Error: Unexpected request: GET
>>>> partials/frontpage.html).
>>>>
>>>> I get the tests to pass by preprocessing templates with
>>>> karma-ng-html2js-preprocessor but even if the actual tests pass, at some
>>>> point Karma still throws the same error not related to any individual test.
>>>> The exact change that breaks the tests is this one
>>>> <https://github.com/angular/angular.js/commit/8237482d49e76e2c4994fe6207e3c9799ef04163#diff-34e732507a1b6941aaf4ae5084a7c6caR24>
>>>> .
>>>>
>>>> Has anyone else been experiencing similar problems?
>>>>
>>>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "AngularJS" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/angular/3uMX8V4HWGo/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/angular.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.

Reply via email to