quasar-testing

quasar-testing copied to clipboard

When using starttest with http-get I think the devserver should not automatically pick a free port since the http-get will never succeed and you will wait for the timeout. Or, if possible the http-get should then use the same port that the devserver chose.

Do you have any suggestion on how to fix this problem? The quickfix I see is to define a custom port (eg. 9999) when starting quasar dev and ping that one instead I'm not sure it's easily doable to autodetect the port used from quasar dev and ping that one instead (and you may have more than one Quasar instance running) We're open to PRs

I guess @bahmutov or someone from contributors of start-server-and-test might have to handle that like in the helpers/net thing quasar uses to pick a new port. Alternatively, you could run the net helper and then spawn a process for start-server with the final port.

In the upcoming new version we'll force the devServer to use 8080 port to unify the usage among different build targets

Ouch, that will pretty much ruin our cors settings because we use 8088

We could add a prompt and ask the user which port to enforce 🤔 Would that suffice?

I guess so

Implemented in https://github.com/quasarframework/quasar-testing/commit/a33265d1ee753c66b0dbb2f692f853976a0d2484, will be available into next v5.2 release