One of the most discussed topics in UI Test Automation is Page Object Model. Page Object Model is a de-facto industry-standard pattern. This pattern was introduced by Martin Fowler in 2013  and is an adaptation of Facade and Adapter patterns to the UI Test Automation.
There’s no lack of Test Automation courses and mentoring programs nowdays. Yet, most of the courses I am aware of (either free or paid) start at the wrong place — they start either on UI or API level but fail to give a proper foundation a well-grounded Test Automation Engineer must have.
“If you start with framework — you do it wrong”
Let us draw a line here and now, Test Automation Engineers are not Testers — their primary objective is almost never to test. Instead, they are special kind of developers — developers specialized in Test Automation Solutions development. …
Some time ago I wrote this post describing my understanding at that time of the architecture patterns used to create Test Automation Framework and Solutions. While there’s some information I still agree with, my understanding has evolved and I want to share this evolved understanding with others.
One of the first steps (if not the first) on the path of moving to Test Automation job should be learning a programming language. Solid programming fundamentals are essential for building a successful career in Test Automation. Luckily, there’re lots of resources that can help you with that.
Probably the most popular architecture pattern used for test automation frameworks is Layered (also known as N-Tier or Tiered) architecture. This pattern is so well known that on job interviews for some companies when they ask you about Test automation framework architecture you are supposed to describe this one. …