This repository contains a collection of sample webdriverIO (Selenium - Node.js/JavaScript) projects and libraries that demonstrate how to use the tool and develop automation script using the Cucumber (v 3.0.0) BDD framework. It support ES5 to ES8 (via babel-register) and uses Grunt to manage tasks, provides utilities to read data from MS-Excel, executes SQL statements to any database for end to end testing. It generate Spec, JUNIT, Allure, JSON reporters as well.
This project is tested on Node v6.10.0 to v8.9.0. While earlier versions of node may be compatible, they have not been tested or verified.
JDK 1.8: Install JDK 1.8+ and make sure class path is set properly. JAVA is require to start Selenium Server nothing else.
Node.JS: Install from the site - https://nodejs.org/en/ take the LTS version based on your Operating system. Please make sure you install NodeJS globally. If you have nvm installed globally, then run nvm install to get the latest version of node specified in the.nvmrc file here. If you don't use nvm, be sure that you are using a compatible version. Further details on nvm can be found on the official github page. MAC OSX users are best suited to install nvm with homebrew brew install nvm.
Once installation is done - open terminal (MAC OSX) or command prompt (for windows OS) and type below command to verify NodeJS has been installed properly.
node --version
npm --version
Above command should print out the version that you have installed.
Now navigate to the framework's package.json folder and run npm install to grab all dependencies.
To take full advantage of the command line and use grunt tasks you will need to make sure that you have added node_modules/.bin to your $PATH. Otherwise you will need to install the following globally:
npm install -g grunt-cli
To run your test You must have selenium / Appium server up and running to execute any WebdriverIO tests, or it will fail fast with an error. There are two ways you can run selenium.
Once all the node dependency modules are installed (through npm install) then for development, you can run npm run selenium-postinstall followed by npm run selenium-start if you wish to start it manually else you can use services: ['selenium-standalone'], in .conf.js to start it automatically which has been added as part of this project. That's all there is to it.!. Please note that this step is only one time activity at the initial framework set up. Alternatively you can also use below options to start the selenium server.
- Install Selenium (selenium-standalone) through NPM (this is the recommended way to install) as you can use it as a services in your framework without worrying to start the selenium server manually. Please note that you follow this below step if
selenium-standalonepackage in not been installed through package manager. If you are behind a specific proxy, then in that case you need to set environment variables:
-
On OSX:
- NODE_TLS_REJECT_UNAUTHORIZED=0
-
On Windows:
- setx NODE_TLS_REJECT_UNAUTHORIZED 0
sudo npm install selenium-standalone@latest -g
sudo selenium-standalone install
selenium-standalone start
OR
- Download the latest selenium standalone server version: and then for example $ java -jar selenium-server-standalone-3.4.0.jar. This option is require if you have not done the step No-1. Else ignore it. this is the other way of doing.
Note: While installing through sudo command - you need to provide System admin password. On windows don't use sudo
To execute the entire test suite in local development, you can use any one of the options mentioned below
Option 1: npm run test
Option 2: grunt webdriver:test. This executes all features in the [./test/features/*.feature] directory with a Spec reporter by default and references the suite.yourSpecific.conf.js file. Refer to the ./test/config of cucumber-bdd
To execute tests on mobile device use : npm run test-mobile
Note: Before running mobile tests, perform the requisite Appium setup. For hassle free Appium setup on OSX refer appium-setup-made-easy-OSX OR refer Appium Docs
WebdriverIO uses configuration files to setup and execute tests in specific ways. The configuration is fully customizable, and different functions can be invoked before, during and after each test or test suite. Config files can be found in the /test/config/ directory and all end with *.conf.js. These can be called via the the cli
WebdriverIO uses several different types of test reporters to communicate pass/failure.
To use the dot reporter just add 'dot' to the reporters array in the config file. The dot reporter prints for each test spec a dot. If colors are enabled on your machine you will see three different colors for dots. Yellow dots mean that at least one browser has executed that spec. A green dot means all browser passed that spec and a red to means that at least one browser failed that spec. All config files have this turned on by default.
Test reporter, that prints detailed results to console.
The Allure Reporter creates Allure test reports which is an HTML generated website with all necessary information to debug your test results and take a look on error screenshots. Add allure to the reporters array in config file and define the output directory of the allure reports.
To generate and view an allure report locally, run npm run allure-report. A typical Allure report will look like this
Allure has several other reporting tools optimized for the CI server of your choice. You can view the documentation here.
The JUnit reporter helps you to create xml reports for your CI server. Add it to the reports array in the config file and define the directory where the xml files should get stored. webdriverIO will create an xml file for each instance under test and the filename will contain the browser and OS.
To generate and view an allure report locally, run npm run junit-report.
The JSON reporter is especially versatile. Since it produces a literal in a key : value pair, help to read, translate execution results to any custom reporter / it can be used to transport reporter events to another process and format them there, or to store the execution results back to any standard RDBMS or to NoSQL like mongodb with very minimal effort.
You can write test by using Cucumber BDD framework. You can choose javascript based design pattern or ES6 based. This project is ES6 friendly (via babel-register)
Refer complete WebdriverIO API methods to write your automation tests.
Tests are written in the Cucumber framework using the Gherkin Syntax. More about Gherkin & Cucumber can be found at https://cucumber.io/docs/reference
Tests are place in *.feature files in the /test/features/ directory. A typical test will look similar to this:
Feature: Performing a Yahoo Search
As a user on the Yahoo search page
I want to search for Selenium-Webdriver
Because I want to learn more about it
Background:
Given I am on the search page
Scenario: Performing a search operation
When I enter "Selenium Webdriver" into the search box
And I click the search button
Then I should see a list of search results
Scenario Outline: Performing a search operation with passing test data as data table
When I enter <searchItem> into the search box
And I click the search button
Then I should see a list of search results
Examples:
|searchItem|
|"Selenium Webdriver"|
Within your web app's UI there are areas that your tests interact with. A Page Object simply models these as objects within the test code. This reduces the amount of duplicated code and means that if the UI changes, the fix need only be applied in one place. In other wards one of the challenges of writing test automation is keeping your [selectors] (classes, id's, or xpath' etc.) up to date with the latest version of your code. The next challenge is to keep the code you write nice and DRY (Don't Repeat Yourself). The page object pattern helps us accomplish this in one solution. Instead of including our selectors in our step definitions(in cucumber) or in Spec file (in Jasmine or Mocha), we instead place them in a <pagename>.js file where we can manage all these selectors and methods together. Your test file should only call the test methods.
You can also place reusable functions or logic inside of these pages and call them from your step files. The page object serves as a layer of abstraction between tests and code. When A test fails, it fails on a individual step. That step may call a selector that is no longer valid, but that selector may be used by many other steps. By having a single source of truth of what the selector is supposed to be, fixing one selector on the page object could repair a number of failing tests that were affected by the same selector.
An object called Page will be created with the prototype model or by ES6 class pattern. This ensures that every instance of a page object is exported as a stateless construct. Any any changes to that state are handled in the browser, rather than on the server.
It is preferable to separate page objects into individual files that end with .page.js. These will require the basic page.js prototype construct / abstract class and create new objects for each individual page. For more information on the implementation, refer to the /test/pageobjects directory.
It defines one or more selectors/tags to uniquely identify the object at runtime. You can query any element with more than one selector at a time. The benefit of using multiSelector() method is, during run time, if one selector is failed, still you can identify that element with another alternative selector on and on... which makes your test script robust.
*method : multiSelector(selectorList)
- @param {selectorList} - an arraylist which contains different alternative selector
- for example - ["[href='/guide.html1']", "//*[@id='userid']", "[@class='myclassname']"];
import utl from '/utilities/common-utilities';
browser.element(utl.multiSelector(['//*[@id="userid"]', '//*[@name="userAlias"]', "[ng-model='$ctrl.signInData[field.name]']"]));
// or inside your page class you can use like ...
//get usernameInput() { return browser.element(utl.multiSelector(['//*[@id="userid"]', '//*[@name="userAlias"]', "[ng-model='$ctrl.signInData[field.name]']"])); }
A relational database is, simply, a database that stores related information across multiple tables and allows you to query information in more than one table at the same time. Your application under test displays data from these database. So when you are actually performing automation testing it is very likely that you need to verify the data between actual (which you got it from browser) Vs expected (which you will get it from the database by executing SQL statements on database). This can be done by below statements in your code.
//example of connection to Oracle DataBase
var db = require('node-any-jdbc');
cogfig = {
libpath: './config/drivers/oracle/ojdbc7.jar',
drivername: 'oracle.jdbc.driver.OracleDriver',
url: 'jdbc:oracle:thin:QA/password123@//abc-test.corp.int:1527/stage1',
// uri: 'jdbc:oracle:thin://abc-test.corp.int:1527/stage1',
// user: 'QA',
// password: 'password123',
};
//example of sample select query to fetch the result set
var sql = 'SELECT * FROM emp_info where emp_id = "1001"';
db.execute(cogfig, sql, function(results){
//console.log(results);
//then do what ever validation you want to do with results
});
For trouble shooting and more information, please visit node-any-jdbc module which can be found here
Note: node-any-jdbc is NOT packaged under this project. If you need, you can install it as a separate npm module npm install node-any-jdbc --save and start using it right away.
You can also find sample examples under /util-examples/database-example.js
Refer to the common Javascript functions that provides clean, performant methods for manipulating objects, collections, MS-Excel utilities, DataBase utilities etc. Few sample code can be found in /util-examples/
Use Underscore.js already bundled inside the framework which provides over 100 functions that support both your favorite workaday functional helpers: map, filter, invoke — as well as more specialized goodies: function binding, javascript templating, creating quick indexes, deep equality testing, and so on.
Create a fork of the project into your own repository. Make all your necessary changes and create a pull request with a description on what was added or removed and details explaining the changes in lines of code. If approved, project owners will merge it.
Industry is moving towards Node.js / JavaScript, Angularjs, Full-Stack world. WebdriverIO, a JavaScript binding wrapper for Selenium Webdriver, was originated by Camilo Tapia's initial Selenium project called WebdriverJS, which was the first Webdriver project on NPM. In 2014, the project was renamed WebdriverIO later on. This repository is a pre-configured version of webdriverIO meant to jump-start the process of writing new test automation or adding test automation to existing node.js applications.
MIT