-
Notifications
You must be signed in to change notification settings - Fork 21
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
Fix E2E test when using RC #2393
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.
Hey @puntope, thanks for working on a fix to resolve the E2E test error.
The way WooCommerce is installed on the E2E environment was recently changed in #2362 to address an issue with the installation order and WooCommerce plugin dependency.
As these changes revert what was done is this not going to re-introduce problems?
Hi @martynmjones thanks for the feedback. I thought the falling tests were because of another issue (I did a fix here https://github.com/woocommerce/google-listings-and-ads/compare/fix/e2e-tests) But you're right that this might reproduce that issue you mentioned #2362 . So I tweaked the PR so I activated the extension also in wp-env Now the tests failing should be only the ones here https://github.com/woocommerce/google-listings-and-ads/compare/fix/e2e-tests Can we test again? |
Avoid running malicious inputs as shell commands in the GitHub Actions
Sorry, @puntope and @martynmjones
Reverted in 7564eb8. |
…ious-input" This reverts commit ad30181, reversing changes made to eb50e5d. Ref: #2393 (comment)
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.
Thanks for adding the extra precaution against the plugin dependency error @puntope.
Tested again and all looks good now ✅
Changes proposed in this Pull Request:
When testing E2E for WC 8.9.0-rc.1 I saw the E2E tests were failing because the workflow was not able to deactivate WooCommerce.
After investigating. Seems like this is happening because the way we load and install WooCommerce in our wp-env. This PR updates the logic to install WC in the
test-env-setup.sh
file.Replace this with a good description of your changes & reasoning.
Screenshots:
Before
After
Detailed test instructions:
npm run wp-env:up
npm run -- wp-env run tests-cli -- wp plugin update woocommerce --version=8.9.0-rc.1
npm run wp-env:up
npm run -- wp-env run tests-cli -- wp plugin update woocommerce --version=8.9.0-rc.1
Additional details:
Changelog entry