node.js - Understanding the Web Driver API -
node.js - Understanding the Web Driver API -
if understand w3c's info on webdriver api right, browsers implement api can automated using restful api. is, can open http connection browser , send commands using rest.
i found this gist confirms me guess right: node.js script straight connects phantomjs has been started webdriver server.
so far, good.
what don't why apparently other browser still need selenium server. projects such webdriverjs require me run selenium server.
my question just: why?
shouldn't possible automate browser without selenium server? should browsers not able provide api straight (as phantomjs does)?
can shed lite please?
you misunderstand w3c spec. though section 2.6 of specification declares implementers must provide json-over-http-accessible "remote end" of protocol, declares implementation:
may take form of standalone executable translates json on http protocol encoding , transport mechanism used remote end.
so, put, no, may not case may fire browser instance , expect connect via http. while phantomjs include webdriver implementation part of browser executable, may require separate executable functionality. example, automating chrome requires instance of separate chromedriver executable, implements http server portion of protocol.
furthermore, of import note specification @ working draft
stage, , has not yet reached last call
or candidate recommendation
status. means browser vendors may not yet have published implementation of specification. while there in-progress implementations beingness done mozilla firefox, , published 1 internet explorer microsoft, neither of these implementations finish yet, , both of implementations in particular require external executables access via http, chrome does.
thus, moment, using selenium server alternative browsers not supply http implementation. list major desktop browser vendors @ moment includes firefox, net explorer, , safari.
node.js selenium webdriver
Comments
Post a Comment