You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your enhancement related to a problem? Please describe.
Coming out of #611, there were some failing E2E tests on trunk only. In looking at most of those, they were issues with the openDocumentSettingsSidebar command that comes from our Cypress WP Utils library. My assumption is something has changed within the Block Editor and that command needs updated to account for that change.
Since this is an upstream fix, I disabled the running of E2E tests on trunk for now. As soon as that upstream change is made though, we should open a PR to pull in those changes and re-enable the tests, fixing any other issues that we may find at that point.
Designs
No response
Describe alternatives you've considered
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Note that I'm moving this out of the v3 milestone assuming that if WP 6.4 and 6.2 (ClassifAI's current max and min WP versions) are passing for e2e tests, then that's the important bits for a v3 release. WP 6.5 isn't due out for almost 2 months, so we've got a bit more time to sort out why WP trunk is failing on e2e tests and get that fixed but I don't think we need to block the v3 release in resolving that.
Is your enhancement related to a problem? Please describe.
Coming out of #611, there were some failing E2E tests on
trunk
only. In looking at most of those, they were issues with theopenDocumentSettingsSidebar
command that comes from our Cypress WP Utils library. My assumption is something has changed within the Block Editor and that command needs updated to account for that change.Since this is an upstream fix, I disabled the running of E2E tests on
trunk
for now. As soon as that upstream change is made though, we should open a PR to pull in those changes and re-enable the tests, fixing any other issues that we may find at that point.Designs
No response
Describe alternatives you've considered
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: