Test Components - ChrisMell/OEL-wiki GitHub Wiki

Execution Components

In order to successfully execute tests, several classes and files must be created, properly placed, and correctly linked to each other. The following sections describe each component in the abovementioned arrangement, and how they connect with each other to facilitate a successful test execution.

Features

The feature files contain scenarios, each consisting of steps, written in Gherkin (plain English). This sequence of test steps form the automated scripts that are ran in the test environments, to gather information and produce results, regarding the system under test.

(Shown above is a feature file containing the 'folder-setup' scenario.)

Each step can be linked by Cucumber tags (given, when, then), to a step definition method, which can be found in one of the packages described in the Framework Components - Test section of this document.

The feature files can be found in the src/test/resources/features directory of the project. They are also further organized into folders by iteration.

For information on how to create a feature file, please refer to the section entitled: Create a Feature File.

Test Step Definitions

If the test step in the feature file is the chassis, the corresponding test step definition, found in a separate class, is the steering column, braking system, and internal wiring.

Whereas the test step in the feature indicates in plain English, the tasks expected to be performed, the test step definition contains the code that will perform those tasks within the environment.

(An example test step definition.)

Once the step in the feature file is syntactically matched with the Cucumber tag above the step definition's method signature, in the step definition file, the code within the step definition will execute, during runtime.

Please refer to the Create a Step Definition File section, for information on how to create such step definitions.