This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
[✨] Add qwik add command for WebdriverIO #81
Labels
[STAGE-2] incomplete implementation
Remove this label when implementation is complete
[STAGE-2] not fully covered by tests yet
Remove this label when tests are verified to cover the implementation
[STAGE-2] unresolved discussions left
Remove this label when all critical discussions are resolved on the issue
[STAGE-3] docs changes not added yet
Remove this label when the necessary documentation for the feature / change is added
[STAGE-3] missing 2 reviews for RFC PRs
Remove this label when at least 2 core team members reviewed and approved the RFC implementation
Is your feature request related to a problem?
Providing Playwright as the only solution for e2e testing suggests people it is fine to run tests in browser engines (some of which even modified) which by no means comes close the real browser and many folks have interest in testing in the browser that their users use.
There are whole talks about why testing in a browser engine is just not the same as testing in real browser: https://www.youtube.com/watch?v=Mo6LmFGrtxY
Describe the solution you'd like
Similar to QwikDev/qwik#1926 I would love to help extend the qwik CLI to support the ability to use WebdriverIO.
Describe alternatives you've considered
n/a
Additional context
I am maintaining WebdriverIO and help at the W3C to move standards for browser automation forward. I am disappointed to see that frontend frameworks just go with the "popular" tool and disregard the development of the web platform. I am happy to step in and do the leg work. In my opinion Qwik deserves to be tested in real browser on desktop and mobile, powered by web standards and users should at least have the option to decide which tool to use.
The text was updated successfully, but these errors were encountered: