-
Notifications
You must be signed in to change notification settings - Fork 481
cypress not running after server start #96
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
Comments
With the proposed solution, cypress opens, but the default test fails. To fix this problem, I ran |
I just tried a fresh project with the same exact options, using
And opening the localhost link in a browser, it shows |
if the tests don't start, it's probably because your |
Ah I didn't realize I had to change that too, thanks. So I changed it to Anyway with that, and building the app before running the test per @Tommytrg , the e2e tests worked. But I guess since it relies on building the app, that means hot-reloading with e2e wouldn't work? Seems like something's missing here. For context, I was just playing around with create-vue because I saw that they (just recently?) started officially recommending it, but it seems odd that one of the huge functionalities of it wouldn't work out of the box. And fwiw I'm on an M1 Mac with Monterrey, a common-enough developer platform I think. Seems like I'll probably stick with Vue CLI for now until this matures more. |
create-vue why not use playwright ? |
Hi @jeremyriverain, When I adjusted the following code, it can work.
|
This is due to the subtle differences between
This is expected because I believe end-to-end tests should run against the production build to better match the real-world environment. On the other hand, it is a pain point that the feedback loop would be too long with So in the most recent release, I added a
The latest release has added a Playwright option alongside Cypress. |
Hi,
I just created a Vue app using the
npm init vue
command.When I run the
test:e2
andtest:e2e:ci
commands on my machine, Cypress does not run after starting the server.These errors are fixed when I replace
http://127.0.0.1:5050/
withtcp:5050
intest:e2e
andtest:e2e:ci
scripts.This means replacing:
with:
fixed these errors.
Do you agree ? Can I create a pull request to fix this error?
The text was updated successfully, but these errors were encountered: