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
chore(packages/sui-test-e2e): Update Cypress to version 10.2.0 #1431
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.
how about publishing a beta version of sui-test-e2e
so we can try out these changes on local & CI?
Released the version |
In order to test these changes in CI, I've tried to publish a docker image running the beta version, pushed without the I'll keep posting updates here! |
We've published a docker image (with a personal user, just for testing purposes), which name is Thanks a lot to @jordevo for the help during the publishing process π₯ πββοΈ |
Description
π How to test in local: Install the version
1.11.0-beta.1
of@s-ui/test-e2e
package to test these changes.π How to test in CI: Modify the CI job to use the
oegeaadevinta/e2e-test:cypress-10
docker image instead ofsuitools/e2e-test
All of these should be temporary changes, just to check that your e2e tests run as expected after the update.
--
As part of the
end2end reborn
initiative, from the motor vertical, we have concluded that upgrading Cypress to the latest version available could be a good way to improve stability and performance of our end to end tests (among other actions), and additionally a way to get more useful features that aren't available on version8.7.0
.This PR introduces some changes to the
@s-ui/test-e2e
package to adopt the last Cypress version, which is the10.2.0
version.This is still a proof of concept, and we're currently performing some tests to ensure that tests keep working as expected after this changes.
If you want to know more about this action and how it is related with the end2end reborn initiative, please refer to this document
Related to compatibility:
Apparently, there are not breaking changes (we have tested it in coches.net and coches.net pro without modifying anything). However, as a side effect, a basic
cypress.config.js
file will be created on every project updated to Cypress 10. Until now we had theconfigFile
parameter set tofalse
to avoid creating configuration files, however, since Cypress 10, having that file seems to be mandatory.Known Problems:
Related Issue