Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mockNuxtImport unable to test for useRouter #975

Closed
cheesypeperoni opened this issue Oct 11, 2024 · 2 comments
Closed

mockNuxtImport unable to test for useRouter #975

cheesypeperoni opened this issue Oct 11, 2024 · 2 comments

Comments

@cheesypeperoni
Copy link

I have a router.push in my store, its working completely fine and im able to navigate accordingly

Image

However when i try running test to it using vitest, it shows router not found. from what i see it actually couldnt read the "instance" of my router from my store.

i have this at the top of my file


  beforeEach(() => {
    setActivePinia(createPinia())

    mockNuxtImport('useRouter', () => {
      return () => {
        return mock<Router>()
      }
    })
  })

and then

    it('will navigate user to Route.dashboard upon logging in', async () => {
      const authStore = useAuthStore()
      const router = useRouter()

      expect(router.push).not.toHaveBeenCalled()

      await authStore.login({
        username: emailUsername,
        password,
      })

      expect(router.push).toHaveBeenCalledOnce()  // !! HERE is not found. any idea what might be the issue
     })
Copy link
Contributor

Would you be able to provide a reproduction? 🙏

More info

Why do I need to provide a reproduction?

Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making.

What will happen?

If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritise it based on its severity and how many people we think it might affect.

If needs reproduction labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it.

How can I create a reproduction?

We have a couple of templates for starting with a minimal reproduction:

👉 https://stackblitz.com/github/nuxt/test-utils/tree/main/examples/app-vitest
👉 https://stackblitz.com/github/nuxt/test-utils/tree/main/examples/app-jest
👉 https://stackblitz.com/github/nuxt/test-utils/tree/main/examples/module

A public GitHub repository is also perfect. 👌

Please ensure that the reproduction is as minimal as possible. See more details in our guide.

You might also find these other articles interesting and/or helpful:

Copy link
Contributor

github-actions bot commented Nov 1, 2024

This issue was closed because it was open for 7 days without a reproduction.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants