Selenium/Explanation/Stack

This page explains stack from Selenium/Node.js/Simple page. This tutorial will assume that you are running tests from your machine, targeting beta cluster. Code from this page is available at repository. For more examples see Selenium/Node.js.

Examples will:


 * open browser
 * go to main page
 * check that  link is present
 * close browser

WebdriverIO
Reasons for selecting WebdriverIO:


 * sane and understandable API,
 * centralized and complete documentation,
 * built-in page object support,
 * configuration management,
 * good support.

Stack
For more information about the stack see Selenium/Stack.

Advantages

 * Minimal stack.

Disadvantages

 * No assertions.
 * No testing framework (setup, teardown, reporting...).
 * No page object pattern.

Output
Start Chromedriver in one terminal tab or window and run the tests in another one.

Everything is fine.

There is a problem.

Advantages

 * Testing framework (setup, teardown, reporting...).

Disadvantages

 * No assertions.
 * No page object pattern.

Output
Start Chromedriver in one terminal tab or window and run the tests in another one.

Everything is fine.

There is a problem.

Advantages

 * Testing framework (setup, teardown, reporting...).
 * Assertions.

Disadvantages

 * No page object pattern.

Output
Start Chromedriver in one terminal tab or window and run the tests in another one.

Everything is fine.

There is a problem.

Advantages

 * Testing framework (setup, teardown, reporting...).
 * Assertions.
 * Page object pattern.

Disadvantages

 * Several new tools to learn.

Output
Start Chromedriver in one terminal tab or window and run the tests in another one.

Everything is fine.

There is a problem.