Do You Still Need Page Objects? | Bondar Academy

Lesson Summary

Key Question: In the age of AI agents, do we still need to use page objects in test automation? The speaker reflects on their extensive use of page objects across various frameworks, including Selenium with Java and C# , Cypress with JavaScript , and Playwright with TypeScript . Traditionally, page objects were created to simplify code organization and reuse, making development and maintenance faster. Why Page Objects Were Used: Facilitated code reuse through abstractions. Streamlined the maintenance process by allowing updates in one place to affect multiple tests. Enhanced readability and organization of test scripts. However, with the advent of AI agents, the need for page objects is being questioned. The speaker argues that: AI agents handle code generation, reducing the necessity for manual coding. Validation of results becomes the main bottleneck, shifting focus away from page objects. Reviewing tests organized in page objects can be more complex and time-consuming. Examples and Comparisons: Using a practical example, the speaker contrasts traditional page object-based tests with AI-generated tests. The latter allows for: Faster creation and review of tests. Direct interaction with user-visible locators and actions. Efficient updates through AI assistance without manual intervention. In conclusion, the speaker posits that as we move into a new era of test automation, the reliance on page objects may become obsolete, allowing engineers to focus on more complex tasks such as user management and test data handling.