-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Site editor: Fix e2e tests navigation panel #26454
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.
Do we want to update the "Front page" string in packages/e2e-tests/specs/experiments/multi-entity-saving.test.js:209
as well?
I ran both tests locally. The multi-entity editing test is still passing 🎉 I'm curious though -- did you happen to run into any problems with I'm pretty certain the issue is something with my local testing environment because of the nature of the error and the fact that it's passing without issue in Github Actions, but I was wondering if you saw anything similar. Either way, +1 when my question about "Front page" in |
09578ee
to
fdd4919
Compare
Gotcha! Updated that as well. Thanks!
E2E tests aren't working for me locally at all 😄 |
Size Change: 0 B Total Size: 1.2 MB ℹ️ View Unchanged
|
Is your current workflow to wait for github actions jobs to pass? 😿 If you ever need evaluated quickly, feel free to ping me if you see me online. I'm happy to checkout your branches for a little bit and run tests locally until you you get your e2e testing environment ironed out 🙂 |
These axe-core error failures look unrelated as they seem to be happening on all PRs currently. It looks like the axe is having problems injecting into the iframe / block previews (and does it even make sense for it to be since it is a disabled preview in the first place). 🤔 |
Also noting that the changes like 'Front Page' don't seem to fix any failures that I am able to reproduce locally or seeing on current CI checks? 🤔 These e2e's are a pain. |
Yes 😅
Thank you! I will ping you next time!
I saw an E2E test fail on one of the PRs that said it can't find the |
Yeah. I have seen that before as well. I cant get consistent results from either CI or local though, which is strange. You think it would fail consistently? Either way, the changes here still make sense to me. |
I think it should fail consistently, since XPath is case sensitive. But I can't say it for sure since E2E tests are kinda unreliable 😅 |
I wasn't able to have it fail in my local environment. I do, however, remember seeing the failure that you're describing pop up non-deterministically (it resolved itself on a rerun). I agree with Addie. I'd expect this spec to fail consistently as well. The changes make sense either way, and my hope is that they solve the non-deterministic failures. |
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.
Changes make sense to me.
Description
Change template name in E2E to match the current naming.
Types of changes
Bug fix
Checklist: