-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Add cypress as e2e tests framework #12210
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you should not remove protractor tests and keep both while cypress is not a full replacement.
We are moving all scenario tests from Protractor to Cypress and plan to deprecate Protractor. |
...ss/templates/src/test/javascript/cypress/integration/account/reset_password_page_spec.ts.ejs
Outdated
Show resolved
Hide resolved
.../cypress/templates/src/test/javascript/cypress/integration/account/settings_page_spec.ts.ejs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My biggest issue is the naming convention used for data-cy
...r/src/main/webapp/app/account/password-reset/finish/password-reset-finish.component.html.ejs
Outdated
Show resolved
Hide resolved
...rs/client/templates/angular/src/main/webapp/app/account/password/password.component.html.ejs
Show resolved
Hide resolved
...rs/client/templates/angular/src/main/webapp/app/account/settings/settings.component.html.ejs
Outdated
Show resolved
Hide resolved
...t/templates/angular/src/main/webapp/app/admin/configuration/configuration.component.html.ejs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work, really impressive !
Just an additional general comment: One thing that is troubling me a bit is some coupling between tests, that rely on the state of another test. It is not recommended in Cypress best practices: https://docs.cypress.io/guides/references/best-practices.html#Having-tests-rely-on-the-state-of-previous-tests
...rs/client/templates/angular/src/main/webapp/app/account/register/register.component.html.ejs
Outdated
Show resolved
Hide resolved
.../templates/src/test/javascript/cypress/integration/administration/administration_spec.ts.ejs
Outdated
Show resolved
Hide resolved
...ors/cypress/templates/src/test/javascript/cypress/integration/account/login_page_spec.ts.ejs
Outdated
Show resolved
Hide resolved
generators/cypress/templates/src/test/javascript/cypress/support/keycloak-oauth2.ts.ejs
Outdated
Show resolved
Hide resolved
generators/cypress/templates/src/test/javascript/cypress/support/keycloak-oauth2.ts.ejs
Outdated
Show resolved
Hide resolved
...ss/templates/src/test/javascript/cypress/integration/account/reset-password-page_spec.ts.ejs
Outdated
Show resolved
Hide resolved
.../cypress/templates/src/test/javascript/cypress/integration/account/settings-page_spec.ts.ejs
Outdated
Show resolved
Hide resolved
.../templates/src/test/javascript/cypress/integration/administration/administration_spec.ts.ejs
Outdated
Show resolved
Hide resolved
I agree with and that's why I reworked the register spec file. We plan to do the same with other tests, avoid tests to be dependent from others. If you are ok @clementdessoude you could check the modifications and tell us if you think the modifications are good enough. |
.../cypress/templates/src/test/javascript/cypress/integration/account/register-page_spec.ts.ejs
Outdated
Show resolved
Hide resolved
.../cypress/templates/src/test/javascript/cypress/integration/account/settings-page_spec.ts.ejs
Outdated
Show resolved
Hide resolved
.../templates/src/test/javascript/cypress/integration/administration/administration_spec.ts.ejs
Outdated
Show resolved
Hide resolved
b5aa926
to
67db059
Compare
We are waiting for #12243 to remove the draft flag. I think all things are done. |
- fix field.js - add faker to all clients package.json if we use cypress
@avdev4j @adilabed @nassimerrahoui : We lost some commits:
We should use git fetch + git merge name/branch, so no work will be lost |
Fixes to cypress entity generator.
Add tests for entity-client part
As the work on Cypress is more important than exepcted (even if I think we are close to finish it), we merge this PR on a new Cypress branch. Every further modifications would be done from this branch. When we'll decide, the cypress branch will be merged into the master one. At least we need to:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work everyone.
It looks great!
We made it 🥇 |
The last but not least : And I hope we could merge it. GG team ! |
Great. It is now just missing the update to cypress 5 |
We forgot it. Done here jhipster#12298 |
As we struggle a bit with Cypress 5 CI builds, I suggest to merge Cypress 4+ as is and keep working aside on Cypress 5. The goal is to avoid, as much as possible, conflicts between branches. |
#11961
Please make sure the below checklist is followed for Pull Requests.
All continuous integration tests are green
Tests are added where necessary
Documentation is added/updated where necessary
Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed
Migrate or abandon entity tests
When you are still working on the PR, consider converting it to Draft (bellow reviewers) and adding
skip-ci
label, you can still see CI build result at your branch.