Selenium RC
|
Selenium WebDriver
|
You first need to launch a separate application called Selenium Remote
Control (RC) Server before you can start testing
|
Web Driver’s architecture is simpler than Selenium RC’s.
|
Selenium RC is slower since it uses a JavaScript program called
Selenium Core. This Selenium Core is the one that directly controls the
browser, not you.
|
Web Driver is faster than Selenium RC since it speaks directly to
the browser uses the browser’s own engine to control it.
|
Selenium Core, just like other JavaScript codes, can access
disabled elements.
|
Web Driver interacts with page elements in a more realistic way.
|
Selenium RC’s API is more matured but contains redundancies and often
confusing commands.
|
Web Driver’s API is simpler than Selenium RC’s. It does not contain
redundant and confusing commands.
|
Selenium RC cannot support the headless HtmlUnit browser. It
needs a real, visible browser to operate on.
|
Web Driver can support the headless HtmlUnit browser.
|
Selenium RC Has Built-In Test Result Generator. Selenium RC
automatically generates an HTML file of test results.
|
Web Driver has no built-in command that automatically generates a Test
Results File.
|
Selenium RC needs the help of the RC Server in order to do so.
|
web Driver directly talks to the browser
|
Selenium RC can support new browsers
|
It cannot readily support new browsers
|
Automation Testing Tutorial includes Selenium, Framework Development, Advanced Appium Concepts, Java, Manual Testing, Agile & Mobile App Testing
Wednesday, August 14, 2019
Difference Between Selenium RC & Selenium WebDriver
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment
If any suggestions or issue, please provide