Member-only story
Page Object Model Is Not Enough: The 4 Layers Real Frameworks Use
By a Staff QA Automation Engineer — for junior QA Engineers, SDETs, and anyone who thinks POM is “the” framework.
Page Object Model is not a complete automation framework. Learn the 4 layers — Driver, Page, Business Actions, and Test — that real enterprise QA automation frameworks use to scale from 20 tests to 2,000.
The Story Every Automation Engineer Knows
Six months ago, Pranta was proud.
He’d just finished building a JavaScript + Playwright framework for his team. Every screen had a clean Page Object class. Locators were neatly separated from test logic. LoginPage, DashboardPage, CheckoutPage—everything looked well organized. Twenty tests, all green. The code review comments? "Nice structure!"
Fast forward to today. The suite has 2,000 tests.
LoginPage has 40 methods, twelve of which do almost the same thing with slightly different parameters. Three different CheckoutPage methods contain near-identical retry logic, copy-pasted because nobody dared touch the "working" one. Every sprint, someone adds business logic — discount calculations, order validation, role-based checks — directly inside a page class, because "that's where the login stuff already lives."
