The nearest I could find was What is page object modelling? and Why is it so important? ... which is over 6 years old and has less than 500 views.

Is there a better one to refer to, or could some folks with more experience using POM provide some more canonical answers there? I considered putting a bounty on that question to solicit canonical answers but wanted to make sure there wasn't already a better question around.

Part of why I'm asking is I've been playing around with Cypress.io, and their dev team seems to not quite grasp the actual benefits of the pattern (and therefore doesn't appear to put much effort or interest into supporting it). E.g. this seed question by one of their devs on SO and this answer in their FAQ.

I've seen plenty of experts here talk about the importance of POM for writing maintainable UI tests, but those responses are scattered throughout the site. It would be nice to have a canonical link to point at when advocating for supporting this pattern as a first-class citizen, and I imagine it would be useful in many other scenarios as well.


2 Answers 2


I think this is an excellent idea.

You're more than welcome to create a canonical question with references to some of the answers scattered through the site and pull in your own answer, if nobody else does it before you (particularly since you've obviously searched for a canonical answer).


Page Objects make specifications readable and maintainable.

Good code is easily to read and change. Page objects help that happen.

  • And the tooth fairy leaves me a dollar every time I put a tooth under the pillow.
    – kratos
    Jan 10, 2019 at 15:23
  • 1
    Not sure what you mean here. I've used Page Objects for all object identifiers in 4 jobs in a row and it has helped make specs easy to maintain. Are you saying you think that is just a dream? Jan 10, 2019 at 19:22

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .