Automation Testing


Selenium is used for automating Web Applications. In this course you will experience to work with Data Driven Framework and Keyword Driven Framework and perform Cross browser testing. Selenium IDE, Selenium RC, Selenium WebDriver and Selenium-Grid are covered during the course. You will learn to perform tests on multiple machines simultaneously running on different Operating Systems, integrate other frameworks like JUnit and TestNG with Selenium.


SpecFlow helps domain experts and developers to communicate easily by binding business readable behavior specifications and examples to the underlying implementation. Acceptance Test Driven Development (ATDD) and Behavior Driven Development (BDD) are supported by SpecFlow, which are often used synonymously with Specification-By-Example.


BEHAT training course helps developers to get started with the process of behaviour driven development (BDD) in PHP using the BEHAT toolkit in order to align technical testing with business expectations. Technical project managers and QA testers will also find this course helpful by introducing them to the concepts and importance of User Acceptance testing in client site development.


Cucumber is a framework for writing and executing high level descriptions of your software’s functionality. One of Cucumber’s most compelling features is that it provides the ability to write these descriptions using plain text in your native language. Cucumber’s language, Gherkin, is usable in a growing variety of human languages.


The course on Java BDD with JBehave from Wenso teaches students how to do Behavior-Driven Development (BDD) with JBehave in a Java software development environment. In BDD, team focuses on the problem field and creates a familiar language for communicating a product’s preferred behavior as stories and acceptance test criteria. Software developers can then map the criteria and stories on their test code to confirm application behavior. It moves the vocabulary from being test-based to behaviour-based, and poses itself as a design philosophy..

Manual Testing

Black box testing

Internal system design is not considered in this type of testing. Tests are based on requirements and functionality.

White box testing

This testing is based on knowledge of the internal logic of an application’s code. Also known as Glass box Testing. Internal software and code working should be known for this type of testing. Tests are based on coverage of code statements, branches, paths, conditions.

Unit testing

Testing of individual software components or modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. may require developing test driver modules or test harnesses.

Incremental integration testing

Bottom up approach for testing i.e continuous testing of an application as new functionality is added; Application functionality and modules should be independent enough to test separately. done by programmers or by testers.

Integration testing

Testing of integrated modules to verify combined functionality after integration. Modules are typically code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.

Functional testing

This type of testing ignores the internal parts and focus on the output is as per requirement or not. Black-box type testing geared to functional requirements of an application.