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

Migrate to Cypress 11 #205

Merged
merged 11 commits into from
Dec 9, 2022
Merged

Migrate to Cypress 11 #205

merged 11 commits into from
Dec 9, 2022

Conversation

iamdharmesh
Copy link
Member

@iamdharmesh iamdharmesh commented Dec 1, 2022

Description of the Change

This PR upgrades the Cypress version to 11 and updates needed files as part of the migration.

Closes #199

How to test the Change

Make sure PR PASS E2E tests check OR verify E2E tests locally.

Changelog Entry

Changed - Migrated to Cypress 11

Credits

Props @iamdharmesh

Checklist:

  • I agree to follow this project's Code of Conduct.
  • I have updated the documentation accordingly.
  • I have added tests to cover my change.
  • All new and existing tests pass.

@iamdharmesh iamdharmesh marked this pull request as ready for review December 1, 2022 12:04
@github-actions github-actions bot added the needs:code-review This requires code review. label Dec 1, 2022
@iamdharmesh iamdharmesh requested review from a team and Sidsector9 and removed request for a team December 1, 2022 12:04
@iamdharmesh iamdharmesh added this to the 1.3.0 milestone Dec 1, 2022
@@ -25,7 +25,7 @@ jobs:
uses: actions/checkout@v2

- name: Install dependencies
run: npm i && npm i -g cypress@9.0.0
run: npm i && npm i -g cypress@11.2.0
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a specific reason to install Cypress globally instead of using the local version?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We set env vars from repo secrets for a twitter API key and secret. So, directly calling the cypress command in workflow instead of using npm scripts. see here

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Sidsector9 I tried a different approach to setup cypress env variables and removed global cypress installation.

Copy link
Member

@Sidsector9 Sidsector9 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for working on this! LGTM 👍

@iamdharmesh iamdharmesh merged commit 997d3c7 into develop Dec 9, 2022
@iamdharmesh iamdharmesh deleted the upkeep/199 branch December 9, 2022 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs:code-review This requires code review.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Migrate to Cypress 11
2 participants