[Feature] Component testing and page.goto

Context:

• Playwright Version: 1.24.0
• Operating System: All
• Node.js version: v17.3.0
• Browser: Chromium
• Extra: Vue component testing

I’ve been playing with the Vue component testing feature and it seems like the page.goto() is not working properly.

For example i have a failing test that should be passing.

It should navigate to the 404 page because i have a catch all specified /:pathMatch(.*)* inside Vue router see the code here.

The Vue router plugin is registered here.

Here you can see another example that also uses the page.goto function that i can’t get to work.

[sand4rt]

Thanks for explaining! Yes, makes sense. Yeah i believe it’s either history mode or hash mode.

The first use case/test is works!

Navigating before mount doesn’t work yet. I need to debug it a little further.

Don’t you think that the API for navigating in SPA’s is a bit too verbose? I think the config.use.baseURL setting is not respected when using page.evaluate(() => window.history.....) as well right?

Why not something like?:

page.goto('/route-not-exsist', { mode: 'history' })

[sand4rt]

I don’t think a link is the only contract. Users are able to type the url in the browsers address bar as well (aka page.goto). imo we should be able to mimic the user’s behaviour even if this reloads the JS state.