Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Can you keep Cypress as an option for e2e testing? #43

Open
glyad opened this issue Jun 21, 2022 · 1 comment
Open

Can you keep Cypress as an option for e2e testing? #43

glyad opened this issue Jun 21, 2022 · 1 comment

Comments

@glyad
Copy link

glyad commented Jun 21, 2022

I use Cypress for e2e testing last 3 years. Why do not keep Cypress as one of the options?

In addition, I would be very glad to add options to use Cucumber both with Cypress and with Playwright. I just built the template using Cypress(10)-TS-Cucumber. If need, I can contribute it.

@3cp
Copy link
Member

3cp commented Jun 21, 2022

Sorry about that.
https://discourse.aurelia.io/t/playwright-or-cypress-for-aurelia-2-and-1/4807/7

We had difficulty to keep up with cypress's breaking changes over the years (I don't know why cypress needs to make so many breaking changes). And there are some random errors on CI we need to bypass too.

However, I gave a branch name for previous cypress skeleton. You can still access the branch through

npx makes aurelia/v1#cypress

FYI, au new just calls npx makes aurelia/v1 internally.

Cucumber is welcome, as long as it's not flaky for CI.

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

No branches or pull requests

2 participants