feat: catch resolve errors

Adds a try/catch around the route resolution to simplify testing scenarios where the developers use `router.push({name: 'hey'})` and do not want to declare the corresponding route, as they just want to check if `push` was called.

Fixes #41

Author: cexbrayat

__tests__/navigations.spec.ts

@@ -17,6 +17,14 @@ describe('Navigations', () => {
     expect(wrapper.vm.$router.push).toHaveBeenCalledTimes(1)
   })
 
+  it('can check calls on push even if the route is not declared', async () => {
+    const wrapper = mount(Test)
+
+    wrapper.vm.$router.push({ name: 'hey' })
+    expect(wrapper.vm.$router.push).toHaveBeenCalledWith({ name: 'hey' })
+    expect(wrapper.vm.$router.push).toHaveBeenCalledTimes(1)
+  })
+
   it('can check calls on replace', async () => {
     const wrapper = mount(Test)
 

src/router.ts

@@ -191,8 +191,13 @@ export function createRouterMock(options: RouterMockOptions = {}): RouterMock {
       return pendingNavigation
     }
 
-    // NOTE: should we trigger a push to reset the internal pending navigation of the router?
-    router.currentRoute.value = router.resolve(to)
+    // we try to resolve the navigation
+    // but catch the error to simplify testing and avoid having to declare
+    // all the routes in the mock router
+    try {
+      // NOTE: should we trigger a push to reset the internal pending navigation of the router?
+      router.currentRoute.value = router.resolve(to)
+    } catch (e) {}
     return Promise.resolve()
   }