Overview

In OpKey, a Test Case is a collection of test steps and a test step contains either a Keyword, a Control Flow Construct, Function Library file or Service Repository file. A Keyword can take either no input or can take object, data, or both as inputs. Each test step also returns an output which can be used as input for the other step. Follow any one of the following steps to create a new Test Case file.

Working with Test Case

  • After successfully login into OpKey Web, select the appropriate Project in which you want to create a Test Case File.
  • You will be navigated to the screen having as shown.

  • You can mark the “Don’t show me again” checkbox as checked if you do not wish to view this notification again.
  • Click “End Tour” to proceed with the process of creating a Test Case file.

How to create a Test Case File?

Method 1

  • After clicking on “End Tour” , you may "Click to Create New Artifact".Select Test Case.
  • The Test Case”  text will appear highlighted.

  • Click on the highlighted icon to create a New Test Case file. A Create Test Case window will get open as shown.

  • The fields marked with * are mandatory. Enter the Name of the Test Case. You can also enter the Description. Click OK.

Method 2

  • Go to Project Workspace > Select the root Folder > Click Create New file icon  > Select Test Case'

  • A Test Case file will be created in the root Folder of the project Workspace.

Method 3

  • Right click on root folder > select Create New > select ‘Test Case.

  • Test Case file will be created in the root Folder of the project Workspace.

The Test Case window will open up as shown:

Open your Test Case file and click on Add Test Step button to add steps.

noteThere are three ways of creating a Test Case: By adding Test Steps, by Recording & by Adding Flowchart. These ways are described in next articles.

 

Getting Familiar with Test Case buttons: 

The Dockable panels of the Test Case Window:

The Test Case window contains four Dockable panels namely Details,Used ByAudit Trails and Tags. The details of these Dockable panels is mentioned below:

Details

This Dockable panel gives you the details about the Test Case such as the name of the OpKey user who has created it, the date on which the Test Case was created, the name of the user who has last modified the Test Case and the date on which it was last modified.

You can add comments/description about the Test Case in the right-hand side of the Details window.

Used By

The Used By Dockable panel provides details about the artifacts/component files that are using this particular Test Case.The information include Name, Full Path, Description, and Component Type of the artifact.

Audit Trails

This Dockable panel reflects the details about all the changes done by user irrespective of the Test Case which includes Task, Field, Old Value, New Value, Time Stamp, and ByUser.

The 'Task' detail specify what activity has been performed by the user.'Field' provides the name of the Data field being modified. As the name Suggest 'Old Value' and 'New Value' describes the previousand currentvalue of the Field being modified.

'Time Stamp' denotes the Dateand Timeon which the field was modified. The Detail 'By User' indicates the name of the user who has performed the task.

Export Audit Trails:

Once you click on the Export Audit Trails icon, a pop up window will open up as follows:

Tags

Tags are key-value combination added in the tags panel that allows the user to provide any important detail/information related to the Test Case. For example, the browser or environment on which the artifact has been created. A user can add as many number of tags as possible in a particular component file.

Getting Familiar with the icons of Tags:

Execution Status

Execution Status tab in the dockable panel provides you the information about the test execution of the artifact. The information displayed in a tabular form with Session Name, Executed From, Executed By, Execution Time, Executed On & Status as column names.

Older Versions

  • Older Versions tab in the dockable panel provides you the information about the existing older version of the file. If you have not created any file version then no file is displayed here in Older Version tab.

  • You can view version details by clicking on Version Details button.

  • You can preview and make replica of the older version file by clicking on Preview button.
  • Here, you can view that the replica is being created.

  • Here, replica has been created successfully. Once the replica has been created successfully, the saved older version file gets deleted automatically.
  • Click on Finish.

  • You can restore the saved version by clicking on the Restore Version button.
  • Select folder in which you want to restore the older version file and then click on Next.

  • From here, you can add tags.

  • The desired older version file has been restored successfully. You can download logs by clicking on Download Logs button.
  • Click on Finish.

Function Library Viewer:

Now, you can view Function Library added to the Test case. For this you can use any of the given options (Expand FL, Show FL Information, Open in New Tab). Expand FL opens the Function Library file in expanded view showing all added Test Steps. Show FL Information opens Function Library file in a popup window and shows detailed information about the Function Library file. Open in New Tab option can be used to open the Function Library file in a new tab.

  • Expand FL opens selected Function Library File with all added steps in a new popup window as shown below:

  • Show FL Information opens selected Function Library information in a new popup window as shown below:

  • Open in New Tab opens selected Function Library with all added steps in a new tab as shown below:

