-
Notifications
You must be signed in to change notification settings - Fork 69
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 flakiness while creating a page with the checkout block #10340
Conversation
Test the buildOption 1. Jetpack Beta
Option 2. Jurassic Ninja - available for logged-in A12s🚀 Launch a JN site with this branch 🚀 ℹ️ Install this Tampermonkey script to get more options. Build info:
Note: the build is updated when a new commit is pushed to this PR. |
Size Change: 0 B Total Size: 1.28 MB ℹ️ View Unchanged
|
…c/woocommerce-payments into dev/10339-wcb-checkout
…c/woocommerce-payments into dev/10339-wcb-checkout
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 working on this fix, Eduardo! Everything looked good but as noted in our p1739194864927739/1738846788.754599-slack-C01B8KNUYSW, we uncovered some weird behavior when running all three specs in a row. The additional changes to fix that weird behavior look to be working as I'm now getting consistent passing tests.
LGTM!
Fixes #10339
Changes proposed in this Pull Request
This PR aims to prevent possible flakiness in the tests that create a page with WC blocks checkout. The idea is that the action of clicking on the button to open the right sidebar can interfere with the action of searching for the checkout block, causing the test to fail.
Testing instructions
npm run test:e2e shopper-wc-blocks-checkout-failures.spec
— the tests should passnpm run test:e2e shopper-wc-blocks-checkout-purchase.spec
— the tests should passnpm run test:e2e shopper-wc-blocks-saved-card-checkout-and-usage.spec
— the tests should passnpm run changelog
to add a changelog file, choosepatch
to leave it empty if the change is not significant. You can add multiple changelog files in one PR by running this command a few times.Post merge