Types of Opkey keywords and ways of mapping in a test step

In a test case, keywords indicate specific actions for each step. These actions include tasks such as opening or closing a browser, clicking, typing text, etc. 

Types of Keywords in Opkey

Generic Keywords:  

Opkey's generic keywords seamlessly integrate with commercial tools, enabling effortless test script creation and execution by selecting the plugin at runtime. Examples: SyncBrowser, SelectCheckBox, GetTableRowCount.

System Keywords:  

Opkey's System keywords, like GetTimeAtTimeZone and StringContains, are pre-defined functions that work regardless of the plugin used.

Control Flow Construct:  

Control flow construct keywords manage step execution based on conditions, affecting test flow. Categories include Comment, Condition, Iteration, Obstruction etc. Examples: PauseExecution, StopExecution etc.

Selenium Webdriver Keywords:  

Selenium Webdriver keywords interact directly with web browsers via the Selenium web driver plugin. Examples include GetSingleRowText and GetObjectProperty.

Visual Keywords:  

Visual plugin-specific keywords facilitate GUI testing with referenced images, requiring the Visual plugin. Examples include 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. 

Login to your Opkey portal, and select the project to work on.

In the chosen test case, click 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 also 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 

Object mapping streamlines the linking of recorded web objects from the object repository to the respective test case steps. Select a test step and click on the Test Object tab. It reveals corresponding object input arguments in the right pane under the Object Repository to be linked.

Data driving the Test Case by using Data Input Arguments - 

The data driving feature imports data from various sources like the Global data repository, Global Variable, Auto Data Generation, or Token Manager. Map the desired source to the test step as per your scenario. 

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