The Page Object Pattern is widely known and used amongst Test Automation Engineers. It allows engineers to model the application for their tests, reusing certain elements, making the test solution more structured and hence decreasing maintenance cost and the learning curve of test automation.

Working at large fintech and other companies, Peter came to realize that, for some, Page Object is not intuitive. From a tester’s point of view it could be improved. Moreover, it breaks the Single Responsibility principle, which has been one of its most criticized flaws.

That’s why the Flow Model pattern was created.

In this approach the structure of the application (Page Models) is separated from the logic (Flow Models). All the user flows are stored in these new models creating a facade over the page objects.

In this session, Peter will go through the technical details comparing the two approaches, how the Flow Model offers solutions to the Page Object’s problems, and how it is easier for testers applying this architecture design. Peter will give examples to help the audience pick the right approach for themselves.

Language: English

Sign up