Here’s the Deal
Slant is powered by a community that helps you make informed decisions. Tell us what you’re passionate about to get your personalized feed and help others.
When comparing WD.js vs elm-webdriver, the Slant community recommends elm-webdriver for most people. In the question“What are the best Node.JS Selenium WebDriver client libraries / bindings?” elm-webdriver is ranked 6th while WD.js is ranked 8th.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Cleaner and more concise code than WebdriverJS
There is no need to pass the 'driver' instance around, and not as many parentheses.
Using WD.js
function login(username, password) {
return this
.waitForElementByCss('.loginForm', asserters.isDisplayed, seconds(explicit_wait))
.elementById('emailAddress').sendKeys(username)
.elementById('password').sendKeys(password)
.elementById('signInButton').click()
}
Using WebDriverJS
function login(driver, username, password) {
driver.wait(until.elementIsVisible(driver.findElement({css: '.loginForm'})), seconds(explicit_wait));
driver.findElement({id: 'emailAddress'}).sendKeys(username);
driver.findElement({id: 'password'}).sendKeys(password);
driver.findElement({id: 'signInButton'}).click();
}
No pros yet!
Cons
Con Dropped by Intern
Intern v1 used WD.js, but they dropped it in favor of developing Leadfoot.
Con Less activity than WebdriverIO
WebdriverIO issues: 34 open, 507 closed. First release May 2012 at v0.6
WD.js issues: 18 open, 216 closed. First release: April 2011
No cons yet!