Open in New Tab in Test Case:

Open in New Tab feature enables you to view added artifacts (FL, SR method, Mapped Objects, & Mapped DR) in a Test Case.

  • You can click on the Open in New Tab option of the added Function Library to open it into a new tab.

  • You can right click on added Service Repository Method and select Open in New Tab option.

  • You can view mapped object with a Test Case step in detail. Right click on mapped object and then click Open in New Tab.

  • You can view the Object in the Object Repository in a new tab.


Creating test case by adding test steps


https://youtu.be/nFlHCSjWCwA

noteTest step contains either a Keyword, a Control Flow Construct, Function Library file or Service Repository file. The added test step can be mapped further with object input argument, data input argument or step output as per requirement of your test scenario.

 

Work Flow explaining the Process of Manually Creating a Test Case

4.1.1 Adding Keywords to Test Steps

 

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 user to create test case for automation without writing any scripts/coding. To add new step within your test case, click on Add Test Step.

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 on 'Add Keyword' button. The selected keyword will be added to your test case step. You can update/replace a selected test step keyword by using 'Update Keyword' button of the new corresponding keyword. You can also add FL file(s) and SR method(s) as a test step in Test Case. Go to the 'Add Keyword' tab and scroll down and select your FL/SR Method file and add it to your Test step.

noteYou can also add FL file(s) and SR method(s) as a test step in Test Case. Go to the 'Add Keyword' tab, scroll down & select your FL/SR Method file then add it as your Test step.

OpKey Keywords:

  1. Generic Keywords: OpKey generic keywords can be used to create test script & execute it with 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 set of steps resulting in a choice. It contains 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 Selenium webdriver as plugin. For Example, GetSingleRowText, GetObjectProperty etc.
  5. Sikuli Keywords: Keywords in this tab are plug-in specific and they are used to test GUI using referenced images. They work only with Sikuli as 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 object, from object repository file, with the test case step as per your test scenario. When you click on any test case step, the corresponding object input arguments that can be associated/mapped with that test case step, are shown in the right pane.

Data driving the Test Case by using Data Input Arguments - 

This feature allows you import data from the Global data repository file or from an Excel sheet (.xlsx files only). Map Global data repository file with the test case step as per 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 (as shown in Repositories tab). Cyclic radio button helps you to run test steps again and again with different input data during the execution. On the other hand, when Continuous radio button is selected, data input argument(s) are used only once.

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

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

Select Test Step, navigate to the Step Output tab and provide 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.

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.

Mapping a Test step with a Step Output of an earlier test step -

This feature is used to reference keywords in a Test Case. The output of one test step can be made as an input for the other test step. This panel plays an important role in referencing steps with each other.

4.1.2 Executing a Test Case

