Can there be a more helpful error for non-existing routes

[homanchou]

I don't know if this is the right venue, but here is my user story:

As a developer, when I use an incorrect route in my $urlRouterProvider.otherwise config, I would prefer to see an error like 'no matching route for $urlRouterProvider.otherwise' instead of 'Some of your tests did a full page reload!', so that I know where the error is coming from, so that I do not pull my hair out.

http://stackoverflow.com/questions/20960332/ui-router-causing-full-page-reload-in-controller-test

[timkindberg]

Haha, we can mark it as a bug and see what happens.

[homanchou]

I may have jumped to the wrong conclusion. A co-worker wrote some new tests and the error Some of your tests did a full page reload! came back despite using a correct value for $urlRouterProvider.otherwise(...). I have updated the stackoverflow http://stackoverflow.com/questions/20960332/ui-router-causing-full-page-reload-in-controller-test conversation. I'm not sure what my problem is now since the error I'm getting is unexpected GET request for the state's template file.

[timkindberg]

At this point you'd need to put together a plunkr and try to isolate the bug. Then we can take a look at it.

[homanchou]

http://plnkr.co/edit/DoaIBqK1JMqbTJj3vlmH?p=preview

[homanchou]

Looks like it's a known issue?

#212

I have implemented the state mock method mentioned in that issue. It appears to works for now, it bypasses kicking in the actual routing, which would be more of an integration test instead of the desired unit test that I want.

[timkindberg]

Is this a dupe then?

[homanchou]

yes