QUnit vs WebdriverIO

In cases where you want (I know your test cases must be atomic) where you really really want your test cases to run in a specific order, maybe if the current one rely on those of previous case, you can use Qunit by setting QUnit.config.reorder = false and your test cases will run in the order you've provided.

All frontend developers already know the ease that jQuery framework has brought to their lives, in handling DOM events and accessing elements. Since Qunit was built as a part of jquery (is even used by jQuery itself for unit testing) hence it makes testing of DOM elements a lot easier.

Seriously! All you have to do is include the Qunit library from the CDN, then create your Testcases js file, and RUN IT! . Your outputs would be displayed in a pretty little format in your browser.

WebdriverIO lets you use your favorite testing framework (Jasmine, Mocha, Cucumber) and assertion library (Chai for Mocha). Other projects implement their own testing and assertion APIs, for example Nightwatch, Intern.

It should be mentioned though that v4.2.16 has an incompatibility with at least tap v7.1.2: stdout/stderr written during a run gets lost.

Chimp.js, is an emerging web application test framework that implements easy sync tests using WebdriverIO, CucumberJS and Chai. Features include:

• synchronous style
• built-in "widget framework" (an implementation of the PageObject pattern)
• automatically downloads dependencies (ChromeDriver, PhantomJS etc.)
• works with SauceLabs and BrowserStack (CrossBrowserTesting TBD)
• automatically takes screenshots on failures
• works on Windows in addition to Linux and OS X
• automatically produces boilerplate code for step definitions, which you can copy, paste and edit
• file watcher reuses the browser sessions and can run only the tests you tag, to maximize development speed

So you don't need to worry about promises

Run wdio config and WebdriverIO will generate a config file for testing locally vs. in the cloud, specifying the test framework (Jasmine, Cucumber, Mocha), where to find tests and store screenshots etc.

WebdriverIO has a plugin called WebdriverCSS that allows you to do cross visual platfrom/browser tests with an integration to Applitools.

WebdriverIO is accessible via gulp and grunt and even has a Sublime Text plugin for autocompletion.

selenium-webdriverjs:

driver.get('http://www.google.com');
driver.findElement(webdriver.By.id('q')).sendKeys('webdriver');
driver.findElement(webdriver.By.id('btnG')).click();

WD.js:

browser
  .get("http://www.google.com")
  .elementById('q')
  .sendKeys('webdriver')
  .elementById('btnG')
  .click()

WebdriverIO:

client
    .url('http://google.com')
    .setValue('#q','webdriver')
    .click('#btnG')

If you develop web applications with Meteor.js, you might want to use the xlovio:webdriver wrapper, because it's the Selenium binding behind the preferred testing framework (Chimp) promoted by the Velocity (Meteor's official testing framework) team for using BDD via Cucumber.

Service is provided by WebdriverIO which over comes the con of starting selenium server independently.
Reference: http://webdriver.io/guide/services/selenium-standalone.html