-
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 the E2E Tests Atomic workflow #10290
base: dev/10240-update-npm-scripts
Are you sure you want to change the base?
Fix the E2E Tests Atomic workflow #10290
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.36 MB ℹ️ View Unchanged
|
…to dev/10239-atomic-workflow
Remove log line from Playwright config
…ttic/woocommerce-payments into dev/10239-atomic-workflow
…ttic/woocommerce-payments into dev/10239-atomic-workflow
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.
Great team work @eduardoumpierre and @allie500! 🚀 The code changes look good to me, and the action runs without issues.
I'd like to know more about why we need things like ensureCustomerIsLoggedIn
or adding articles by its name. Is only due to Atomic? 🤔
Hey @ismaeldcom! Thank you for reviewing this PR!
Yes, we encountered some issues where, potentially due to an error, the browser would lose its context. This caused subsequent tests that relied on a specific user context to fail as well. To address this, we implemented that function to mitigate the issue and ensure more reliable test execution.
Could you please clarify this part? |
Sure! I meant this commit. I know that there were some local issues before, but I would like to know if you've found it happening constantly for any reason. I'm just wondering if this solution might lead to the same problem because it relies on the page number. Maybe we can use the slug to navigate directly to the product page. Anyway, not a concern, just curiosity 🙂 |
Fixes #10239
Fixes #10260
Changes proposed in this Pull Request
Testing instructions
dev/10239-atomic-workflow
npm 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