Misconception about RemoteWebDriver [Selenium] | LetCode

[@rohitsri1000]

Something new and refreshing..thanks for sharing this unique information.No one is sharing this kind off stuff.thanks for sharing.

[@letcode]

Thanks a lot

[@brajeshkokkonda]

Perfect and straight to the point 👍👌

[@letcode]

Thanks 👍

[@kunal-ashar]

Nicely described and taught. looking forward to more such videos.

[@letcode]

Thank you 😊, please share the video with your colleagues.

[@sssaamm29988]

Well, this is something new to me. Will try with remote webdriver going forward.

[@kiranmayispecial]

Hi, Thanks for sharing. I was also thinking the same that why can't we use remote web driver and you have cleared all my doubts.

[@letcode]

Happy coding 🤗

[@Amudha_Sampath]

Excellent explanation, thank you!

[@letcode]

Welcome 🤗

[@rockmusicvideoreviewer896]

I had a hard time understanding because of your accent but still gave u a like.

[@letcode]

Hey thanks mate, I'm trying to improve my accent.

[@Alright4now]

Great job sir🙌

[@letcode]

Thank you 😊

[@peterkim9696]

Still don't know what difference between remotedriver and webdriver can you explain

[@tulasiramsunkara]

@Koushik: If we can use RemoteWebDriver which infact has lot of methods like getScreeshotAs, JavaScriptExecutor, I am really suprised why entire world is using WebDriver instead of RemoteWebDriver.., Any thoughts?

[@letcode]

Basically interface acts as an contract, so that in future if any browser is introduced, still we can rely on WebDriver the interface.

[@akshaygoyal1]

@@letcode could you please elaborate more

[@letcode]

@@akshaygoyal1 interface is rul set, so if any browser comes, assume brave browser. We can use the WebDriver functions like get, findelement all those. So everyone is using WebDriver which is correct. But in selenium remot web driver is the super class and all the WebDriver implementation are there, so even if new browser comes, actual implementation will be there in RWD.

[@madhurivandanapu2764]

can we do cross browser testing with remote web driver? The reason we give WebDriver driver = new ChromeDriver() is because later on we should be able to change to different driver and run cross browser testing without modifying the code, please clarify

[@letcode]

Yes we can do. I have shown the demo as well to run in parallel with chrome and Firefox.

[@chandanguptaSDET]

Nice one Kaushik!! Just one suggestion , your can and can't sound similar. I was little confused, I heard can instead of can't :-)

[@letcode]

Thanks for the feedback, l will definitely work on it and improve. Cheers 😌

[@gaddipatiprabhakar2889]

Thank You for your video, Good One.

[@letcode]

Welcome, glad you like it 😊

[@raja310]

so we can do cross browser testing only with help of testNG.

[@letcode]

Yes ofcourse

[@Biplab1991]

You are telling classes are faster. So we can use remoteWebdriver class for faster execution but we are using webdriver which is an interface. Then why are we using webdriver, you only told classes are faster so we can use remotewebdriver which is a class..

[@letcode]

I always use RemoteWebDriver, people are not ready to accept it. Because of constructor in RemoteWebDriver I believe.

[@Biplab1991]

@@letcode if constructor is there then what is the problem??? Because in webdriver there is no constructor as it is an interface

[@letcode]

In construction it's asking for url and capabilities. I think that's y everyone is confused about it. I have described that in this video.