Test: Fix E2E import/export tests for WP 6.2 compatibility #348
+905
−279
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Follow-up to #345 to fix E2E test failures on WordPress 6.2.
Why
The import/export E2E tests were failing on WP 6.2 due to Playwright strict-mode violations. The locator used matched two elements on WP 6.2 (which displays an additional core warning notice), but only one element on newer WordPress versions.
How
Using
.filter({ hasText: ... })to target the specific SCF warning notice by its expected text content rather than relying on element order. This approach is more robust because it explicitly targets the notice we care about, regardless of how many notices are present on the page.Testing Instructions
.wp-env.override.jsonwith{"core": "WordPress/WordPress#6.2"}npm run wp-env startnpm run test:e2e tests/e2e/import-export.spec.ts