Creating a test case by adding keywords and ways of mapping test step

Keywords in a test case represent actions for a specific step. Each testing action, like opening or closing a browser, mouse clicks, keystrokes, etc., is denoted by specific keywords such as "open browser," "click," "Typtext," etc

Types of Opkey Keywords in Opkey

Generic Keywords:

Opkey's generic keywords seamlessly integrate with commercial tools, allowing you to create and execute test scripts effortlessly by selecting the appropriate plugin during runtime. Examples include SyncBrowser, SelectCheckBox, and GetTableRowCount.

System Keywords:

Opkey's System Keywords are predefined generic functions that work independently of the plugin used. Examples include GetTimeAtTimeZone and StringContains.

Control Flow Construct:

Control flow construct keywords govern the execution of specific sets of steps based on certain conditions, influencing the flow of the test case. They include categories like Comment, Condition, Iteration, and Obstruction. Examples include PauseExecution and StopExecution.

Selenium Webdriver Keywords:

Selenium Webdriver keywords directly interact with web browsers without running scripts within them. They function exclusively with the Selenium web driver plugin and include examples like GetSingleRowText and GetObjectProperty.

Visual Keywords:

Visual plugin-specific keywords are used for GUI testing using referenced images. They require the Visual plugin and include examples like CompareImageObjects and Paste.

Appium Keywords:

Appium plugin-specific keywords are used for mobile device testing. They require the Appium plugin and include examples like CloseApplication and DoubleTouch.

Robotium Keywords:

Opkey Mobility keywords are specifically designed for testing Android applications. They require the Mobility plugin and include examples like ClickOnText and IsEditTextEmpty.

Let’s see how a test case is created by adding keywords to Test Steps.

In this method, you can use Opkey's 700+ built-in keywords to create test cases without scripting or coding.

In the chosen test case, click on the ‘+’ button to add the required keywords.

Search the desired keyword in the search box, select it, and click "Add Keyword" to incorporate it into your test case step.

The added keyword can be seen in the image below.

Additionally, Function Library files and Service Repository methods can be incorporated into test cases by selecting them from the "Add Keyword" tab.

Different ways of mapping the Test Step

Mapping the Test step with the object by using the Object Input Argument

The object mapping feature facilitates the effortless linking of objects from the object repository file with test case steps. By selecting a test case step, the corresponding object input arguments that can be mapped to it are revealed in the right pane under the Object Repository.

The Global Variable tab displays all global variables added via the Tools menu bar. Select the desired global variable to add as a data input argument.

During execution, the values will be picked as mapped using Global Variable.

Data driving the Test Case by using Data Input Arguments -

The data driving feature facilitates the import of data from either the Global data repository, Global Variable, Auto Data Generation, or Token Manager. Map the desired data source with the test case step based on your test scenario requirements.

The dynamic data input feature allows you to add dynamic data generated in a test step, as input data in the next step.

For Example: Assign the data generated in the step to an output variable. We will map this data to the input data of the next step. This allows the output of one test step to serve as input to the next.

Select the Test Step in which you want to enter the output data. Navigate to the Step Output tab and provide the value.

To use the output of one test step as input to another, select the subsequent test step, navigate to the Data Input Argument tab, and select Data Output. Then, choose the desired step output value to be added as an input of that particular step.

This will add the output data of one step to the input of the next step.

This covers the various ways in which mapping can be done in test cases and its creation through keywords.

Creating a test case by adding keywords and ways of mapping test step

Keywords in a test case represent actions for a specific step. Each testing action, like opening or closing a browser, mouse clicks, keystrokes, etc., is denoted by specific keywords such as "open browser," "click," "Typtext," etc

Types of Opkey Keywords in Opkey

Generic Keywords:

Opkey's generic keywords seamlessly integrate with commercial tools, allowing you to create and execute test scripts effortlessly by selecting the appropriate plugin during runtime. Examples include SyncBrowser, SelectCheckBox, and GetTableRowCount.

System Keywords:

Opkey's System Keywords are predefined generic functions that work independently of the plugin used. Examples include GetTimeAtTimeZone and StringContains.

Control Flow Construct:

Control flow construct keywords govern the execution of specific sets of steps based on certain conditions, influencing the flow of the test case. They include categories like Comment, Condition, Iteration, and Obstruction. Examples include PauseExecution and StopExecution.

Selenium Webdriver Keywords:

Selenium Webdriver keywords directly interact with web browsers without running scripts within them. They function exclusively with the Selenium web driver plugin and include examples like GetSingleRowText and GetObjectProperty.

Visual Keywords:

Visual plugin-specific keywords are used for GUI testing using referenced images. They require the Visual plugin and include examples like CompareImageObjects and Paste.

Appium Keywords:

Appium plugin-specific keywords are used for mobile device testing. They require the Appium plugin and include examples like CloseApplication and DoubleTouch.

Robotium Keywords:

Opkey Mobility keywords are specifically designed for testing Android applications. They require the Mobility plugin and include examples like ClickOnText and IsEditTextEmpty.

Let’s see how a test case is created by adding keywords to Test Steps.

In this method, you can use Opkey's 700+ built-in keywords to create test cases without scripting or coding.

Search the desired keyword in the search box, select it, and click "Add Keyword" to incorporate it into your test case step.

Additionally, Function Library files and Service Repository methods can be incorporated into test cases by selecting them from the "Add Keyword" tab.

Different ways of mapping the Test Step

Mapping the Test step with the object by using the Object Input Argument

The object mapping feature facilitates the effortless linking of objects from the object repository file with test case steps. By selecting a test case step, the corresponding object input arguments that can be mapped to it are revealed in the right pane under the Object Repository.

The Global Variable tab displays all global variables added via the Tools menu bar. Select the desired global variable to add as a data input argument.

During execution, the values will be picked as mapped using Global Variable.

Data driving the Test Case by using Data Input Arguments -

The data driving feature facilitates the import of data from either the Global data repository, Global Variable, Auto Data Generation, or Token Manager. Map the desired data source with the test case step based on your test scenario requirements.

The dynamic data input feature allows you to add dynamic data generated in a test step, as input data in the next step.

For Example: Assign the data generated in the step to an output variable. We will map this data to the input data of the next step. This allows the output of one test step to serve as input to the next.

Select the Test Step in which you want to enter the output data. Navigate to the Step Output tab and provide the value.

To use the output of one test step as input to another, select the subsequent test step, navigate to the Data Input Argument tab, and select Data Output. Then, choose the desired step output value to be added as an input of that particular step.

This will add the output data of one step to the input of the next step.

This covers the various ways in which mapping can be done in test cases and its creation through keywords.

Read more articles on test cases by clicking here