Closed staszek998 closed 11 months ago
That's a known problem, see a related one https://github.com/quasarframework/quasar-testing/issues/196
It boils down to not knowing wheter the end user tampered with the default port, and not having a simple way to act upon that manual change We're open to PRs, but the only thing which comes to my mind right now is just to add a disclaimer on the documentation
In the upcoming new version we'll force the devServer to use 8080
port to unify the usage among different build targets
Software version
What did you get as the error?
Running the
npm run test:e2e
command does NOT open the Cypress runner. The process hangs on the very beginning, just after the initialization of the Quasar's dev server, waits for some time, and finally outputs the following message:What were you expecting?
I expected the Cypress runner to pop-up.
What steps did you take, to get the error?
npm init quasar
devServer.port
property inside thequasar.config.js
file to any value different from the default one (default is9000
). Example values to reproduce the bug:9001
,8080
,3000
.quasar ext add @quasar/testing
package.json
npm run test:e2e
ornpm run test:e2e:ci
command (it doesn't matter which one, the effect is exactly the same).Current workaround
Update the body of the
test:e2e
andtest:e2e:ci
scripts so they use the correct dev server port. For example, when you set thedevServer.port
property value to3000
, your scripts should look like this:Likewise, when you set the
devServer.port
property value to9001
, your scripts should be updated accordingly: