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

‍A Test Case includes Test Steps or Function Libraries with keywords that can take inputs and produce outputs usable in subsequent steps. 

For instance, you can create a Test Case to assess the functionality and user interface of an e-commerce web application, with steps including login, product search, purchase, payment, and logout.  


How a test case is created by adding keywords to Test Steps 

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

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

Existing test step keywords can be modified or replaced using the "Update Keyword" button.

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




Types of Opkey Keywords  


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.

Different ways of mapping the Test Step 

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

The object mapping feature enables seamless association of objects from the object repository file with test case steps. Selecting a test case step reveals the corresponding object input arguments that can be mapped to it in the right pane. 



Mapping the Test step with the object with a Global Variable 

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 file or an Excel sheet (.xlsx files only). Map the desired data source with the test case step based on your test scenario requirements.

The dynamic data input feature introduces flexibility by allowing you to add dynamic values to test case steps. These dynamic values replace the static values within the test case steps.



The output panel assists in referencing keywords in a test case by linking the output of one step to the input of another. 

For Example: Assign an output to a variable named Output and reference it as an input to another test step. This allows the output of one test step to serve as input to the next. 

Select the Test Step. Navigate to the Step Output tab and provide the name of the Output. 




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.


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


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


To learn about more Opkey features, click Here.  



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article