![[The AI Show Episode 143]: ChatGPT Revenue Surge, New AGI Timelines, Amazon’s AI Agent, Claude for Education, Model Context Protocol & LLMs Pass the Turing Test](https://www.marketingaiinstitute.com/hubfs/ep%20143%20cover.png)
![[Tutorial] Chapter 9: Task Dashboard: Charts](https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fnotu3uxqtwmann665q6r.png)
![[Tutorial] Chapter 10: Task Dashboard (Part 2) - Filter & Conditions](https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ffjbdyeaw51nx8g13ag12.png)
![From drop-out to software architect with Jason Lengstorf [Podcast #167]](https://cdn.hashnode.com/res/hashnode/image/upload/v1743796461357/f3d19cd7-e6f5-4d7c-8bfc-eb974bc8da68.png?#)
.jpg?#)
_ArtemisDiana_Alamy.jpg?#)
 (1).webp?#)
-xl.jpg)
![Yes, the Gemini icon is now bigger and brighter on Android [U]](https://i0.wp.com/9to5google.com/wp-content/uploads/sites/4/2025/02/Gemini-on-Galaxy-S25.jpg?resize=1200%2C628&quality=82&strip=all&ssl=1)
![Apple Rushes Five Planes of iPhones to US Ahead of New Tariffs [Report]](https://www.iclarified.com/images/news/96967/96967/96967-640.jpg)
![Apple Vision Pro 2 Allegedly in Production Ahead of 2025 Launch [Rumor]](https://www.iclarified.com/images/news/96965/96965/96965-640.jpg)
Page objects vs Functional helpers
The debate on Page Object vs module pattern is really just Inheritance vs Composition. Inheritance (PO) is great for describing what something is; the page has x, y, z on it. Composition (module pattern) is great for describing what something does. Which one do you think best fits component based architecture, where components are the building blocks and get reused on pages? How about user flows? Components compose and if the pages which are built of components are abstracted with classes, there's over-abstraction and inevitable duplication In modern testing frameworks like Playwright and Cypress, strict Page Object Model (POM) can feel overkill, especially when: • You’re using data selectors (data-qa, data-cy) for stable locators. • The tools already offer powerful, built-in utilities for interacting with the UI. • You don’t need unnecessary abstraction layers that make debugging harder. 1️⃣ Unnecessary Abstraction • POM adds an extra layer that often doesn’t provide real value. • Modern test frameworks are already powerful enough without it. 2️⃣ Base Page Inheritance is Overkill • Having a BasePage class with generic methods (click(), fill()) just to wrap Playwright’s own API makes no sense. • Playwright already has page.locator(), page.click(), page.fill(), etc. 3️⃣ Harder Debugging • With POM, if a test fails, you often have to jump between multiple files to find what went wrong. • With direct helper functions, you see exactly what’s happening.
The debate on Page Object vs module pattern is really just Inheritance vs Composition. Inheritance (PO) is great for describing what something is; the page has x, y, z on it. Composition (module pattern) is great for describing what something does. Which one do you think best fits component based architecture, where components are the building blocks and get reused on pages? How about user flows?
Components compose and if the pages which are built of components are abstracted with classes, there's over-abstraction and inevitable duplication
In modern testing frameworks like Playwright and Cypress, strict Page Object Model (POM) can feel overkill, especially when:
• You’re using data selectors (data-qa, data-cy) for stable locators.
• The tools already offer powerful, built-in utilities for interacting with the UI.
• You don’t need unnecessary abstraction layers that make debugging harder.
1️⃣ Unnecessary Abstraction
• POM adds an extra layer that often doesn’t provide real value.
• Modern test frameworks are already powerful enough without it.
2️⃣ Base Page Inheritance is Overkill
• Having a BasePage class with generic methods (click(), fill()) just to wrap Playwright’s own API makes no sense.
• Playwright already has page.locator(), page.click(), page.fill(), etc.
3️⃣ Harder Debugging
• With POM, if a test fails, you often have to jump between multiple files to find what went wrong.
• With direct helper functions, you see exactly what’s happening.
