architecture

Structure scalable Page Object Models by adopting a layered POM skeleton that separates tests, pages, and config directories. This approach organizes test context and shared fixtures across roles to enforce consistency and maintainability.

Use a context-sharing decision tree to determine when to share or isolate test fixtures across roles. Following documented rules for shared versus isolated contexts prevents inconsistent test states and ensures reliable UI test execution.

Adopt the Role<Role><Page>Page naming convention for role-based Page Object classes. This standardizes base-class guidance and class-level sharing patterns, making new roles easier to implement and maintain across projects.

Add a new user role by following step-by-step patterns for role-based test flows and class-level sharing. Use the provided POM skeleton to implement the role's specific pages and integrate them with the shared test context.

Layered POM design improves UI test maintainability by separating page interactions, test logic, and configuration. This structured approach prevents fragmented Page Object patterns and enforces consistency across QA teams.

No specific testing framework is required to implement a canonical POM skeletal layout. The guidance applies to organizing tests, pages, and config directories within any UI automation framework to achieve scalable test context.