Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. It only takes a minute to sign up.
Sign up to join this community
I have 2 different ways of working with the driver in the page object model:
Creating the driver in all the pages and passing it from one class to another. You have an example here.
Extending the classes to a Base class where the driver is created. You have an example here
Can you tell me the pro/cons between this two options?
I would personally suggest you while working with POM first design your TestBaseSetup class. In this initialize your drivers and the same driver you can use it in your page object class by passing 'constructor' of the base class to your all object classes.
This will create Page Object classes. For each page, we will create a separate class with a constructor. We identify the locators and keep all together on just below the class. This will help us to reuse the locators for multiple methods and the main important is, we can easily find the locator and change if required.
We need to identify and a list of all the possible functionalities on this page and we should write methods in such a way they are re-used. When ever there is a method to click on a button or link, we should return driver object of that page.
For more details how to design POM, you can check here.
I like using a base class because it means there's less code duplication. Whenever I think of something that I have to repeat each time for a class, it's a good time to look and see if there's a better way to refactor that duplication and save yourself some work. Adding a base class is one way to do this.
Also, your links aren't working for me.
