-
Notifications
You must be signed in to change notification settings - Fork 10.8k
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
Updated wp-env
To 8.0.0
#38440
Updated wp-env
To 8.0.0
#38440
Conversation
Test Results SummaryCommit SHA: c822909
To view the full API test report, click here. To view the full E2E test report, click here. To view all test reports, visit the WooCommerce Test Reports Dashboard. |
Hi @jonathansadowski, @samueljseay, @rodelgc, Apart from reviewing the code changes, please make sure to review the testing instructions as well. You can follow this guide to find out what good testing instructions should look like: |
Hi @samueljseay, Apart from reviewing the code changes, please make sure to review the testing instructions as well. You can follow this guide to find out what good testing instructions should look like: |
The |
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.
The changes look good to me, CI passes (with one expected and acceptable exception), but locally I always have one or two e2e tests fail even after retries. Not sure if that's acceptable / expected / OK so I'd like to hear the perspective from Solaris.
"afterSetup": "./tests/e2e-pw/bin/test-env-setup.sh", | ||
"lifecycleScripts": { | ||
"afterStart": "./tests/e2e-pw/bin/test-env-setup.sh", | ||
"afterClean": "./tests/e2e-pw/bin/test-env-setup.sh" |
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.
Thank you for adding the afterClean
scenario here!
Looking good! I ran the tests and GitHub workflows that are likely to be affected by this change.
Seems like there are conflicts in the PNPM lock file. I'm pre-emptively approving this PR in case the conflict isn't related to the changes here. |
When you run `wp-env clean` it will erase any options that we set automatically. We need to set up the test environment again if this was the case for clean-ness.
7e5e42e
to
c822909
Compare
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.
👍 looks good to me with the noted caveat about the code-analyzer failure being related to this change, which seems low-risk as this PR doesn't change any templates 😄
Submission Review Guidelines:
Changes proposed in this Pull Request:
We are updating
@wordpress/env
to 8.0.0 in order to consume some upstream fixes.wp-env
no longer requires WSL to function.wp-env run
that no longer require us to use quotes (and in fact, break, when we do)How to test the changes in this Pull Request:
Using the WooCommerce Testing Instructions Guide, include your detailed testing instructions:
pnpm --filter=woocommerce env:test
after updating.pnpm --filter=woocommerce test:unit:env
and confirm they pass.pnpm --filter=woocommerce test:e2e-pw
and confirm they pass.