Closed Rogeriohsjr closed 8 months ago
Hey there, thanks for the PR! I noticed you're using the Vue CLI, but you're not using the Quasar Vue CLI plugin: https://quasar.dev/start/vue-cli-plugin
It shouldn't change anything for Cypress setup, but it changes something for the normal vue-cli setup, simpifying the setup
Can you update the project to use that instead?
I'd also avoid the nested forlder cypress-component-test
and just install the project into test-vue-cli
folder
Hey @IlCallo , thanks, I was wondering what did you see that says it wasn't created by Quasar Vue CLI? I am wondering that because I am pretty sure I did add quasar using the "vue add quasar", which is the step in the doc that you shared. I can try again
Sure, I can move that to not be nested.
I just thought that would be confusing because if each different installation vue has it could have a different setup, and have a folder which doesn't say the type of installation could be confusing.
Ah, my bad, I missed some files while reviewing, that's correct indeed I only changed the lock file to use yarn, which is what the whole repo is using
What kind of change does this PR introduce? (check at least one)
If you are adding a new test runner, have you...? (check all)
/packages/base/runners.json
?/README.md
?baseline.spec.vue
?Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
dev
branch and not themaster
branchfix: #xxx[,#xxx]
, where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information: