Hello Sir, your way of explaining things is too good....Thank you...But to achieve encapsulation we need getter and setter approach......Or to achieve encapsulation ,getter and setter is the only approach...?
I didnt understand where you said we hiding implementations of webelements and achieving Abstraction but you didnt make the method as abstract instead it was Inheritance, ElectronicPage extended Generics, this is confusing me
Please improve the quality of explanation. It's very lagging when you are using a sentence 2 times. This could be just 15 mins Video but dragged for 30 mins
WebDriverWait is not an interface..its a class WebDriverWait wait = new WebDriverWait (driver, 20); object is being created..how then it would be an interface??
The WebDriver interface in Selenium is implemented by various browser-specific classes such as ChromeDriver, FirefoxDriver, EdgeDriver, etc. These classes provide the concrete implementation of the methods declared in the WebDriver interface. Using the WebDriver interface allows for a consistent way of interacting with different browsers, making the code more modular and flexible.
Just a suggestion, Please don't repeat the same word again and again multiple times.. it's actually spoils the learning here .. thanks for your efforts...
Hey hi they asked me in project explain oops not in framework or selenium methods..can you tag any video which you explained for project 😅
Very well explained. OOPS concepts in selenium are now much clear.
Very Informative and easily relatable to understand the oops concepts for Selenium. Thanks for Sharing!!!
Super bro, I understood how we r using oops in automation.
Very nice explanation of OOPS concept in Selenium which I have been searching for long. Thank you so much Sir!
Great Explanation. This video is Very helpful. Thanks so much.
Thanks buddy ❤️
Wow ... I was always looking for this video 💫. Thank you!!!
Thank You so much for your love and support…👍
Very helpful video
Thank you for sharing ur knowledge.
My pleasure 😇
very very useful video
This is one of interview question in morgan stanley automation interview
Nice🎉
Very informative and helpful video. But can you please not repeat each sentence twice just for the sake of it?
Easy to explain how framework is
Simply wow
Thanks for your work! Well done!
Thanks for sharing
Thank you so much 😊
Subscribed and Liked. Very nice video and you made me understand easy even we know the basics of the concept.
Hello Sir, your way of explaining things is too good....Thank you...But to achieve encapsulation we need getter and setter approach......Or to achieve encapsulation ,getter and setter is the only approach...?
It really helps a lot .thanks
Thanks for your support 🙂
Smoothly explained, helped a lot.
Thanks Bro
@4:59 , WebdriverWait is not an Interface
Can you please share the git repo for this project that would be really helpful
Thank you
Can you please share the git url of this project
Thanks🙏
nice
Thank you please support our channel. 👍😊
I didnt understand where you said we hiding implementations of webelements and achieving Abstraction but you didnt make the method as abstract instead it was Inheritance, ElectronicPage extended Generics, this is confusing me
WebDriverwait is a class
Please improve the quality of explanation. It's very lagging when you are using a sentence 2 times. This could be just 15 mins Video but dragged for 30 mins
Thanks.
WebDriverWait is class not an Interface please correct it
WebDriverWait is not an interface..its a class
WebDriverWait wait = new WebDriverWait (driver, 20);
object is being created..how then it would be an interface??
The WebDriver interface in Selenium is implemented by various browser-specific classes such as ChromeDriver, FirefoxDriver, EdgeDriver, etc. These classes provide the concrete implementation of the methods declared in the WebDriver interface. Using the WebDriver interface allows for a consistent way of interacting with different browsers, making the code more modular and flexible.
@@shubhamherwade1260 did u read the question properly ?
Please paste this framework link for reference
Webdriverwair is class not interface
Dont repeat same lines again and again. Once is enough
Just a suggestion, Please don't repeat the same word again and again multiple times.. it's actually spoils the learning here .. thanks for your efforts...
I don't think so
Yes , it is irritating to listen same thing twice eact time
Very Informative and easily relatable to understand the oops concepts for Selenium. Thanks for Sharing!!!
WebDriverWait is class not interface