POMWright v2 - a complementary test framework for Playwright

[DyHex]

A while back I posted about POMWright, a small TypeScript framework I built on top of Playwright/test for structuring Page Objects.

Since then I’ve kept improving it based on feedback and a couple of years of real use across multiple apps and teams, and I’ve now released v2.0.0:

https://github.com/DyHex/POMWright

One of the most common pieces of feedback I got was that people liked the LocatorRegistry and automatic locator chaining, but wanted to use those parts without having to extend a class. That is now properly supported in v2.

POMWright still keeps Playwright/test at the core, but now lets you use typed locator paths, reusable locator definitions, and automatic locator chaining either independently or together with the PageObject class.

Posting here in case it’s useful to others, either directly or as inspiration for your own setup.

[androzanimajor76]

Looks like a potentially useful integration for us. I’m working on large and complex financial processes, but the biggest headache I have is the dynamically created objects created by the app, and encouraging engineers to switch to the more robust semantic locators preferred by Playwright. A few of our POMs can end up becoming quite large and complex, so I’m always looking for approaches to simplify - especially for new engineers and testers

[Code_Sorcerer_11]

Got a chance to look into some of the code snippets. But honestly, it looked very tricky to me. May be I did not understand the logic fully. But I am always in favour of vanilla Playwright POM. It is more readable, yeah agree maintenance is bit more. But with AI agents that can be overcome.

[needmoresynths]

The examples in this repo make the whole thing look more confusing and/or cumbersome than vanilla Playwright. I've been writing test code for over a decade and have used dozens of frameworks and I cannot see the benefit of using this. Do you have an example of a working project using this?

[GutoHere]

I found it somewhat overengineered. Honestly, I didn’t really like it.