Amuthan, your expertise in framework and Java 8 implementation has helped me improve my existing skills and project frameworks. Thank you so much, and may you be blessed abundantly.
Honestly speaking, there tons of videos on design patterns, but this one is at different level. Unique talent to put a complex concept in easiest manner. Love all your videos, keep up the good work. I liked and subscribed...thanks a lot for all your great work.
Hi Amuthan, Thank you for starting this design pattern series. It adds more values when you explain with testing based examples. Keep up the good work 💪
Watched this video twice to understand its simplicity. Thank you for including the with & and example and using the method name build. Now i can corelate how Gherkin/RestAssured might be using this keyword and / with internally. Also how the action class must be using the build method.
Thank you for sharing knowledge, this is more useful. Here I have one question, If the field is not mandatory, no need to mention that attributes in the payload. How to handle this type of scenario with pojo class and builder.
Thanks a lot for such valuable contents..Just wish to understand the concept clear, while building with parameters you cannot skip the boolean & address field, but while using the build method having return type "Employee" under employeeBuilder POJO, how it is building without these parameters without error? I am sure I am missing some key concepts, if possible please let me know. Thanks
Hi Amuthan We are working on api automation using playwright and our request payload is very big and we have many attributes in it probably 100 lines in json file We have to check with different combination of attribute Is there any design pattern u could suggest to make things easy to handle request payload for apis ? What is the best way to handle it ..i felt maintaining them in jsons will not be a good option
@@priyankav2890 Normally these test have to be written at unit level. Where you can check which attributes are mandatory. You can build a default pojo from external json file and then alter attributes based on your needs. You can leverage factory pattern to get all possible combinations of input but you have to still construct them manually.
Amuthan, the code you have used to build Builder pattern is not making the object immutable? and cannot we do the same setter methods in Employee POJO directly if we do not care about immutability of objects?
Creating two objects even after optimization would be too costly. You hardly need a single object, to solve this problem. Also why are you creating a static method and creating an instance inside it ? Doesn't make any sense
We weed immutable student object. To do that, there are multiple ways. Using an external builder class is one way. Replacing constructor with static method is a common practice for providing readability.
![[Webinar Recording] Design Patterns in Test Automation](/img/n.gif)
Amuthan, your expertise in framework and Java 8 implementation has helped me improve my existing skills and project frameworks. Thank you so much, and may you be blessed abundantly.
Happy to hear your feedback!
Honestly speaking, there tons of videos on design patterns, but this one is at different level. Unique talent to put a complex concept in easiest manner. Love all your videos, keep up the good work. I liked and subscribed...thanks a lot for all your great work.
Hi Amuthan,
Thank you for starting this design pattern series. It adds more values when you explain with testing based examples. Keep up the good work 💪
Watched this video twice to understand its simplicity.
Thank you for including the with & and example and using the method name build.
Now i can corelate how Gherkin/RestAssured might be using this keyword and / with internally.
Also how the action class must be using the build method.
Amuthan Kudos to you for always thinking out of the box 😀
Hi Amuthan, would be great if you could make a video on Screenplay pattern as well. Thanks for the great videos 🙏🙏
Thank you for sharing knowledge, this is more useful.
Here I have one question, If the field is not mandatory, no need to mention that attributes in the payload. How to handle this type of scenario with pojo class and builder.
You can use jackson annotations to cater this scenario.
Thanks a lot for such valuable contents..Just wish to understand the concept clear, while building with parameters you cannot skip the boolean & address field, but while using the build method having return type "Employee" under employeeBuilder POJO, how it is building without these parameters without error? I am sure I am missing some key concepts, if possible please let me know. Thanks
By default, false will be set for Boolean and null for Address
Thanks for the knowledge.
Amuthan, please tell me on getting the name - Builder in the getter template list?
yes if possible please make one on solid principles
you should know SOLID principles first before jumping to Design Patterns
Hi Amuthan
We are working on api automation using playwright and our request payload is very big and we have many attributes in it probably 100 lines in json file
We have to check with different combination of attribute
Is there any design pattern u could suggest to make things easy to handle request payload for apis ? What is the best way to handle it ..i felt maintaining them in jsons will not be a good option
@@priyankav2890 Normally these test have to be written at unit level. Where you can check which attributes are mandatory.
You can build a default pojo from external json file and then alter attributes based on your needs.
You can leverage factory pattern to get all possible combinations of input but you have to still construct them manually.
@@TestingMiniBytes thanks for the reply .will try what you suggested
Amuthan, the code you have used to build Builder pattern is not making the object immutable? and cannot we do the same setter methods in Employee POJO directly if we do not care about immutability of objects?
Hi Amuthan, Whats the Url /APi u r automaitng?
Thanks
www.testingminibytes.com/sponsor - you can consider this link next time. Thank you for your contribution. !
Creating two objects even after optimization would be too costly. You hardly need a single object, to solve this problem. Also why are you creating a static method and creating an instance inside it ? Doesn't make any sense
We weed immutable student object. To do that, there are multiple ways. Using an external builder class is one way. Replacing constructor with static method is a common practice for providing readability.