Cypress tests don't work with @quasar/app 1.0.6

Software version

OS: Ubuntu bionic (amd64 flavour) Node: v12.9.1 NPM: 6.10.2 Any other software related to your bug: yarn 1.17.3

What did you get as the error?

I get no error message, but the “npx quasar test --e2e cypress” command will wait forever after building the app and before running my test suite.

Here is the console output :

$ npx quasar test --e2e cypress app:extension Running “@quasar/testing” Quasar App Extension… +0ms app:test Running “@quasar/testing” > “test” command +3ms

Dev mode… spa Pkg quasar… v1.1.0 Pkg @quasar/app… v1.0.6 Debugging… enabled

app:extension Running “@quasar/icon-genie” Quasar App Extension… +0ms app:extension Running “@quasar/testing” Quasar App Extension… +7ms app:extension Running “@quasar/testing-e2e-cypress” Quasar App Extension… +1ms app:quasar-conf Reading quasar.conf.js +4ms app:dev Checking listening address availability (0.0.0.0:8080)… +2ms app:webpack Extending SPA Webpack config +316ms app:dev Extension(@quasar/icon-genie): Running beforeDev hook… +2ms app:extension-manager Updating /quasar.extensions.json for “@quasar/icon-genie” extension … +10s app:generator Generating Webpack entry point +15ms app:dev-server Booting up… +2ms

app:progress Compiling SPA… +214ms app:progress Compiled SPA in ~17s +17s DONE Compiled successfully in 16755ms15:50:41

N App dir… /path/to/my/project App URL… http://localhost:8080 Dev mode… spa Pkg quasar… v1.1.0 Pkg @quasar/app… v1.0.6

After that, all I get is a blinking cursor and no CPU activity.

What were you expecting?

I’m expecting the test suite to run.

What steps did you take, to get the error?

• put “1.0.6” in package.json
• run “npx quasar test -e2e cypress”

Important remarks

1. If I downgrade the @quasar/app package at version 1.0.5 (by putting “1.0.5” without leading ‘^’) and run “yarn install” again, then the test suite works fine.
2. I’ve tried to create a new dummy app (“npx quasar init foo”) + add the testing extension (“npx quasar ext add @quasar/testing”) with Cypress support enabled + add the cypress extension (“npx quasar ext add @quasar/testing-e2e-cypress”). It leads to the same result : the command for running the tests suite “sleeps” forever. So here you have a simple way to reproduce that bug.
3. I don’t know if the issue is linked to this repo, or with the ‘quasar’ repo. It seems to be some incompatibility between @quasar/app 1.0.6 and the current packages from this repo.

P.S. : big thanks for making Quasar. It’s just awesome.

Best regards, Olivier Ricordeau Co-author of https://acompas.org (quasar-based !)

[amfine-soft-drault]

Hi again guys i’ve been thinking about and looking into this issue and i think i’ve found the cause : https://github.com/quasarframework/quasar-testing/blob/dev/packages/testing/src/index.js#L121 this is the regex used to detect if the dev server is up & running const doneRegex = /App URL\.{11} (https?:\/\/localhost:\d{4}\/)/ but looking at my quasar dev output it does NOT match the regex due to the expected trailing / !! i tried removing it from the regex and tests are now executed when server is running const doneRegex = /App URL\.{11} (https?:\/\/localhost:\d{4})/

comments/further analysis would be appreciated : @rstoenescu may be ? of course, i can provide a pull request if needed (though i can’t say i’m familiar with any of the code from quasar-testing…)

best regards

[sgalinanes]

Is there any fix for this issue planned?