WD.js vs Leadfoot -> Intern

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();
}

The documentation starts by describing what Intern is, what it's good for, who it's good for, its terminology, and continues with a tutorial.

Intern is used by big companies such as IBM, Intuit and Mozilla.

Intern (and Leadfoot) is a JS Foundation project. The JS Foundation is sponsored by IBM, Samsung, and other industry leaders.

A project that compares itself with prior art has done its homework.

Compare the Intern releases with those from Nightwatch, let alone WD.js

The built-in support for source maps allows you to easily track issues to the original source files.

Can integrate with cloud hosting services from BrowserStack, Sauce Labs and TestingBot.

Since it always uses Promise objects every time an asynchronous operation needs to occur, the test system pauses until that Promise object is resolved, or until a timeout occurs. Suite, test and reporter functions can return a Promise.