router.push could be a simple mock functions by default?

What problem is this solving

For a component doing a navigation with router.push({ name: 'home' }); on an action, our associated unit test usually does a simple assertion like the following:

const mockRouter = createRouter({ history: createWebHistory(), routes: [] });
jest.spyOn(mockRouter, 'push').mockResolvedValue();
const wrapper = mount(App, {   global: { plugins: [mockRouter] } });
// do the action
expect(mockRouter.push).toHaveBeenCalledWith({ name: 'home' });

Using vue-router-mock, we can simplify the test a bit by using createRouterMock:

// do the action
expect(getRouter().push).toHaveBeenCalledWith({ name: 'home' });

but the mock router created tries to really resolve the navigation and throws:

Error: Uncaught [Error: No match for {"name":"home","params":{}}]

Proposed solution

Would it be possible to have a simpler router mock that just have mock functions by default? Most use cases would probably not need a real navigation to be resolved and triggered. Or maybe that could be an option?

Describe alternatives you’ve considered

It’s of course possible to spy on getRouter().push but I feel that this should be the default.

[cexbrayat]

I followed your idea and opened #53

I tried a patched version in our projects, and it does simplify our tests quite a bit 👍

[posva]

It shouldn’t be skipped because it normalizes the route location and also to simulate how the router changes the current route by affecting the whole route also, and this should be respected because it won’t trigger the same watchers, making a test fail while the actual code works