noteThe Test Case can be executed by clicking over 'Run Now' & 'Debug Now' button which is described in upcoming section (Refer: http://opkey.com/Help/docs/opkey-help/execution-result/execution/


Creating test case by recording (Web & Mobile)


Quick Start Screencast

https://youtu.be/T4FMB7PPTjc

Overview:

Creating a Test case by recording is one of the most well known feature OpKey which helps you to record actions performed over the web application and create a Test case in a hassle free way.

  • Select a folder from project workspace and create a new test case file.
  • Go to the toolbar section and click on 'Record' button which provides three options: Web Recorder, Mobile Recorder, Desktop Recorder, Oracle Recorder, Salesforce Recorder & Workday Recorder.
  • To perform recording on the web applications you need to select Web Recorder
  • To perform recording on the Mobile applications you need to select Mobile Recorder
  • To perform recording on the Desktop applications you need to select Desktop Recorder
  • To perform recording on the Oracle applications you need to select Oracle Recorder
  • To perform recording on the Salesforce applications you need to select Salesforce Recorder
  • To perform recording on the Workday applications you need to select Workday Recorder
  • To perform recording on the iOS applications you need to select iOS Recorder

Let us first start with Web Recorder..

4.2.1 Recording on Web Applications:

When you click on 'Web Recorder', Web Recorder page opens.

There are two steps to be followed for start recording on a web application.

Step 1: Select Object Repository (Default Object Repository or Choose Object Repository)

Step 2: Select your Browser (Chrome AddOn or Smart Recorder)

An alert message pop up appears which asks you to keep OpKey Recorder jnlp file. Click on Keep to proceed the recording process.

Jnlp file gets downloaded every time and detects OpKey Smart Recorder, if it is installed on your machine then you are redirected for recording and if not installed then it redirects you to install the OpKey Smart Recorder.

noteIf the user invokes the recorder (OpKey Smart Recorder) on local machine before starting recording, then the process of downloading JNLP file will be skipped and user will directly be redirected to OR Selector window.

For further details, please refer installing OpKey Smart Recorder

While working with OpKey Web on Mozilla Firefox and using OpKey Smart Recorder for the first time, you will need to install the OpKey certificate on Mozilla Firefox manually (Please refer: Installing OpKey Certificate on Mozilla Firefox)

Java Runtime Environment (JRE) needs to be installed on your system to run jnlp successfully.

13

Further, your application gets downloaded.

14

Once downloading gets completed, your application gets verified.

15

A dialog box will open where you can create new or select existing OR file. Select your folder and click on Create New File icon. Choose desired browser on which you want to perform your recording operation.

16

(Here, we have chosen Google Chrome browser to record objects.)

Web Recorder home page opens as shown below:

17

Getting Familiar with buttons/icons used while recording:

recording-buttons

Now, you can perform your recording by clicking over the desired object on web application. Fetched object properties are shown in the bottom pane.

Objects fetched while recording, are shown in left upper pane with their name and the properties of recorded objects are shown in left bottom pane.

18

While performing recording operation, you can switch to a new browser by closing the current browser. To switch to a new browser, click on desired browser icon. A pop up message box will be displayed for closing current browser and opening new one. Click on OK to proceed.

19

In addition, you can also navigate to a new URL. For this, enter the desired URL in the URL bar and click on Navigate. The entered URL will open in your browser as well.

20

Once the recording process gets completed, click on Stop button. The browser will be closed, and you will be prompted to save and close the recorder

21

noteAn alternative way of starting the recording session is to right click on the test case steps. When you right click here, you get various options to perform actions like copy, paste, add step, delete etc. along with ‘Record’ option for recording on desired web application.

Right click on the Test steps provides you with various options, as shown in below screenshot. You can perform tasks corresponding to each options displayed on right click as well.

Once the objects get saved, you can see all the test steps, corresponding to your recording, on the Test case main window as shown below.

23

 

Spy mode of Recorder: 

Spy is an advanced feature of recorder which enables you to helps you observe page hierarchy and object property before working on it. This feature is very useful in case you have forgotten to fetch an object while performing recording. While fetching objects in Spy mode, keep holding Ctrl key and hover mouse over the desired object. Properties of spied object get fetched and displayed in bottom pane of the recorder window.

24

Hold 'Ctrl' button & Hover mouse on desired object > 'Object properties' are fetched

Click on 'Highlight' button > Targeted object highlighted within red square

Click on 'Click' button > Target object is clicked

In the above given images, the first image shows Spy feature home page without any object and the second images shows details about the properties of fetched object.

Now, the fetched object can be added directly to the step or to OR. If you want to add it to the step then click on Add Step button by choosing action from the drop down list. When you use Add Step button then this fetched object will be added within the current recording session only. Another way to use the fetched object is Add to ORBy using this button, you can directly add this fetched object to the corresponding OR which can be used as per your need, not only within this session but also with other sessions as well.

 

With the help of Relational APIs, you can find out the relation between the 'Set Pivot' object and the mouse hovered object. This relation describes the object location whether it’s nearby (leftOf, rightOf, belowOf and aboveOf) or within div (in).

Now, you can find out the dynamic object by setting pivot to any nearby static object. While recording on a web application having static & dynamic objects both, you first need to identify a static object. Hold Ctrl key and hover your mouse over the static object to fetch properties. Now, check 'Set Pivot' checkbox.

r01

Hold Ctrl key and hover mouse over the dynamic objects to fetch the current properties. Now, you can scroll down to see details about the fetched properties of this object along with its current location with reference to the static object (Set Pivot).

r2

note“Set Pivot” feature of Spy Recorder is very helpful for recording objects having dynamic properties. By using this feature, you can handle such situations easily.

 

4.2.2 Recording on Mobile device

One of the advanced features of OpKey is Recording on Mobile device which is similar to the Web recording. While doing this, you just need to follow few simple steps as described below:

Create a Test Case file & open it > Click on the "Record" button > Click on  "Mobile Recorder"

 

 

(A) Recording on Mobile devices over pCloudy:

https://youtu.be/DYcem5pU014

In the next step of mobile recording, you need to select the 'Object Repository' File where fetched objects will be saved. You can perform recording over pCloudy or locally connected device as shown in the image below. (Here, we are performing recording over pCloudy.)

r2

In order to access pCloudy devices, you must be a registered user of pCloudy along with enough credits for testing.

Enter all required credentials over pCloudy dashboard and click on 'Log In' as shown below:

r3

Further, you need to select your android application from the dropdown list and device from the device list. Click on 'Finish' to proceed.

r4

Mobile recording page opens as shown below. Left window shows the recorded objects and their properties etc. Right window shows connected device information.

Click on objects shown on the mobile screen to fetch their properties.

r5

Once recording process gets completed successfully, click on the 'Stop & Save' button. A confirmation notification appears. Click on 'Save'.

r6

You can see the Test Case file created, based on your recording actions over the mobile device. Now, you can execute your newly made Test Case and analyze execution result.

r7

 

 

(B) Recording on Locally connected Mobile devices:

https://youtu.be/oxz2ZApY5Ek

OpKey allows you to perform recording over locally connected mobile devices as well. But, you must register your locally device(s) before starting recording process.

Go to the "Tools" menu > Mobile Management > Device Management > Select your running Execution Agent > Click on "Register" icon for selected device.

register

Let us proceed to the recording over locally connected device...

Create a Test Case file > Click to the "Recorder" button > Select Mobile Recorder

Create or select your OR file to store all recorded objects > Click on "Local" button to start recording on your connected device. 

2

Select your Local running Execution Agent > Select connected Mobile device > Select your Mobile Application

3

Now, you can see that your selected application opens on connected device. It lets you tap or type on desired object which has to be recorded.

Here, you can see list of actions performed while recording along with objects and their properties.

r1

Click on "Stop and Save" button to save recorded test steps to your test case.

You can see the Test Case file created by recording actions performed on mobile. You can now playback this recorded test case and analyze your execution result as well.

r3

 

(C) Recording on iOS devices over pCloudy:

https://youtu.be/7x4SsePFSYo

  • Mobile Recorder window opens. From here, you need to select/create an Object Repository file to proceed recording on a pCloudy device.
  • Click Next to continue.

  • pCloudy Dashboard page opens. Enter API Endpoint, API User Name & API Access Key & click on Login.

  • From here, select an iOS Application, iOS version, corresponding iOS device, enter duration & click on Start Recording.


  • Mobile Recorder page opens. Start working on your iOS application on iOS device.
  • You can see that the actions being performed on the application has been recorded one by one along with their object properties.

  • The Test Case has been created automatically. You can have a look below.

Search Added Test Step:

While working with Test Case and Function Library artifact having few test step(s), you can search the added Test Step from the list of keyword library. You don’t need to browse and search for location of the particular Test Step from Add Keyword tab.


Search Added Test Step

 

4.2.3 Image based recording and playback on mobile

OpKey Web allows you to perform image based recording and playback on mobile device. Before starting image based recording, make sure that your mobile device is correctly connected and registered on your machine. In addition, OpKey Smart recorder is installed on your machine which is required for recording.

Follow below given steps: 

  • Launch OpKey Smart Recorder.
  • Open OpKey Web, create a Test Case and open it.
  • Click on the Mobile Recorder of Recorder button.
  • Select/Create OR file to store objects to be recorded.
  • Local Mobile Recorder window opens as follows. Select your Execution Agent, Mobile device and Mobile app and then click on Complete to proceed.

i1

  • The next step will take few moments to download and install app on connected mobile device.

i2

  • Once, it has completed, you come to the Recorder window as shown below. Click on Capture image to create new object button.

i3

  • Crop the image to be captured. You can see that the object has been fetched. Add corresponding action keyword to the captured step. Follow this step to capture all required images one by one.

i4

 

  • If you want to change the captured image then you can use Capture image to add into the existing object

i5

Once, recording has finished, click on “Stop & Save” button to stop and save the recorded steps and objects. Now you can see the created Test Case by performing image based recording.

i6

Now, go to the created OR file. Properties contain only one value as URL.

i7

Let us add two new properties by clicking Add Property button. You need to add Height and Width properties by providing their values which depends on the resolution of device on which recording has performed. Check IsUsed checkbox for both newly added properties. Click Save to save added properties.

i8

Further, you can execute your Test Case by using “Run Now” button for playback of the recorded steps by using OpKey Mobility Plugin.

4.2.4 Image based recording on web

While working on OpKey Web, the user can perform image based web recording. To do so, follow the steps given below: 

  • Create a Test Case and Click to Open it.
  • Click Record Button and select Web Recorder.
  • Your Recorder page will get open. Click on the desired browser icon (Google Chrome, Mozilla Firefox or Internet Explorer). 

i1

  • Type the URL of your web application.
  • Click on Capture image to create a new object button. An image type  object gets automatically added to the Recorder window.

i2

  • Crop the image. The Image gets captured and added to the Value of the Object attribute. Go to Action cell, add corresponding action (Keyword) to be performed on captured object. 
  • In this way, you can capture all required image objects one by one. You can also change/update any captured image by using Capture image to add into the existing object button.
  • Once all the images are being captured, you need to add corresponding action (Keyword)  with the captured images as shown below:

i3

  • Now, click on Stop & Save button to stop and save fetched image objects.

i4

  • Here, you can see that the Test Case has been created through image based recording on web.

i5

  • Click Save.
  • Click Run Now to execute the Test Case by using Sikuli as Generic  Plugin in Execution Wizard.


Creating Test Case by recording on IE & IE (Protected)


 Introduction:

OpKey allows users to create a Test Case by recording actions performed on Internet Explorer & Internet Explorer (Protected) browser. User can use any one of the Internet Explorer web browser and record his/her flows. OpKey Smart Recorder is used to record actions performed on the objects in web application.

Difference between recording on IE & IE (Protected):

While using Spy mode of recording object properties on Internet Explorer, you can spy object properties even when Internet Explorer browser window is not in focus. But, in order to fetch object properties through Spy mode, Internet Explorer (Protected) browser window must be in focus.

Objects locating in I-Frames under a Dome on the Internet Explorer web page, cannot be highlighted for recording objects whereas in Internet Explorer (Protected), objects can be spied and highlighted for fetching object properties.

Creating Test Case by recording actions on Internet Explorer

  • Create a Test Case & open it.
  • Click on the Record button and select Web Recorder.

  • Select Smart Recorder and then launch the Smart Recorder.
  • Select Internet Explorer and click on the Start Recording to proceed.

  • Perform actions on the web application. Actions being performed are getting recorded with Object Properties.

  • You can hover mouse on the desired object which gets highlighted with a red color circle.

  • Switch to the Spy mode of recorder. Keep pressing Ctrl button and hover mouse on the desired object.
  • Here, you can view that the Object properties of the Run object have been fetched.
  • You can now select an action from the dropdown and set to be performed on this object.

  • Switch to the Normal Record mode.
  • Once the recording session gets completed, click on the Stop & Save button.

  • Here, Test Case has been created successfully. Now you can execute it on any browser with specific plugin.

 

Creating Test Case by recording actions on Internet Explorer (Protected)

Quick Start Screencast:

https://www.youtube.com/watch?v=ZQB7clgtCdc
 

  • Create a Test Case & open it.
  • Click on the Record button and select Web Recorder.

  • Select Smart Recorder and then click on Open Start to launch the Smart Recorder.

  • Select Internet Explorer (Protected) and click on the Start Recording to proceed.

  • Perform actions on the web application. Actions being performed are getting recorded with Object Properties.

  • Switch to the Spy mode of recorder. Keep pressing Ctrl button and hover mouse on the desired object.
  • Here, you can view that the Object properties of the Run object have been fetched.
  • You can further select an action from the dropdown and set to be performed on this object.

  • Objects locating in I-Frames under a Dome on the Internet Explorer web page, cannot be highlighted for recording objects whereas in Internet Explorer (Protected), objects can be spied and highlighted for fetching object properties.
  • Here, you can view that the Object properties of the Run object have been fetched.

  • Switch to the Normal Record mode.
  • Once the recording session gets completed, click on the Stop & Save button.

  • Here, Test Case has been created successfully. Now you can execute it on any browser with specific plugin.

 


Creating Pre & Post Execution Report


Overview

OpKey has now been added with an all new advanced feature, Pre & Post Test Execution Report. This feature allows you to export Pre as well as Post execution report of the Test Case and Suite. You can upload your sample report(s) template of desired format (Word form) to the selected project from the Upload Templates tab in Reports under the Project Management of OpKey Admin. Later, you can update, export and delete the uploaded report as required. You can download Sample Template for your reference by clicking on the Download sample template button. Pre execution report feature allows you to generate a report of your test without doing the actual test execution of the flow whereas you can export Post-Execution report after completing test execution.

Need of Pre & Post Execution Report?

Execution Reports play an important role in the validation of test execution and its analysis. Now, OpKey is implemented with such advanced feature known as Pre & Post Execution Report (Pre & Post Validation Report). OpKey users were looking for such reporting feature. This reporting feature helps you to create Pre & Post execution report of your own sample uploaded in word format. Here, you can create your own format so that you can customize your format and add desired fields that you need.

Getting started with the Pre & Post Execution Report

Now, OpKey allows you to generate Pre as well as Post execution report for the Test Case and Suite. You don't need to execute the Test Case or Suite in order to generate the Pre-Execution (Validation) Report.

Before creating Pre or Post Execution report, make sure that you have uploaded sample report in OpKey from Reports (Beta) tab under Project Management in OpKey Admin Panel.

Uploading Sample Reports

  • Login to OpKey Web and switch to the OpKey Admin Panel.

  • Click on Upload Template icon to upload a new report template.
  • Select template and click on Open. Only a single template can be uploaded in one go.

  • Here, two template samples have been uploaded successfully. You can download a sample Validation report by clicking on the Download sample template icon.
  • You can update, export and delete uploaded template, as required.

  • Next tab, System Fields contains a list of the unique fields that can be added in the sample report to be uploaded which results filling of respective test data in the mapped fields in the Pre and Post-execution reports.

Note: System Fields (E.g. Test Script ID, Test Script Name etc.) in which test data will be filled in exported report, must be mapped under the Test Procedures table in the uploaded sample template. Go through the System Fields table for details about those fields, as showing above...

  • You can add your custom field tags from the Custom Fields tab in the selected project. Once you saved the newly added a new tag in Tag Name field, Field Name gets automatically added as per the set standard. While exporting Pre or Post-execution report, you can add Custom Field(s) and get added respective test data in the exported report.

  • Click on Add Tags icon to add new tag.

Creating Pre-Execution Report

  • Let us generate Pre execution report of a Test Case.
  • Open your Test Case, click on Run Now and then select Pre-Report option.

  • Fill required fields and click Next. Make sure that your OpKey Agent is online.
  • You can choose Step Hierarchy (One Level or Two Level).

Note: Step Hierarchy is the order level of Parent and child artifacts. If you choose One Level then report will contain only one level (Parents) whereas if you select two level then your report will contain Parent as well as child artifacts also.

  • From here, you can add Session Tags (Key & Value).
  • Click Finish to start creating Pre Execution Report.

  • Navigate to the Pre-Reports tab under dockable panel to view the status of report being created.

  • Pre-Execution Report has now been generated and you can download and view it.

  • Click on Download Report icon and then open it.
  • You can have a look at the Pre-Execution/Validation Report created successfully.

Creating Post-Execution Report

  • Let us generate Pre execution report of a Test Case.
  • Open your Test Case, click on the Execute under the Run Now button.

  • Fill all required fields of Local Execution Wizard.
  • Check Show Advanced Settings checkbox and click Next.

  • From here, you can apply Plugin Settings. Click Next to proceed.

  • Check Post Execution Report checkbox and click Next to proceed.

  • Post Report Settings (Beta) page which allows you to select Template, enter Report name, select Snapshot, Steps Hierarchy, Report Logo and then click on Next

  • From here, you can add Session Tags. Click Next to proceed.

  • From this step, you can choose a Global Variable and apply it.

  • Once the test execution gets completed successfully, click on the Export Report, select Post Execution Report and export it.

  • Now, here you can view your exported Post Execution Report in Word format.

Thus, we have successfully created Pre as well as Post Execution Report.