Selenium (POM) With Builder Pattern in Java || Practical Example

Selenium (POM) With Builder Pattern in Java || Practical Example

Schedule a meeting in case of any queries/guidance/counselling:

~~~Subscribe to this channel, and press bell icon to get some interesting videos on Selenium and Automation:

Follow me on my Facebook Page:

Let's join our Automation community for some amazing knowledge sharing and group discussion on Telegram:

Naveen AutomationLabs Paid Courses:
GIT Hub Course:

Java & Selenium:

Java & API +POSTMAN + RestAssured + HttpClient:

[Dinu-zl]

Thanks Naveen, This really helps a lot especially in e-commerce supply chain applications where lot of data entry is being done.

[rahuldubey]

I was waiting for this video. This playlist is very essential when one is planning the framework. I am trying to use Factory pattern with RestAssured. I am also using cucumber. Is it a good choice?

[omkarkulkarni]

Hi Naveen,
this is a very nice explanation, can you also give more optimised code using the Lombook where we can reduce the getters and setter this will be of great help

[ankur_sharma]

Thanks Naveen for this, really great explanation with live example.
I have a question, if a page has large number of locators (assuming they are distinct) including input fields, button, anchors, images etc. Would you create class variable for every locator? What approach would you take to handle class variables? Breaking down a page class to feature level could help but is it a good approach? I know common or similar elements can be handled by HashMaps or having generic xpath to get list of web elements. Looking out for better approach. Thank you in advance.

[parthis]

Suggest to use Lombok builder annotation

[joyvenke]

Hi Naveen thanks for share getter and setter method but I have some case is this possible to pass different xpath’s or elements in one method!? To reuse same method but different different step definition classes! Sorry to ask

[creepy]

This is a whole lot of extra code when you could just add set* methods in the page object. I would only use the builder pattern if the object I'm trying to build is complex and I really need the final object. In the example shown, you don't show a good reason WHY the final object is needed so I would avoid the extra complexity of the builder pattern.