Repository navigation
Conversation
…ance when switching environments
…undant page objects
…t restrictive feature grep
…test repeatability
- Seed a shop_manager user and expose managerPage fixture/credentials - Flush rewrite rules after direct add-on config writes - Count post rows directly so disabled add-ons still report data
b-l-i-n-d
marked this pull request as draft
October 22, 2026 16:55
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Testing
pnpm e2e:fullagainst a fresh wp-env container and confirm the suite starts without a restrictive feature grep.pnpm e2e:proand confirm the Pro project resolves the shared config and factories.beforeAll/afterAllrestores the previous enabled state with no leakage into neighbouring specs.tsc --noEmiton changed TypeScript.