Understanding Opkey keywords

 In this method of creating a test case, you can add keywords present in the Opkey library. There are 700+ inbuilt keywords present in the Opkey library which helps users to create test cases for automation without writing any scripts/coding. To add a new step within your test case, click on Add Test Step in the test case.

The keyword you want to use can be searched by typing the name of that keyword in the provided search box. All the keywords corresponding to the typed keyword are displayed in the dropdown list. 

You can select the desired keyword by clicking the keyword from the dropdown. The selected keyword will be added to your test case step. You can update/replace a selected test step keyword with the new corresponding keyword. 

You can also add Reusable Component(RC) file(s) and Service Repository method(s) as a test step in Test Case. Go to the ‘Add Keyword‘ tab and scroll down and select your RC/SR Method file and add it to your Test step.

Opkey Keywords:

1. Generic Keywords: Opkey generic keywords can be used to create a test script & execute it with a commercial tool by selecting the corresponding plug-in during run time. For Example SyncBrowser, SelectCheckBox, GetTableRowCount, etc.

2. System Keywords: The System Keywords in Opkey are the pre-defined generic functions independent of the plugin used. For Example GetTimeAtTimeZone, StringContains.

3. Control Flow Construct: Control flow construct keywords are responsible to execute certain sets of steps resulting in a choice. It contains the following categories: Comment, Condition, Iteration, and Obstruction. For Example PauseExecution, StopExecution, etc.

4. Selenium Webdriver Keywords: Selenium Webdriver keyword is used to execute suite by directly opening a web browser rather than running scripts within the browser. They work only with the Selenium webdriver as a plugin. For Example, GetSingleRowText, GetObjectProperty etc.

5. Visual Keywords: Keywords in this tab are plug-in specific and they are used to test GUI using referenced images. They work only with Visual as a plugin. For Example: CompareImageObjects, Paste etc.

6. Appium Keywords: These keywords are specifically used while using Appium as a plugin for mobile devices. For example: CloseApplication, DoubleTouch etc.

7. Robotium Keywords: Keywords in this tab are plug-in specific and applicable on Android applications. For Example: ClickOnText, IsEditTextEmpty etc.

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

This feature allows you to map objects, from an object repository file, with the test case step as per your test scenario. When you click on any test case step, the corresponding edit button for Set Data provides you with the option of editing the data of the selected step.

Further you need to select the object as required.

Add Gif

Data driving the Test Case by using Data Input Arguments –

This feature allows you to import data from the Global data repository file or from an Excel sheet (.xlsx files only). Map the Global data repository file with the test case step as per the requirement of your test scenario. 

This feature provides you flexibility to add dynamic value as data input argument to the test case step. The associated value of data input argument will replace the static value of test case step.

There are two ways of using data input arguments: Cyclic and Continuous. The cyclic radio button helps you to run test steps again and again with different input data during the execution. On the other hand, when the Continuous radio button is selected, data input argument(s) is used only once.

The output panel is used to reference keywords in a test case. The output of one test step can be associated with an input for the other test step. This panel plays an important task in referencing steps with each other.

For example: The output of a test step has been assigned as ‘Output’ which is further associated with another test step as an input. Now, the output of the test case step acts as input for the next test case step.

Select Test Step, navigate to the Step Output tab, and provide the name of the Output (Here Output).

Select further test step, navigate to the Data Input Argument tab, select Data Output, and then select desired step output value.

The global Variable tab shows the global variables added from the Tools menu bar. Choose the desired global variable to add as a data input argument.