Topics in July 2022:

• Applying a Design Thinking Prioritization Grid approach into Quality Engineering

• Flow Model vs Page Object Pattern

0

Days

0

Hours

0

Minutes

0

Seconds

The sessions took place on July 6 (Wednesday) from 11AM to 1PM Eastern Time (ET)

You have the opportunity to watch the recording after registering.

Get the media content:

Test Automation Meetup is a free virtual online event that focuses on QA topics like software testing, test automation and quality assurance. We provide automated testing services and test automation outsourcing thus would like to find latest trends with experts. The goal is to share know how, best practises and trends from experts to community.

This event is a good way to learn new Strategies, Tools, and Trending Technology in the Software Quality Assurance and Test Automation area. Become a part of this conference and deep dive into QA topics ranging from QA in agile, DevOps, and advanced test automation techniques.

Join the free meetup and be a part of the global QA community.

Schedule

July 6 (Wednesday) from 11AM to 1PM Eastern Time (ET)

Paul Grossman

About host

10.45 am – 11.00 am (ET)

Opening by host Paul Grossman

Rafael Cintra

About speaker

11.00 am – 12.00 pm (ET)

Applying a Design Thinking Prioritization Grid approach into Quality Engineering

Understanding what is a Prioritization Grid and how it can be used

How can we leverage what is important to our customer to apply into our Prioritization Grid

How to apply a Prioritization Grid into Test Planning and Execution to be more efficient by testing what is most important and critical to our customer

Péter Földházi Jr.

About speaker

12.00 pm – 1.00 pm (ET)

Flow Model vs Page Object Pattern

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

For some, Page Object is not intuitive though

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 one of the reasons, 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