Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Support for Vite? #1000

Closed
flowt-au opened this issue Apr 17, 2023 · 5 comments
Closed

Support for Vite? #1000

flowt-au opened this issue Apr 17, 2023 · 5 comments

Comments

@flowt-au
Copy link

I am wondering if there is any progress on supporting Vite? I see this issue related to component testing has been dormant for a year.

I have a Quasar 2 (Vue3) Vite project that works with Cypress e2e testing. I would now like to use this cucumber plugin which I was able to do with previous Vue 2 projects.

Any thoughts?
Thanks,
Murray

@badeball
Copy link
Owner

You need to

  • use the existing issue for questions about the issue
  • further explain why vue2 works and vue3 doesn’t

@flowt-au
Copy link
Author

Ok, Ta.

  1. The existing issue seems to be about component testing Cucumber with Vite (which, if I understand it, doesn't yet work). I am interested to know about Cucumber Vite e2e testing.
  2. Quasar with Vue 2 used Webpack. Quasar with Vue 3 offers Vite. Vue 2 worked because webpack is supported. I am wondering whether Vite is supported because as I mentioned, that is what I am using: Quasar on top of Vue3 using Vite.

It might well be that I am missing something and can use one of your examples, but I cannot see one that will work with Vite.

Thanks for taking over this project. BDD is, IMO, a great way to go.

Cheers,
Murray

@flowt-au
Copy link
Author

PS: I got a possible answer here: https://stackoverflow.com/questions/76030846/how-to-get-cypress-cucumber-preprocessor-working-with-quasar-2-vue-3-and-vite/76032632#76032632. I will close this issue once I check it out.
Thanks again.

@badeball
Copy link
Owner

There's no reason for you to think that you need Vite support in the preprocessor just because you're testing a Quasar application, assuming we're talking about E2E testing. What bundler you chose to bundle your tests simpy isn't affected by the test subject. I think you're misunderstanding something here.

@flowt-au
Copy link
Author

@badeball Yes, you are correct, I was misunderstanding that the test bundler needed to match the dev bundler. I now have it working as per the SO answer

Thanks for your help. :-)

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants