Participant Training Guide

2021

Version 12

Introduction to
Worksoft Certify®
Automation

Worksoft, Inc. · 15851 Dallas Parkway, Suite 855 · Addison, TX 75001 www.worksoft.com · 866-836-1773

1|Page
Introduction to Worksoft Certify Automation v11.0.0 Participant Training Guide
V1.0 last updated 03/01/2021

© Copyright 1999-2029 by Worksoft, Inc.

All rights reserved. All text and figures included in this publication are the exclusive property of Worksoft
and may not be copied, reproduced, or used in any way without the express written permission of
Worksoft. Information in this document is subject to change without notice and does not represent a
commitment on the part of Worksoft.

Worksoft may have patents or pending patent applications covering subject matter in this document. The
furnishing of this document does not give you any license to these patents except as expressly provided
in any written license agreement from Worksoft, Inc.

All other copyrights are the property of their respective owners.

Trademarks

Worksoft and Worksoft Certify are registered trademark of Worksoft Inc. All other trademarks and trade
names mentioned in this guide are the property of their respective owners.

2|Page
 Table of Contents
Overview _______________________________________________________________________ 7
About This Guide ______________________________________________________________________ 7
Training at a Glance ____________________________________________________________________ 8
Lesson 1 - Introduction to The Worksoft Platform _______________________________________ 9
Overview 9
Objectives 9
The Worksoft Platform _________________________________________________________________ 9
Business Process Testing Methodology ___________________________________________________ 10
Certify Architecture ___________________________________________________________________ 12
Worksoft Process Capture 2.0 ___________________________________________________________ 14
Lesson Summary _____________________________________________________________________ 14
Lesson 2 – Define Business Processes ________________________________________________ 15
Purpose 15
Objectives 15
Process Overview _____________________________________________________________________ 15
The Worksoft Web Sample Application ___________________________________________________ 15
Set an Optimal Capture Environment _____________________________________________________ 16
EXERCISE 2.1 — Configure Desktop Resolution _____________________________________________________ 16
EXERCISE 2.2 — Configure Windows Internet Explorer _______________________________________________ 16
EXERCISE 2.3 — Configure Google Chrome _________________________________________________________ 19
EXERCISE 2.4 — Create a Purchase Order __________________________________________________________ 19
Explore the Sample Application and Identify Processes _______________________________________________ 21
Use Process Capture 2.0™ to Record Business Knowledge ____________________________________ 22
Guidelines for Process Capture 2.0 _______________________________________________________ 22
Process Capture 2.0 Buttons ____________________________________________________________ 23
EXERCISE 2.5 — Install Process Capture 2.0 ________________________________________________________ 25
EXERCISE 2.6 - Configuring Capture _______________________________________________________________ 26
EXERCISE 2.7 – Configuring Web Options for Certify _________________________________________________ 30
EXERCISE 2.8 — Use Process Capture 2.0 to Record Purchase Order Creation _____________________________ 32
Lesson Summary _____________________________________________________________________ 36
Lesson 3 - Certify Navigation & Best Practices _________________________________________ 37
Overview 37
Objectives 37
Exploring the Certify Interface __________________________________________________________ 37
General Navigation Flow _______________________________________________________________ 38
Processes Overview ___________________________________________________________________ 39
Process and Data Editors _______________________________________________________________ 40

3|Page
 Identifying Processes __________________________________________________________________ 42
Designing Processes ___________________________________________________________________ 43
Naming Processes ____________________________________________________________________ 43
Worksoft Naming Convention – Best Practices _____________________________________________ 44
Accessing Worksoft Certify _____________________________________________________________ 47
EXERCISE 3.1 — Log in to Worksoft Certify ________________________________________________________ 47
Getting Started with Users and Groups ___________________________________________________ 47
Defining Certify Tasks for Users __________________________________________________________________ 47
EXERCISE 3.2 — Add Yourself as a User ___________________________________________________________ 49
Create Process Folders_________________________________________________________________ 51
Your Development Folder ______________________________________________________________________ 51
EXERCISE 3.3 — Create a Development Folder ______________________________________________________ 51
EXERCISE 3.4 — Add Folder Security ______________________________________________________________ 53
Create a Results Folder ________________________________________________________________ 54
EXERCISE 3.5 — Create a Results Folder ___________________________________________________________ 54
Lesson Summary _____________________________________________________________________ 56
Lesson 4 - Develop Functional and Integrated Processes ________________________________ 57
Overview 57
Objectives 57
Create a Functional Process ____________________________________________________________ 57
EXERCISE 4.1 — Import Process Capture 2.0 .XML File into Certify ______________________________________ 57
Parts of a Process Step_________________________________________________________________ 59
EXERCISE 4.2 — Modify the WSA_PO_Create Process and Execute Steps ________________________________ 61
Creating Child Processes from Selected Process Steps _______________________________________ 65
EXERCISE 4.3 — Create the WSA_PO_Create_C_Materials Process _____________________________________ 66
Certify LiveTouch Overview_____________________________________________________________ 72
Preparing to Use Certify LiveTouch _______________________________________________________ 73
Certify LiveTouch Menu Options _________________________________________________________ 74
EXERCISE 4.4 — Create the WSA_PO_Edit_QuantityAndPrice Process ___________________________________ 75
EXERCISE 4.5 — Create the UTL_LaunchWSA Process ________________________________________________ 91
EXERCISE 4.6 — Create the UTL_CloseWSA Process__________________________________________________ 95
Creating an Integrated Process __________________________________________________________ 97
EXERCISE 4.7 — Create & Execute IWCA_PO_CreateEditAndVerify Process _______________________________ 97
Lesson Summary ____________________________________________________________________ 102
Lesson 5 - Use Data to Execute Processes____________________________________________ 103
Overview 103
Objectives 103
Variables Overview __________________________________________________________________ 103
Preparing to Use Variables ____________________________________________________________ 103
Defining Variables in Certify ___________________________________________________________ 104

4|Page
 Use of Variables in Certify _____________________________________________________________ 105
Creating and Modifying Variables _______________________________________________________ 106
Adding Variables to Existing Process Steps________________________________________________ 106
EXERCISE 5.1 — Add Variables to Process Steps ____________________________________________________ 106
Execute Steps with Dialog _____________________________________________________________ 110
EXERCISE 5.2 —Execute Steps with Dialog to Show Variables _________________________________________ 110
Layout Overview ____________________________________________________________________ 111
Recordset Overview__________________________________________________________________ 111
Recordset Modes ____________________________________________________________________ 112
Define Layouts in Certify ______________________________________________________________ 113
Create a Layout Using Add to Layout ____________________________________________________ 114
Add to Layout Window _______________________________________________________________________ 115
Add to Layout: Assets Section __________________________________________________________________ 115
Add to Layout: Columns Section ________________________________________________________________ 116
EXERCISE 5.3 — Create the WSA_PO_Create Layout Using Add to Layout _______________________________ 117
EXERCISE 5.4 — Create the WSA_PO_Create_C_Materials Layout and Recordset _________________________ 120
EXERCISE 5.5 — Create a Recordset for WSA_PO_Edit_QuantityAndPrice Process (Optional) _______________ 123
EXERCISE 5.6 — Create a Layout and Recordset for the IWCA_PO_CreateEditAndVerify Integrated Process ___ 126
Execute Processes with Data ___________________________________________________________ 130
EXERCISE 5.7 — Execute Processes with Data _____________________________________________________ 130
Recordset Filters ____________________________________________________________________ 131
Recordset Filter for the Worksoft Web Sample Application __________________________________ 132
EXERCISE 5.8 — Using a Recordset Filter _________________________________________________________ 133
Export Data 136
EXERCISE 5.9 — Export Data ___________________________________________________________________ 136
Import Data ________________________________________________________________________ 138
EXERCISE 5.10 — Import Data __________________________________________________________________ 138
Lesson Summary ____________________________________________________________________ 141
Lesson 6 - Configure Execution and View Results _____________________________________ 142
Overview 142
Objectives 142
Execution Configuration ______________________________________________________________ 142
Settings Tab ________________________________________________________________________________ 143
Attributes Tab _______________________________________________________________________________ 145
Execution 145
Execution Buttons ___________________________________________________________________________ 146
Execution Dialog Box Tabs_____________________________________________________________ 147
Manage Execution Results ____________________________________________________________ 149
View Execution Results _______________________________________________________________ 152
Configure Advanced Execution _________________________________________________________ 154
EXERCISE 6.1 — Configure Advanced Execution ____________________________________________________ 154
Edit Process Steps from the Result Viewer ________________________________________________ 158

5|Page
 Generate Execution Reports ___________________________________________________________ 158
EXERCISE 6.2 — Generate an Execution Results Summary Report from the Results Window ________________ 159
EXERCISE 6.3 — Generate an Execution Results Detail Report from the Result Viewer _____________________ 160
Export the Test Process to a .BAT File ____________________________________________________ 161
EXERCISE 6.4 — Create a .BAT File ______________________________________________________________ 161
Lesson Summary ____________________________________________________________________ 164
Lesson 7 Certify System Objects and Actions _________________________________________ 165
Overview 165
Objectives 165
Certify System Classes and Actions ______________________________________________________________ 165
EXERCISE 7.1 — Create a System Commands Process _______________________________________________ 172

Lesson 8 Develop Advanced Processes ______________________________________________ 184

Overview 184
Objectives 184
Advanced Processes__________________________________________________________________ 184
Conditional Logic ____________________________________________________________________ 185
EXERCISE 8.1 — Create the WSA_PO_ExportRecordset Process _______________________________________ 191
EXERCISE 8.2 — Create the WSA_PO_UpdateRecordset Layout _______________________________________ 193
EXERCISE 8.3 — Create the WSA_PO_UpdateRecordset Process ______________________________________ 196
EXERCISE 8.4 — Create the IWCA_PO_DeleteByAmount Process ______________________________________ 211
EXERCISE 8.5 — Create the IWCA_PO_DeleteAll Process ____________________________________________ 224
Create an Integrated Process __________________________________________________________ 234
EXERCISE 8.6 — Create and Execute the IWCA_PO_DeleteByPrefixAndAmount Process ___________________ 234
Lesson Summary ____________________________________________________________________ 240
Lesson 9 - Resources ____________________________________________________________ 241
Overview 241
Worksoft Certify Resources ____________________________________________________________ 241
Access Worksoft Certify Help ___________________________________________________________________ 241
Certify Log File ______________________________________________________________________________ 241
Certify Diagnostic Tool ________________________________________________________________________ 242
Worksoft Community and Customer Solutions Site _________________________________________________ 243
Worksoft Help Portal _________________________________________________________________________ 244

Appendix _____________________________________________________________________ 246

Job Aids 246
Overview ___________________________________________________________________________________ 246
To create a process: __________________________________________________________________________ 246
To use LiveTouch to replace the current step: _____________________________________________________ 246
To use LiveTouch to insert one or many steps: _____________________________________________________ 246
To execute the entire process: _________________________________________________________________ 247
Start a New Integrated Process _________________________________________________________________ 247
Create a Layout Manually _____________________________________________________________________ 247
Create a Layout Using Processes ________________________________________________________________ 248
Create a Recordset ___________________________________________________________________________ 249
Add Layouts and Recordsets to an Existing Process _________________________________________________ 250

Course Evaluation ______________________________________________________________ 252

6|Page
Overview
About This Guide
Welcome to the Introduction to Worksoft Certify Automation training. This training guide
is provided to the students to keep and reference according to their own unique needs.
The guide contains instructions, exercises, examples, and definitions that will be needed
to complete this class.

In addition to the content included in this guide, there are available for review a series of
eLearning tutorials on various Certify topics. Students are encouraged to take notes.
They will find this helpful in refreshing their memory once they are back on the job.

NOTE: Guide material is not representative of your actual business data.

7|Page
Training at a Glance
This manual is divided into the following sections:

Lesson 1 – Introduction to the Worksoft Platform. This lesson will

introduce the Platform and Business Process Testing methodology; the Certify Life
Cycle approach; the Business Process Testing Components; and the role of
Process Capture 2.0 in Business Process Discovery.
Lesson 2 – Define Business Processes. Lesson 2 will show how to set up a
consistent environment by correctly configuring the desktop and browser
(Internet Explorer and/or Google Chrome), as well as Process Capture 2.0.
Students will record a process and save it to an .XML file for importing into
Certify.
Lesson 3 – Certify Navigation and Worksoft Guidelines. This lesson will
help students understand how to access and navigate Certify. Worksoft best
practices for naming and organizing processes, variables, layouts, and recordsets
will be covered as well as the concept of folder security.
Lesson 4 – Develop Functional and Integrated Processes. This lesson will
provide a better understanding of the difference between functional and cross
functional (integrated) processes. Topics will include how to import captured .xml
files into Certify; identifying the components of a process step; the methods of
adding steps to a process.
Lesson 5 – Using Data to Execute Processes. This lesson will explain how to
manage test data within Certify, including how to create and use variables,
layouts, recordsets, and recordset filters. The Certify test data import/export
process will also be covered.
Lesson 6 – Configuring Execution and Viewing Results. In this lesson,
more advanced execution techniques will be covered along with guidance on how
to view execution results in the Results Viewer. Also covered will be the method
used to generate and view execution results at either the detail or summary level
as well as how to create a .BAT file by exporting a process.
Lesson 7 – Certify System Objects and Actions. This lesson is a reference
chapter which covers Certify system objects and actions.
Lesson 8 – Developing Advanced Processes. This will cover creating
advanced processes that can interpret and react to different testing situations.
Topics will include simple tests versus robust tests, conditional logic, and tools
and methods for adding conditional logic to Certify automated tests.
Lesson 9 – Resources. This lesson will identify multiple resources which are
useful when working with Worksoft Certify as well as some guidance on how to
contact Worksoft for additional support.
Appendix – Job Aids. The Appendix provides useful job aids for common
Certify tasks.

8|Page
Lesson 1 - Introduction to The Worksoft
Platform
Overview
This lesson introduces Worksoft and explains the Worksoft Business Process Testing
methodology; the Business Process Testing Components; and how Process Capture 2.0
plays an important role in Business Process Discovery.

Objectives
After completing this lesson, students will:
• Understand the Worksoft platform.
• Understand and apply the Worksoft business process testing methodology.
• Understand how Certify is supported by the business process testing
methodology.
• Understand and identify the components of the Certify business process testing
methodology.
• Understand the purpose and components of the Certify life cycle
• Explain how the Certify Life Cycle approach mirrors Business Process Testing.
• Understand Process Capture 2.0’s role in Business Process Discovery.

The Worksoft Platform

Engaging a business’ subject matter experts, in a collaborative methodology that
requires as little of their time as possible, is critical. Worksoft’s collaborative methodology
and enabling technology is the only solution on the market that meets this critical
requirement.

9|Page
Business Process Testing Methodology
Business Process Testing is a methodology from Worksoft that parallels the software
development and deployment cycle but focuses attention on ensuring critical business
processes work.
Business Process Testing prioritizes the user tasks that carry the highest business risk.
Business risks arise from frequency of use or from the consequences of failure. For
example, a certain type of transaction may account for 80% of all daily tasks; therefore,
should be classified as high risk. Other types of transactions may be performed less
frequently, but if they fail, they have dramatic consequences.
In terms of the system life cycle, Business Process Testing is:
• The gateway to business operations.
• The point at which the business confirms that it can continue to carry on
uninterrupted when the software is introduced into production.
• An event that happens last in the system life cycle.
• Why is that so important? Because someone in a deadline crunch might skip unit
or regression testing but would take the necessary steps to certify his/her critical
business processes.
To effectively implement Business Process Testing, remember the following:
When determining coverage, prioritize by business risk. It is not necessary to
test every possible error condition, every bug ever detected, or each combination,
pathway, data type, etc. This distinction is crucial because it implies risk
management.
Accept the fact that you cannot test every scenario. The average commercial
application would require billions of tests to cover every possible circumstance.
Simple economics and physics prevent you from achieving complete coverage.
Define your success by what you do accomplish instead of what you don’t.
Business process testing shifts the focus from what is possible to what is essential.
The underlying logic is that if you can’t test everything, then you must test the
business tasks or processes that are most critical to the business.
Rate the identified defects by operational impact. When defects are found,
you should evaluate the impact of the defect on your business operations.

The result of the Business Process Testing methodology is a model

or profile of production that provides a known level of assurance
IMPORTANT:
that your critical business processes continue to operate as expected
even after software changes.

10 | P a g e
Certify Module
Certify is an integrated test repository and automated test execution solution that
supports the Business Process Testing methodology. The combination of the Business
Process Testing methodology and Certify allows you to parallel the entire product life
cycle and capture it in an organized, measurable, and maintainable way.
Certify provides focus on test coverage through a user-friendly, point and click interface
that can be used to document and automate test cases. Documenting test coverage
includes capturing and maintaining information about applications, business processes,
and operating cycles in a way that is standard across applications. This means
performing end-to-end certification of business processes that cross systems.
Automating test cases means using what has been documented to certify your
applications.
Certifies integrated components not only allow documentation and automation of test
cases, they also allow the tracking of progress in the certification effort and the
measurement of results throughout the complete product life cycle.
Certify’s complete life cycle approach allows execution of the certification process as
soon as the software is ready for test, instead of waiting to define or develop it. This, in
turn, provides more time and minimizes the impact of schedule slips.

Life Cycle
Business Process Testing Certify
Phase
• Identify application for test • Application(s) and Versions
Plan • Identity end users • Projects
• Capture business functions • Requirements
• Adopt naming standards
Design • Define critical business tasks • Process capture
• Define operating cycles
• Interfaces
• Define data elements
• Variables
Build • Develop test cases
• Processes
• Define data states
• Record sets
• Automated or Manual
• Execute certification
Test Execution
• Results
• Results Viewer
• Evaluate Results • Results Viewer
Evaluate • Identify Incidents • Queries
• Status analysis • Reports
• Receive New Application
Version or feedback from • Import
Maintain previous applications • Resolve Processes and
• Version Interfaces
• Reconcile application
Table 1 - The Life Cycle Approach Using Certify

Certify’s approach starts with planning the business process testing, designing the
automated processes, and building the actual test cases. Certify allows for the
documentation of all the business process components identified in the planning, design,

11 | P a g e
and build phases and store this information in a test repository. Once these three phases
have been completed, the business processes are then executed, the results are
evaluated, and the maintenance of the certification processes begins.

Figure 1 - Certify Life Cycle Approach

Certify Architecture
Certify maintains an inventory of all applications and their corresponding components.
These components are all tied together into a consistent and easy to understand
hierarchy.

Figure 2 shows how Certify organizes applications and components in a structured

hierarchy. A Project is a collection of requirements, processes, layouts, recordsets,
variables, and test results. Each project is independent, and information is not shared
between them.

An Application is a set of maps for windows and objects. Applications can be

available in one or more projects. Users are given access to Projects. A user may be
authorized to read and write everything in one project but can only read aspects of
another project.

12 | P a g e
 Figure 2 – Business Process Testing Components

Figure 3 - Certify Life Cycle Approach with Components

Figure 3 illustrates how the Certify components are used in a typical product life cycle.
There are four primary areas in this life cycle:

Components represent the artifacts created during planning, designing, and

building in Certify.
Database represents the repository where documented components are stored.
Applications represent the type of application being tested.
Data Analysis represents the data required for the certification.

13 | P a g e
Worksoft Process Capture 2.0
Worksoft Process Capture 2.0™ (Figure 4) is the most advanced object and action
recognition technology for automated business process discovery, documentation
generation, and testing acceleration. It is a standalone application that records a user’s
actions while completing a business process and enables both business users and test
automation professionals to create end-to-end tests.

Once Process Capture 2.0 is started, all interactions with your SAP GUI, Web,
OracleForms, and Mobile applications are captured. It is important to note that Capture
only creates steps for actions performed in the application, like modifying fields or
adding checks to check boxes.

Figure 4 - Worksoft Process Capture 2.0 Icon

Lesson Summary
The Introduction to the Worksoft Platform lesson is now complete.

Key points to remember:

• Worksoft’s Business Process Testing is a methodology that parallels the software
development and deployment life cycle but focuses attention on ensuring critical
business processes work.
• Worksoft Certify’s Life Cycle approach mirrors the Business Process Testing
methodology.
• Worksoft Process Capture 2.0™ is a standalone application that records
application actions while the business SMEs work through their business process.
Worksoft Capture plays an important role in Business Process Discovery.
• Making changes to systems that support mission critical business processes
requires constant collaboration between business users and IT. Process Capture
2.0 allows business users to quickly and accurately document existing processes.
This means IT users can more efficiently create and modify resilient test plans,
ultimately testing significantly faster.

14 | P a g e
Lesson 2 – Define Business Processes
Purpose
Ensure browsers area is prepared for the use of Worksoft Certify and other applications

Objectives
After completing this lesson, a student will be able to:
• Understand how business processes, test cases, and business functions are
related.
• Create a consistent capture environment by configuring your desktop and
browser.
• Configure Process Capture 2.0 for recording the Application Under Test (AUT).
• Configure the Process Capture 2.0 output to Certify.
• Use Process Capture 2.0 for Business Process Discovery.
• Record a process, using Process Capture 2.0, in the Worksoft Web Sample
Application.

Process Overview
In Certify, automated processes are used to validate and document the execution of
critical business processes. Processes typically map your existing test cases to the
business functions associated with the application being tested.

The Worksoft Web Sample Application

The Worksoft Web Sample Application (WSA) will be used to demonstrate the creation of
a simplified purchase order with header and material details via a web browser (HTML).
Process Capture 2.0 will be used to practice recording this business function.

The techniques learned in this course will be applicable to any interface, for example:
SAP GUI, HTML, Java, Oracle Forms, .NET, or Mobile.

We will use either Internet Explorer or Google Chrome to record

our process as outlined in the Optional Internet Explorer
NOTE: Configuration Exercise. Using Google Chrome requires the
extension addition outlined in the Optional Chrome
Configuration Exercise.

15 | P a g e
Set an Optimal Capture Environment
EXERCISE 2.1 — Configure Desktop Resolution
In this exercise, the desktop resolution will be set before using Process Capture 2.0. In
order to capture fields and screens correctly, desktop resolution must be set to 100%.

The following steps are for a Windows 10 environment. Your

screen may look different depending on your Windows
Platform.
NOTE:
If accessing Certify using Remote Desktop Protocol (RDP),
you must set the local machine’s scale and layout to 100%.
You may have to reboot the local machine to enforce the
new scaling settings.

Size must be 100% - Certify

Livetouch will not capture
properly

Steps Action Field Description / Data

1. Right-Click Desktop
2. Select Display Settings
3. Verify Scale and Layout set to 100%

EXERCISE 2.2 — Configure Windows Internet Explorer

If using Internet Explorer (IE) to develop and execute processes for the WSA, there are
certain setting adjustments needed in IE for the sample application to display correctly
and so that Certify can interact correctly with the application.

For any additional requirements, refer to the Worksoft

NOTE:
Certify Installation Guide.

Steps Action Field Description / Data

1. Open IE (Internet Explorer)
2. Tools

Click

16 | P a g e
Steps Action Field Description / Data
3.
Select (in drop-down
menu)
4. Check Box deselect
5. Check Box deselect
6. Click

Figure 5 – Compatibility View Settings

Steps Action Field Description / Data

7. Go to Tools

8. Select

9. Select

10. Find Check box –

Uncheck box
(optional step)

11. Click

12. Browse AUT URL https://training.cloud.worksoft.com/BasicSampleApp/

17 | P a g e
Steps Action Field Description / Data
13. Go to Tools

14. Select
15. Select
16. Select

17. Click

18. Find Check box –

Uncheck box
19. Verify the full or part
of AUT URL is
displayed in the
website field
20. Click
21. Click
22. Click

Figure 6 – Internet Options and Trusted Sites

18 | P a g e
EXERCISE 2.3 — Configure Google Chrome
If using Google Chrome to develop and execute processes for the WSA, a Worksoft
extension file must be added to Chrome. This extension allows Certify to interact
correctly with an application opened in Chrome.

Steps Action Field Description / Data

1. Open Google Chrome
2. Enter Address bar - Chrome://Chrome
3. Review Version

For Chrome versions 28+, you will need the

Worksoft Automation Extension.crx file

C:\ Program Files

(x86)\Worksoft\Certify\Interface
Client\Worksoft\wsTest\HTML.
4. Enter Address bar – Chrome://Extensions
5. Drag and Drop The extension file from Program Files to the
Chrome Extension page
6. Accept Chrome will requre approval to add extension
7. Select Add Extension
8. Verify Extension is Enabled
9. Select Allow access to file URLs
10 Verify Close and Reopen the Chrome broswer. The
highlighted icon below indicates, Worksoft
Automation extentions has access to the sites.

Figure 7 – Google Address Bar

Congratulations, Chrome browser is now ready to use with Certify.

EXERCISE 2.4 — Create a Purchase Order

User will become familiar with the HTML application under test (AUT) by accessing the
Worksoft Web Sample Application and creating a purchase order.

Steps Field / Action Field Description / Data

1. Open browser & https://training.cloud.worksoft.com/BasicSampleApp/
enter

19 | P a g e
 Figure 8 – Web Sample Application or Application Under Test (AUT)

To create a purchase order, type in the following field values:

Steps Action Description

1.
Enter PO Number 1234
2.
Enter Name Mary Wilson
3.
Enter Ship to 3000
4.
Enter Bill to 3000
5.
Enter Material P-100
6.
Enter Quantity 1
7.

Enter Price 2482 (Do NOT use punctuation)

8.
Click Save

ActiveX controls must be enabled to run the sample

IMPORTANT: application. If an information bar appears, right-click and
select “Allow Blocked Content” to turn the feature on.

20 | P a g e
Explore the Sample Application and Identify Processes
Review Table 2 below for the processes that will be reviewed using the Basic Sample
Application, Process Capture 2.0 standalone application and Certify Capture.

Critical Business
Sub-Processes Description
Process
Creates a purchase order in the
Worksoft Web Sample
Application; a verification steps
selects the most recent
WSA_PO_Create
purchase order, verifies the
purchase order number, and
stores the document number
for future use
IWCA_PO_CreateEdit A reusable child process that
AndVerify WSA_PO_Create_C_Materials enters multiple materials for a
purchase order
Selects a purchase order and
WSA_PO_Edit_QuantityAndPrice edits a specific material’s
quantity and price
Launches the Worksoft Web
UTL_LaunchWSA
Sample Application
Closes the Worksoft Web
UTL_CloseWSA
Sample Application
Exports the WSA_PO_Create
WSA_PO_ExportRecordset
recordset to a .txt file
Adds each purchase order’s
amount to each record
imported to the
WSA_PO_UpdateRecordset WSA_PO_UpdateRecordset
process and exports the data to
a txt file
IWCA_PO_DeleteByPr
Identifies and deletes any
efixAndAmount
purchase order with an amount
less than $6000. This will limit
WSA_PO_DeleteByAmount
purchase orders in the WSA
Purchase Order Table by the
amount criterion
Identifies and deletes all
WSA_PO_DeleteAll purchase order on the Purchase
Order table.
Table 2 – Processes to be Reviewed

*IWCA – Introduction to Worksoft Certify Automation

*WSA – Web Sample Application

21 | P a g e
Table 2 shows the critical business process and sub-processes needed to satisfy the test
requirements for the Worksoft Web Sample Application. Depending on the test design,
verification steps do not need to be in a separate process.

Certify Administrators: Once you have defined all the

processes for your application, you should go back to your
list of requirements and create links between the
IMPORTANT:
requirements and the defined processes. Once the processes
are executed, you can run a Requirement Coverage report to
validate whether the requirement was met. These tasks are
covered in Certify Administration training.

Use Process Capture 2.0™ to Record Business

Knowledge
Worksoft Process Capture 2.0™ plays an important role in Business Process Discovery.
Business users leverage Process Capture 2.0 to discover end-to-end business processes
across all departments. It provides the flexibility to capture all the business process
information in a non-interventional mode, making it easier for business users to
collaborate with IT without the need for interview cycles or detailed knowledge transfer
meetings.
Process Capture 2.0 is a standalone application that records actions while working
through a business process. Processes captured can be automatically sent to Worksoft
Analyze, where the captured information can be used to analyze business processes and
generate automation and visualizations. Or the processes captured can be saved as an
.XML file, in a network directory, and then imported into Certify.

Once Process Capture 2.0 is started, all interactions with SAP GUI, Web, OracleForms,
and Mobile applications are captured. It is important to note that Process Capture 2.0
only creates steps for actions performed in the processes. For example, fields that are
modified or check boxes that are checked.

Guidelines for Process Capture 2.0

• Know the business process flow and data before starting Process Capture 2.0.
• Capture as many business processes as deemed critical to quality.
• Capture the business process as real users perform the activity.
• Use the Naming, Comment, Screenshot, and Verify features of Process Capture
2.0 to record detailed and comprehensive process steps.
• Capture of SAP GUI activities are named automatically based on the transaction
code.

22 | P a g e
Process Capture 2.0 Buttons

Figure 9 – Process Capture 2.0

Options Details

Delete a captured step

View Details

New Process Using Certify Capture

23 | P a g e
Options Details

Open existing xml file that contains captured steps

Append a Capture – to merge two captures together. Add a saved

Capture to the end of another Capture. New in version 11.5

Image Objects – only used to define certain type of Silverlight

graphical objects that cannot be discovered by LiveTouch. A
graphical object is a collection of one or more graphical images in an
application. New in version 11.5

Add a comment - Commented steps are ignored during the

execution process.

Add an Activity – to add a description of max 128 characters. In

SAP, it’s inserted automatically based on the T-Code description

Capture Screenshot – of active window or screen

Capture Button – to start and stop capturing process steps

Save the captured steps to generate a XML file.

LiveTouch – to make a or multiple object selections. Click on the

same button again or press <Esc> key to end LiveTouch

Main Menu button to select other options to assist Process Capture

2.0

24 | P a g e
EXERCISE 2.5 — Install Process Capture 2.0
This exercise will cover the installation of Process Capture 2.0. If Process Capture 2.0
has already been downloaded and installed, this exercise can be skipped.

Steps Field / Action Field Description / Data

1.
Open File Explorer
2. Go to & Double Click Local Disk C:
3.
Go to & Double Click Program Files (86)
4. Find & Double Click Worksoft Folder
5. Worksoft Process Capture 2.0
Open & Double Click
6. Worksoft Process Capture 2.0
Find & Double Click again
7.
Locate ProcessCapture2.exe

Figure 10 – Process Capture 2.0 location

Steps Field / Action Field Description / Data

8. Double Click To install (if not on PC)
9. Automatic Installation Wizard Opens
10. Click Next (click next until installation finishes)
11. Click Finish
12.
Verify Process Capture 2.0 is on Desktop

25 | P a g e
EXERCISE 2.6 - Configuring Capture
Steps Field / Action Field Description / Data
1. Find Process Capture 2.0 Icon on Desktop
2. Open Process Capture 2.0
3. First time Users opens Capture this screen will
display – Worksoft Administrator/IT Dept should
provide this information to users.
Initial Screen Enter the following for training
Enter Provided URL
and Tenant Name

4. Options Button

Select

26 | P a g e
Steps Field / Action Field Description / Data
5.

Displays

6. About Capture

Click

7. Capture Diagnostics

Click

8. Capture Name and Description

Click

9. Enter Name and Description or leave blank

27 | P a g e
Steps Field / Action Field Description / Data
10. Capture Settings

Click

11. Select Same values as displayed

12.

Select – Interface
Options

13. The Program to be worked with for this capture

Select session – Best Practice is to select only the
interface that you will capture.
14.
Click
Options pencil for Analyze
15.

Enter information

16.
Click
Options pencil for Mobile

28 | P a g e
Steps Field / Action Field Description / Data
17.

Enter Information

18.
Click
Options pencil for SAP
19.

Select Options
Desired

20.
Click
Options pencil for Web
21. Web Options
Configuration and Optimization Options

Search & Select –

Matching

22. Internet Explorer performance engine is

selected
Verify

23. Maximum Number of Seconds to generate

attribute

Set

29 | P a g e
Steps Field / Action Field Description / Data
24. Save Options

Select (if available)

25.

Click- Tips

26. Close
Click

IMPORTANT: Close is the save button

EXERCISE 2.7 – Configuring Web Options for Certify

Steps Action Field Description / Data
1.
Locate Worksoft
Certify Icon

Double Click

2.

Enter User Name

Enter Password

3.
Select Ok

30 | P a g e
Steps Action Field Description / Data
4.

Menu: Configure >

Web > Options

6.

Select Global
Settings tab

Note: User Settings

override Global
Settings. If User
Settings are left
empty Certify will
use Global Settings
for web application
automation.

7.

Select Configuration
Tab in middle of the
page

31 | P a g e
 Steps Action Field Description / Data
8. Select The user
Settings Tab

Select the
Configurations
dropdown – Choose
WebAccoutManager
Configurations

Select Definitions
dropdown – Choose
WebAccountManager
Definitions

Select Execution
Engine dropdown –
CrossBrowser

Select Cross
Browser Live Touch
dropdown – True

Scroll Into View -

Middle
9.
Select Close
10.
Select Minimize
Certify

EXERCISE 2.8 — Use Process Capture 2.0 to Record Purchase Order

Creation
This exercise will walk thru the configuration steps needed to allow Process Capture 2.0
to work with the WSA. Capture will be configured to save to Worksoft Analyze and to an
.XML file for importing into Worksoft Certify. The process will then be captured to create
a Purchase Order in the sample application.

Process Capture 2.0 can recognize Mobile, OracleForms, PeopleSoft, SAP GUI, SAP
Fiori/S4HANA, and web interfaces. It is a Worksoft Best Practice to only enable the
interface(s) being used for the current capture. If given an eXtensibility Framework (XF)
class definition from Worksoft Support or Professional Services Team, select those
options (when working with the application) from the Configuration and Optimization
drop-down list.

32 | P a g e
Steps Action Field Description / Data

1. On any Web https://training.cloud.worksoft.com/BasicSampleApp/

browser, navigate
to AUT:

2. Process Capture 2.0 Icon to start program

Double Click

3. Options Buttons
Select
Check all Options to see that Capture is set to the
correct Program every time Capture is opened.

4. Select Capture button

5.
Click Activity Button
(when not using SAP GUI)

6. Enter Text WSA_PO_Create

7. Click OK

8.
Enter PO Number
1234

9. Enter Name Mary Wilson

10. Enter Ship To 3000

11.
Enter Bill To 3000

12. Select Comment Button

13. Enter Comment “Create a child process for the Material table”

14. Select OK

16. Select LiveTouch – (fingerprint button)

17. The Material table with LiveTouch until the table

Select
has a box surrounding the object only

33 | P a g e
Steps Action Field Description / Data

18. Click LiveTouch to turn off LiveTouch

19.
Press
Save in the Sample Application

20. Select to enable liveTouch

21. Select the “An Item is created” message

Select

22. The Action Table

Select

23. Select to disable liveTouch

24. Press Screen Capture button

25. Select Active Window or Screen

26. Select Ok

27.
Select
Capture button to Stop

28. Select Save Button

29. WSA_PO_Create as the file name. Note where

Enter
the file was stored

34 | P a g e
 Figure 11 – Captured Steps and Sample Application with a new PO

Now that the first Capture has been created, let us review some additional buttons in
Capture that will assist in finishing the process.

Steps Action Field Description / Data

1. Select Eye button
2. Object Tab – Field name Detail

Review

3. Window Tab - Name field object is found

Review

35 | P a g e
Steps Action Field Description / Data
4. Step Tab - view the specific step’s details

Review

5. Select to close Process Capture 2.0

Within Process Capture 2.0, users can review each step’s

Object Window and Step detail prior to saving and importing
NOTE:
the capture process. This provides users with the abiltiy to
troubleshoot and edit difficult objects prior to importing

Lesson Summary
The Define Business Processes lesson has been completed.
Key points to remember:
• Business processes typically mirror a business’ test cases.
• Process Capture 2.0™ can be used to document and validate the end-to-end
execution of critical business processes and has a role in Business Process
Discovery.
• As a Worksoft best practice, larger business critical processes should be broken
into smaller components/unit processes to facilitate reuse of those components.
• It’s important to create a consistent environment when using Process Capture
2.0™ to record the business processes.
• The captured process, with all the detailed comments and validation points, will
help reduce the efforts of the automation team by up to 40%.
• Process Capture 2.0™ can record processes in SAP GUI, Web (HTML),
OracleForms, and Mobile interface applications.
• Process Capture 2.0™ can output recordings to both Worksoft Analyze and
Worksoft Certify.

36 | P a g e
Lesson 3 - Certify Navigation & Best Practices
Overview
This lesson will show how to access and navigate within Certify. It also covers the Worksoft
best practices for naming and organizing processes, variables, layouts, and recordsets as
well as how to secure processes and folders.

Objectives
After completing this lesson, a student will be able to:
• Navigate the Certify Main Window.
• Navigate the Certify Process Editor.
• Understand Worksoft best practices.
• Create and secure process and result folders within Certify.
• Explain what processes are and how they are used.
• Design and name processes following Worksoft Guide

Exploring the Certify Interface

Menu Bar

Toolbar

Navigation
Tree

Summary
Navigation
Pane
Taskbar

Detail
Pane

Status Bar

Figure 12 — illustrates the seven sections of the main Certify Interface.

37 | P a g e
 Menu Bar — contains menus of functions and commands needed to carry out tasks
in Certify. Some menu options become inactive depending on the task selected in the
Navigation Taskbar.
Toolbar — gives quick access to commonly performed actions. The buttons are
specific to the selected tasks in the Navigation Taskbar.
Navigation Tree — contains a hierarchy or tree view of the selected project
component or administrative module.
Navigation Taskbar — contains the buttons to access key Certify components. The
button or task chosen affects what is seen in the Summary and Detail Panes. Specific
user access to these buttons is controlled by a Certify administrator.
Summary Pane — located on the top right-side of the primary window. This pane
shows dynamic, display only information that changes depending on the task and
nodes selected in the Navigation Pane.
Detail Pane — located on the bottom right-side of the primary interface (beneath
the Summary Pane). It contains tabs of information related to the items in the
Summary Pane. This information is also dynamic and display-only.
Status Bar — located on the bottom left-side of the screen (beneath the Navigation
Taskbar). It displays the name of the open project.

General Navigation Flow

There is a consistent pattern to navigating the interface elements previously discussed.
Depending on the task to be performed, select the appropriate button in the Navigation
Taskbar. The other elements change to reflect the data contained in the chosen area. Next,
select a node in the Navigation Tree. Related items then appear in the Summary Pane.
Next, select an item in the Summary Pane to carry out tasks (as shown in Figure 2) or click
on the tabs in the Detail Pane. Tasks can also be performed in those tabs (other than the
Details tab). Certify actions are accessed by a right-click.

Users will follow a clockwise pattern repeatedly as you learn

IMPORTANT:
about and carry out tasks within the various Certify conponents

38 | P a g e
 Figure 13 — Relationship of Certify Interface Elements

Processes Overview
In Certify, processes are used to document and validate the end-to-end execution of critical
business processes. Processes typically map existing test cases to the business functions
associated with the application under test.
Processes consist of a series of individual steps where a step performs an action against an
object. Actions can include entering or verifying a field value, pressing keys or buttons, or
verifying results like field values, object states, or messages.
Each process performs a discrete function, such as adding an order or finding an existing
order. When defining processes, select the objects and actions to reflect how the
application operates.

39 | P a g e
Process and Data Editors
Work associated with defining and using processes is carried out in the Processes window
and Process Editor. As shown in Figure 13, the Processes button has been pressed in the
Navigation Taskbar and the corresponding process folder hierarchy is shown in the
Navigation Tree. A folder called “CA” was chosen and the contents of that folder, the list of
processes created for this functional area, are shown in the Summary Pane. The process
“CATS_TimeManagementTimeEntry” was selected from the Summary Pane, and the details
about that process are shown in the Detail Pane.

Figure 13 — Process Window Interface

Once the existing process has been selected as in Figure 13, clicking on the Edit button

from the Toolbar Menu takes you to the Process Editor, shown in Figure 14. The

Process Editor can also be accessed by pressing the New button from the Toolbar
Menu.

40 | P a g e
 Figure 14 — Process Editor Interface

The Process Editor screen is divided into two sections. The left section of the screen is the
Navigation Tree. This section displays, at a high level, the steps and sub-processes
contained in the process being edited. The right section of the screen contains tabs which
allow editing of specific elements of the process. These elements are Details, Steps,
Recordset, and Attributes.

The Process Details tab is the default tab and contains the following information…
Description – The description provides quick insight as to the purpose and
functionality of the test and will be used by other automation engineers when trying
to identify re-use candidates.
Layout Name – This is the name of the associated data layout which will hold the
test data necessary to execute the process. The user can add/change/remove the
layout. Hovering over the layout name will show the specific folder structure location
of the layout.
Recordset Name – This is the name of the data recordset associated with the
process and layout.
Recordset Mode – This field tells Certify how the recordset will be used by the
process…read, append, update.
Development Status – This process attribute helps track the status of the
automation progress. Some of the choices are development, testing, and complete.
Owner – This field contains the name of the process owner. They user can
add/change/remove the owner name.
Folder Name – This is the file folder location of the process being edited.
Project Name – The name of the project which contains the process being edited.

41 | P a g e
The Steps tab will show the user the detailed steps contained in the process and specific
attributes about each of the steps including…
Parameters – All of the specific parameters associated with the specific step.
On True/On False – Parameters which instruct Certify what to do when a step
passes/fails.
Linked Requirements – The name and location of any linked requirements
information pertaining to the step
Images – Any specific images like screen shots or values associated with the step.
The Recordset tab will shows the information about the recordset linked to the process.
The user can tell Certify to import/export data to/from the recordset or use Certify Data to
help retrieve test data. Other information includes…
Name – The name of the associated recordset
Description – A brief description of the recordset
Data Content – The actual data contained in the recordset
The Attributes tab contains all the user defined attributes associated with the process.
Commonly used attributes include functional area, process status, planned start, planned
completion, and process type.
Once all steps are entered and the process is saved, it appears in the Summary Pane (see
Figure 3).

Identifying Processes
The key to successfully testing your application is to first identify all the business-critical
processes. Each of the identified processes will have a series of activities or steps that
define the correct way to execute the business process. In many cases, a business-critical
process could be made up of several smaller processes that focus on functional areas or
navigation.
Per best practices, consideration should be given to breaking down cross
functional/integrated processes into multiple unit tests or components. Doing this supports
the key concept of reuse in which others can use these components as building blocks for
future automation, reducing the need to create new processes. For instance, navigation to
a window and pressing a button would make up a navigation process that can be reused. A
VF01_CreateBillingDocument process can be reused, meaning it can be called from one or
more other end-to-end process.
The actual number of processes which need to be created will vary based on the size and
complexity of your application.
To assist in identifying the processes needed for an application, try these methods:
• Analyze the requirements to determine how many processes are needed to
thoroughly cover each type of feature or function.
• Analyze the functional areas of the application to determine if any existing processes
could be reused to make the processes more efficient.

42 | P a g e
 • Verify that each process maps to a requirement that covers a business function or
feature.
• Organize your identified processes by business function and adopt a naming
convention that will ensure your processes are easy to locate. (See “Naming
Processes” for naming guidelines.)

Designing Processes
Good process design is critical to the success of automated testing. A good test design will
help ensure the elimination of manual intervention during execution, reduce development
and maintenance time, and will foster faster execution times.
When planning a process, keep these guidelines in mind:
• All transactional or component processes should be created for the purpose of being
reused in multiple automated tests.
• Good test data management will help ensure that a process will run without manual
intervention. Required test data should be automatically created as an integral part
of the automation.
• Audit (validation) points must be included in the test. All validation/audit points
should include a screenshot for audit purposes. Every test should have a pre-
determined outcome that is proven with the validation point.
• Tests should be linear. Avoid complex logic.

Naming Processes
Per Certify best practices, it is wise to invest the time to develop and follow a process
naming convention. As test volumes expand and assets are transferred among users,
naming conventions help to promote reuse and reduces confusion. Ideally, names are
descriptive enough that their purpose and use is immediately clear and external
documentation is not needed.
It is important to note that Certify lists are often sorted alphabetically and can be searched
using filters based on name, description, keyword, and user defined fields. For example,
processes called AddCustomer and UpdateCustomer would not appear together in an
alphabetic sorting, while CustomerAdd and CustomerUpdate would. On the other hand, the
former structure could yield a useful list if a filter were created on the word Customer within
the name field. These types of naming standards are essential to designing a reusable,
maintainable test suite.
As a best practice, start your process names with a name common to the area being tested.
It may be an acronym for a functional area or application like GL for General Ledger, AP for
Accounts Payable, or CRM for Customer Relationship Management.
For HTML based applications, start your process names with the window name, followed by
an underscore, and finally the action to perform. For example, WSA_PO_Create and
UTL_LaunchWSA would describe two processes that use the same page Web Sample
Application (WSA) but the actions are different.

43 | P a g e
As another guideline, you should plan to organize your processes into folders that describe
the processes contained within the folder. For example, you could have a folder called
IWCA_PO_CreateEditAndVerify containing the integrated critical business processes, as
well as the sub-processes within that integrated process.

Worksoft Naming Convention – Best Practices

This section describes naming conventions for Certify concepts that you have not yet
learned (e.g. Variables, Data Layouts, and Recordsets). As you look through this section,
you will see how the naming conventions work together. Later, when you begin using these
concepts, you will use these conventions.

Component or Unit Test

• SAP transaction codes (T-codes) or components are capitalized.

• Separate descriptions by an underscore (_).
• Remove spaces from descriptions and capitalize the first letter of each word.

Format : TCode_Description1_Description2_Description3
ACRONYM_ComponentDescription

SAP Example: VA01_CreateStandardOrder

VA01_CreateStandardOrder_MultipleItems

HTML Example: WebOrder_CustomerCreateMyPortal_RegisterStudent

If a process uses a child process to work with a multi-element object such as a table or
grid, it should be extended with the parent process name +, _C, + additional description.
This will ensure the parent and child processes are sorted next to each other.

Example: VA01_CreateContractOrder_MultipleItems
VA01_CreateContractOrder_MultipleItems_C_TableInput

SAP Human Resource Design

• For transactions that encapsulate functionality (for example HR transactions such as

PA30 and PA40), it is best to subdivide processes further than the transaction level.
• The use of Info Types is recommended for naming and defining processes.
• HR processes may also be grouped by Country or State (e.g. CA for Canada or CA for
California).

Format: Tcode_IT<ITypeNumber>_<InfoTypetext>_<Country or State>

Examples: PA40_IT0068_GarnishmentCompensation_CA

44 | P a g e
 PA40_IT0068_NewInitialBalance
PA40_IT0071_PensionFunds_GB

Integrated or End-to-End Process

• Separate test names and descriptions by an underscore (_).

• Remove spaces from descriptions and capitalize the first letter of each word.
• Integrated Processes contain only calls to other processes and Comments.

Format:ApplicationArea_Description1_Description2_Description3

Example: OTC_ShipBill_ConstantQuote
CRM_CustomOrder_ProcessThroughSAP
WebOrder_FromBrowser_ToSAP_ToMainframe

Variables

• Named the same as the field it represents.

Format: Variable names will closely resemble field names

Example: Order Type

Ship-to-party
Exp.Date

If a field needs more than one variable (e.g. Requested delivery date as a Text type
variable and as a Date type variable), then delimit the variable with the difference – such as
a _VariantName.

Format: Req. deliv.date_Format Type

Example: Req. deliv.date_Date

A field may appear on the screen multiple times such that you need different values for
each occurrence. The same variable name should be used with a ‘#’ to indicate that it
indeed is a necessary variable and not a duplicate of an existing variable.

Example: Customer#1 is not equal to Customer#2

Layouts

• Named exactly as the process name.

• Variant Layouts will have the same name as the Process name plus identifier.

Format: Layout Name = Processes Name (not manual test case name)

45 | P a g e
 Example: Process Name = VA01_StandardOrder
Layout Name = VA01_StandardOrder

Process Name =MM01_CreateMasterData

Layout Name = MM01_CreateMasterData

Integrated Test Name = O2C_ShipBill_ContractQuote

Layout Name = O2C_ShipBill_ContractQuote

Most Certify processes have only one layout. However, there may be a need to have more
than one. In this case, use the same name as the original layout and add a variant
identifier.

Example: Process Name = MM01_CreateMasterData

Primary Layout Name = MM01_CreateMasterData
Secondary Layout Name = MM01_CreateMasterData_3rdPartyData

Recordsets

• When implementing the Recordset naming convention, use the Process Name as the
recordset name. Be descriptive as possible when naming recordsets.
• Recordset names will, in most cases, match the Process name and Layout name
being created. Any number of recordsets are possible for any given test.

Format: Process Name_Purpose

Example: Process Name = VA01_StandardOrder

Layout Name = VA01_StandardOrder
Recordset Name = VA01_StandardOrder
Recordset Name=VA01_StandardOrder_InternationalCustomers
Recordset Name = VA01_StandardOrder_NationalCustomers

Example: Integrated Test Name = O2C_ShipBill_ContractQuote

Layout Name = O2C_ShipBill_ContractQuote
Recordset Name = O2C_ShipBill_ContractQuote_Europe
Recordset Name = O2C_ShipBill_ContractQuote_China

46 | P a g e
Accessing Worksoft Certify
To use Certify, it must first be launched, and credentials must be entered to log in
successfully. Once logged in, the interface and navigation can be explored and learned.
User security is also maintained in Worksoft Certify.

EXERCISE 3.1 — Log in to Worksoft Certify

In this exercise, log in to Certify for the first time using the username and password
provided by your instructor or Worksoft Administrator.

Steps Action Description

1. Start > All Programs > Worksoft > Certify > Worksoft
Click Certify or select the on the desktop to
launch Worksoft Certify
2. User ID & Password in Dialog box

Enter

(Initially use “admin & password”)

3. OK
Click

Getting Started with Users and Groups

Worksoft Certify utilizes – Users, Groups and Permissions to secure process definitions and
folders. After logging into Certify, the administrator will need to create users for everyone
who will need access to Certify. To limit access, admin will can create groups with
customized permissions and add users to these groups.

After logging in the first time as a Certify administrator, it’s highly recommended to change
the password for the admin login to maintain security.

Defining Certify Tasks for Users

Certify administrators create the users and groups within Certify and assign them
permissions. Depending on the type of user, administrators can limit the permissions to
specific tasks. Certify has a set of views that you can select for each type of user:

47 | P a g e
 Figure 15 — View Menu
User Description

Administrator Administrators are expected to install Certify, set up users and groups,
create applications and versions, and create projects. Administrators have
duties on the front end of Certify, and then they leave other functionality
to other users.

Use the Certify view for administrators by selecting View >

Administrator in the menu.

Manager Managers have a broad array of responsibilities that includes assigning

work, checking progress, reassigning resources to areas of critical need,
and assessing overall progress toward team goals. Even though these
users may do some Worksoft application work, most of their interactions
with Worksoft applications will be related to administration, planning, and
reporting.

Use the Certify view for managers by selecting View > Manager in the
menu.

Business Business analysts are regular users of Worksoft applications, but they
Analyst usually do not test software. These users might spend an average of a
few hours a day using Worksoft applications. This load may vary over
time with peak loads occurring as part of product release cycles.

Business analysts may use their expertise to create tests while other
groups may be responsible for managing tests, running regression suites
against nightly builds, forwarding builds to quality engineers, and
preparing patch releases.

Use the Certify view for business analysts by selecting View > Business
Analyst in the menu.

48 | P a g e
Quality/ Quality engineer personnel are the most frequent users of Worksoft
Automation applications. Using Worksoft applications are a primary function of these
Engineer users’ daily work. They are expected to use most of the functionality
available in Worksoft products including creating and executing processes
and creating and viewing reports.

Use the Certify view for quality engineers by selecting View > Quality
Engineer in the menu.

EXERCISE 3.2 — Add Yourself as a User

In this exercise, define your user profile and add it to the ReadWriteExecute group.

These functions may have already been

Note: preformed by an Administrator. If so, then skip
to next exercise

Steps Action Description

1. Navigation Taskbar Users & Groups
2. Navigation Tree Right
Click Users Select New User
3.
Input User
information
- First Name
- Last Name
- User Name
(unique
identifier used
by company)
- Email address
- Role

49 | P a g e
Steps Action Description
4. Input User
information
- New Password
- Verify
Password
- Force Password
Change on
login (not
recommended
in class)
- Password
Never Expires –
Select Radio
Button
- Password
expires - In
Days/ On Date
5. Current Groups Containing white space

Right Mouse Click to

add Groups

6. Select Add Group

7. ReadWriteExecute Group

Select

8. OK
Select

9. Group ReadWriteExecute has been added

Review

10. Click OK on the New User Dialog Box

11. Close Certify
12. Re-Login Use New User Name and Password created

50 | P a g e
Create Process Folders
In Certify, creating and using folders is a way to organize project components. Users can
create as many folders and sub-folders as necessary to contain the processes for their
projects. The folder names you use should be descriptive of the processes contained within
them. As a best practice, use a similar naming convention to the one used for
naming processes discussed previously.
To create a new folder, right-click the folder you wish to be the parent folder. This can be
the project folder or an existing folder in the Navigation Tree. Select the New Folder option
and give the new folder a name. You can also copy and paste folders to create new
folders.
As a naming convention example, a folder called IWCA_PO_CreateEditAndVerify could be
created and all the processes created for the Web Sample Application could be placed in
that folder. Later, as more processes are created, it would be smart to create sub-folders
under IWCA_PO_CreateEditAndVerify to hold specific process types or window-related
processes so they are easier to locate and reuse.

Your Development Folder

Throughout this course, students will be using a folder to contain their processes. In the
following lessons and exercises, steps will be defined and added for all the required
processes. However, before beginning to define the processes, a Development folder will
need to be created with the name IWCA_PO_CreateEditAndVerify. This folder will be used
to contain the processes built by the student.
When an exercise references Your Development Folder, simply select the appropriate
folder from the tree.

In the following exercise the 02.04 Development folder is used as

Note: the container for your personalized Development folder. If this is not
correct, contact administrator for folder usage.

EXERCISE 3.3 — Create a Development Folder

In this exercise, students will create a folder structure to hold their processes.

Steps Action Description

1. Navigation Taskbar Processes
Select
2. Projects Folder
Navigation Tree Select
3. New Projects
Open

4. Development Folder
Open

51 | P a g e
Steps Action Description
5. New Folder

Right Mouse click and

select

6. Name Field, enter Name of folder (this should be the

same as your login credentials)

Type

7. OK
Select

8. Folder appears under the Development

Navigation Tree

9. Your name folder

Right Click

10. New Folder

Select

11. IWCA_PO_CreateEditAndVerify

Type in Name Field

12. Select Ok
13. You have the following sub-folders under the
Development folder
Result

52 | P a g e
EXERCISE 3.4 — Add Folder Security
In this exercise, students will add security to their Development folder; this will allow only
the student or an admin to edit their processes.

Steps Action Description

1. Right Mouse click Users specific Development Folder
2. Security

Select

3.
Right click on
permissions white
space

Select Add User/Group

4. Select User’s ID and ReadWriteExecute groups

Scroll down the list

5. Select OK
6. Uncheck Write permission within the ReadWriteExecute
user Group

Modify Permissions

7. Click OK

53 | P a g e
Create a Results Folder
All results are kept in the Certify Database until they are deleted. Folders can be created in
the Results area to organize execution results.
For example:
• In a Development folder for the Automator’s use only. This structure makes it simple
to delete results no longer needed.
• In a folder, specific to a testing cycle. This structure allows team members to quickly
determine the status of testing based on the results in a folder.
• In a structure that matches the Process Folder structure.

Figure 16 — View Result Folder

EXERCISE 3.5 — Create a Results Folder

In this exercise, students will create a Results Folder to store their execution results.

Steps Action Description

1. Navigation Taskbar Select
2. Expand Top Level Folder
Navigation Tree

3. New project Folder

Expand

54 | P a g e
 Steps Action Description
4. Development Folder
Right Click

5. New Folder

Select

6. Name the folder the same as in the Process Section

Type
(name or userid)
7. OK
Click

8.(Optional) Any Results that may exist in the top level folder, into
Move
user folder by clicking and Dragging
9.(Optional) Click On the Created by User Column to sort by UserID

If the Created by User column does not appear, use the Customize
Note: Columns option to arrange the Results column header (right click on the
column headers)

It’s okay if you do not have any result to move. In future lessons, you
Note:
will configure the execusion to send results directly to the results folder

55 | P a g e
Lesson Summary
The Certify Navigation and Best Practices lesson is complete

Key points to remember:

• Navigation in Certify is in a clockwise approach - starting in the Navigation Taskbar.
• Processes are used to document and validate the end-to-end execution of critical
business processes. Processes typically map your existing test cases to the business
functions associated with the AUT.
• A naming convention will help to promote reuse and reduce confusion. Ideally,
names are descriptive enough that their purpose and use is immediately clear and
external documentation is not needed.
• When planning a process, keep these guidelines in mind:
o All transactional or component processes should be created with the purpose
of being used in an end-to-end test.
o Good data management helps ensure that a process will run without manual
participation. Adding a process for adjusting inventory to meet the
expectations of the test.
o Audit (validation) points should be included in the test. All validation/audit
points should include a screenshot for audit purposes.
o Tests should be linear. Do not write logic to test logic.
• When folders are created (processes/data/results), remember to configure the
folders’ security settings.

56 | P a g e
Lesson 4 - Develop Functional and Integrated
Processes
Overview
This lesson will cover the difference between functional and integrated processes; how to
import captured .XML files into Certify; the parts of a process step; how to add steps to a
process; and how to use LiveTouch to add steps to processes.

Objectives
After completing this lesson, you will be able to:
• Import Process Capture 2.0 .XML files into Certify.
• Define Functional processes.
• Define Integrated processes.
• Define parts of a process step.
• Add steps to processes.
• Explain LiveTouch and add steps to processes using LiveTouch.

Create a Functional Process

When you define an automated process in Certify, the components of the process should
describe what is going to be validated and how. These processes typically map your
existing test cases to the business functions associated with the AUT. Processes consist
of a series of individual steps where a step performs an action against an object. When
defining processes, these objects and actions mimic the steps and sequence of the business
process being tested.

EXERCISE 4.1 — Import Process Capture 2.0 .XML File into Certify
This exercise will import the Process Capture 2.0 .XML into Certify to create a functional
process in Certify.

Steps Action Description

1. Navigation Taskbar -
Select
2. 02. New Project Folder
Navigation Tree - Select

3. 02.04 Development folder

Select & Expand

4. Find User Folder & Expand

57 | P a g e
Steps Action Description
5.
Select

6. Right Mouse click In the Process Detail area

7.

Select

8. Find XML file created

Find File
Select Appropriate File
Select OK

58 | P a g e
 Steps Action Description
9.
Capture XML Import
pop-up appears Enter
name
WSA_PO_Create

Uncheck all boxes

Ensure System is set to

System 1.0

Review Web it set to

Certify Web Sample
App 1.0
10. OK
Click

11.

Click - OK

12. WSA_PO_Create appears inn the Process Summary

Pane
Verify

Parts of a Process Step

Each step in a process contains information needed by Certify.
Application Version — Generally this is the name of the application under test.
For very large applications, such as the SAP GUI, the Application Version may be a
component such as “Sales and Distribution”. The Application Version drop-down
contains a list of available application versions that are associated with the current
project.
Window — Usually a screen, window, or page in the application. The Window drop-
down contains a list of learned and system windows available for the selected
application version.
Object — A field or control to be acted upon. The Object drop-down contains a list
of available objects for the selected window.

59 | P a g e
 Action — Input, verify, store, etc. The Action drop-down contains a list of valid
actions for the selected object.
Narrative — This is a phrase describing the step. The step narrative is read-only
and is automatically updated.
At the bottom of the steps area:
Parameters — value(s) to modify the selected action.
As an item in a column is selected, the columns to the right change to reflect the items
available. If a different Window is selected, the object column updates to reflect the objects
in that window.
As an Action is selected, the Parameters area changes to reflect the information needed for
that Action. If the Action is Input, the Parameters will include the value that will be input.

The Application Version, Window, and Object may have slightly

different name in your database. If user steps are signicantly
Note:
different, ask the Instructor, fellow student or Certify support
person to assist in troubleshooting the differences

Let’s explore Step 2 of the WSA_PO_Create process. It contains:

• Application Version — Common HTML 1.0
• Window — WebAccountManager
• Object — PO Number
• Action — Input
• Narrative — Input “1234” into the PO Number EditBox.
• Parameters — Value = 1234 and Follow-up Key = None or {TA}
A step can be manually created by selecting from each drop-down list.
Next, we will execute the step so that data will appear in the fields for the next series of
exercises. There are several ways to execute a step. Once you highlight the step(s), you
can:
• Click Action from the menu and select Execute Step
• Press the F6 function key
• Right-click on the step and select Execute Step.

60 | P a g e
EXERCISE 4.2 — Modify the WSA_PO_Create Process and Execute
Steps
This exercise will review the WSA_PO_Create process, modify steps, and execute the
process.

Steps Action Description

1. Double Click WSA_PO_Create
2. Process Details tab
Select

3. Enter Description
4. Creates a purchase order in the Worksoft Web
Type
Sample Application
5. Steps tab
Select

Figure 17 — Steps after importing the xml file

Steps Action Description

6. Row 7
Go to
7. To Find Row Advanced

Change Action from Drop-

down list

*Parameter options change based on

selection.

61 | P a g e
Steps Action Description
8. Parameters Tab
In Details pane find

9. In ‘Store Found Row Variable icon

Number in’ parameter –
Select
10. _Row variable name

Variable Pop-up box Select

*Variables are discussed in more detail in Lesson

5
11. OK
Click
12. Column Caption 1 (overrides Column Number)
Find Parameter

13. “Material”
Enter (Best Practice is Copy the column name from the
AUT and paste in Column Caption 1 parameter)
14. Cell Sub-Object TagName 1 field
Find Parameter
15. Select Dropdown button select INPUT
16. Match Attribute 1
Find Parameter
17. Select Dropdown button select Value
18. Match Criteria 1
Find Parameter
19. Select Dropdown button select Is Empty

Step 7 is configured to identify an Empty Row in the Material

Note:
Table. More advanced methods will be discussed in Lesson 5.

62 | P a g e
Steps Action Description
20. Select Step 9
21. Parameters Tab
Find

22. Find
22. Enter An Item is created (this is case sensitive)
23. Go to Step 10 (need to store the Document number)
24. Action Column - Store Cell

Go to Action Column
select from Dropdown
list

25. Select Variable Icon

26. Type in search field Doc
27. Doc Number
Choose Doc Number
variable from results

28. Click OK
29. Row Number
Find

30. Last

Select

31. Find
32. Enter DocNumber
33. Save Button
Click

63 | P a g e
Process Steps should look similar to the image below:

Figure 18 — WSA_PO_Create process steps

Steps Action Description

34. • Position mouse cursor anywhere in steps
• Press CTRL+A to select all the steps or click on
the first step and Shift+Click on the last step.
• Right-click In the highlighted steps and select
Execute Steps with Dialog. The Execution
Execute process dialog box appears.
steps above • In the Execution dialog box, right-click in the
Column Headers, and select Customize
Columns

35. “Interface Return Value” and “Interface Error

Message” from Hidden Columns and use the
button to move to Visible Columns Order box

Select

64 | P a g e
 Steps Action Description
36. Re-order columns if necessary
Select

37.
button and step through each step of the
Click process.
For each step will receive a or
38. All steps – Check the process editor status bar for the
Execute
number of steps and status

If one step fails, the Overall status will be “Failed”. Correct any
Note:
failures before moving on to the next section.

Creating Child Processes from Selected Process Steps

Within the Process and Data Editor, you have the ability to create a child process from
selected existing process steps in the Steps tab. When you create the new child process,
the selected steps will be deleted from the process.
To create a child process from selected process steps:
1. In the Navigation pane, click Processes. [The Processes window appears].
2. In the Processes Summary pane, double-click on the process you want to edit.
[The Process and Data Editor opens].
3. Click the Steps tab. [The Steps tab appears].
4. Using the <Shift> key, select the steps that will comprise your new child process.
5. Right-click on these steps and select Create Process from Steps.
6. A message appears stating that the selected process steps will be created as a new
child process and will be deleted from the process.
7. Click Yes to continue.
8. The new process is highlighted in the Steps tab. You will need to name your new
process.

9. In the Parameters tab, click the New Process button next to the Process field.
10. In the Process field, type in a name for your new process.
11. If needed, add new values to parameters.
12. Click Save to save the new child process.

65 | P a g e
EXERCISE 4.3 — Create the WSA_PO_Create_C_Materials Process
This exercise will show how to create a child process to enter materials in the Worksoft Web
Sample Application.

Steps Action Description

1. Select Step 7 in the WSA_PO_Create
2. Right-Click Step 7
3.

Select-
Create Process from Steps

4.

Pop-up box – Select OK

5.

Child Process Created

(Untitled)

6. Click - Untitled

7.
Pop-up Save Process box
Select Yes to Save

8. Go To

66 | P a g e
Steps Action Description
9. Enter Process Name
WSA_PO_Create_C_Mat
erials in the box

10. Enter “This child process

adds materials to a
purchase order” in the
Description
11. Save
Select

12. Steps tab

Select
13. Select Step 1
14.

Right-click

15. Select

When inserting a step above or below, the application version,

window, and object of the original step are copied to the newly
TIP:
inserted step.

Steps Action Description

16. Select Step 2
17. Go to Action Column
18.

Select Drop-Down Menu

19. Select

67 | P a g e
Steps Action Description
20. Find Parameter tab
21. Go to Row Number field
22. 2 Variable Icon
2 Select
.
23. _Row

Select

24. OK
Click
25. Go to Column Caption (overrides Column Number) field
26. Enter “Material” (this is case and space sensitive field)
27. Value
Go to

28. Enter “P-100”

Do not use the scroll wheel on your mouse as the selections

Caution:
could get changed and cause issues when executing any test.

Steps Action Description

29. Select Step 2
30.

Right-click & Select

“Insert Step Below”

31. Find Parameter box

32. Go to Row Number field
33. Variable icon
Select

34.

Select _Row

68 | P a g e
Steps Action Description
35. OK
Click
36. Go to Column Caption (overrides Column Number) field
37. Enter “Quantity” (this is case and space sensitive field)
38. Value
Go to

39. Enter “1”

40. Select Step 3
41.

Right-click

42. Select
43. Find Parameter box
44. Go to Row Number field
45. Variable icon
Select
46.

Select _Row

47. OK
Click
48. Go to Column Caption (overrides Column Number) field
49. Enter “Price” (this is case and space sensitive field)
50. Value
Go to

51. Enter “2482”

52. Save on the Child process
Select

Process Steps should look similar to the image below:

69 | P a g e
 Figure 18 – WSA_PO_Create_C_Materials steps

Steps Action Description

53. WSA_PO_Create parent process in the menu

Select

54. Step 7 is now illuminated in same color as step 6

View

55. Open Open the Worksoft Basic Sample Application

56. Execute the process steps with the Running Man

Execute
Button

Figure 19 – Execution Configuration Screen

70 | P a g e
Steps Action Description
57. Review the pop-up Execution Configuration box –
Pop-up box
Figure 18
58. Find Run Settings area
59. Check Box
Select

60. Find Logging Settings

61. Select Output Location
62. Results = Output Location
Navigate to

63. Select Personal Results Folder

64. OK
Click
65. Start Button
Click

66. Running Man Button

Next screen Select

67. Results Viewer will appear. Close window when done

Review

68. Correct Failed Process Steps

69. Repeat the execution Until no failed steps
70. Close WSA_PO_Create process and Result Viewer

Process Steps should look similar to the image below:

Figure 20 – WSA_PO_Create with the Child Process steps

71 | P a g e
Certify LiveTouch Overview
The Certify LiveTouch feature allows selection of multiple objects in the AUT. New steps can
be created in a new process or steps can be inserted into existing processes by clicking on
one or more object(s) in the AUT. LiveTouch inserts corresponding process steps for each
of the selected objects. LiveTouch also pre-populates the appropriate step parameters with
values entered or produced by the AUT.

As shown in Figure 19, from the Process and Data Editor, steps can be added using
LiveTouch by right-clicking a step and selecting Insert Step Below Using LiveTouch. Certify
will minimize and the AUT will appear, along with the Certify LiveTouch dialog box.

Figure 21 — Certify LiveTouch

LiveTouch allows the user to learn multiple windows in one session. First, access a window
and learn the objects on that window. Clicking the Pause button allows the user to move to
another window in the application. Lastly, click the Start button and learn the objects in the
new window, all in the same session.

• When LiveTouch is open and Ready, any click made with the mouse is captured. If
there is a need to change windows or start a new application, press Pause before
using your mouse.
• Do not try to click any objects until the LiveTouch window displays Ready.

72 | P a g e
 • After clicking an object, wait for the message “Ready (x Selected)” where “x” equals
the number of objects clicked, before pressing “Save & Close”.
• Clicking an object using LiveTouch is a toggle function, e.g. it the object was
previously selected, and it is selected again, it will be deselected.

Key Functions of Certify LiveTouch

When Certify LiveTouch adds steps to a process, it performs many functions almost
instantaneously. However, there are several other key functions of Certify LiveTouch:
• Adds an object(s) and step(s) to your Certify process.
• Attempts to pull the object and corresponding window from the Certify database. If
the object doesn’t exist in the database, Certify LiveTouch creates the object and
adds it to the database and corresponding window.
• If the window doesn’t exist, Certify LiveTouch creates the window and corresponding
object.

Preparing to Use Certify LiveTouch

To take advantage of the LiveTouch feature, do the following:
• Create a new process or open an existing process for modification.
• Open the AUT and navigate to the screen that will be used for the Certify process.

73 | P a g e
Certify LiveTouch Menu Options
Menu Option Description

Displays the following options:

• Application
• Program
Fields • Transaction
• Screen Title
• Class
View • Text
• Name
• Physical Location

This selection is continued throughout your session.

Fields (Show when As you hover over objects in the application, the field
hovering mouse) information is displayed.

Learn Objects as Needed Learn new objects while adding steps to your process.

Learn
Save Objects to
Save the newly learned objects to a specific application version.
Application Version

Select a target folder for the variables. Note: This feature is

Target Folders
only available to users who purchased Certify Data.
Settings
Use Variables for New Create new variables for the application’s values. Note: This
Steps feature is only available to users who purchased Certify Data.

List of interfaces
Enable supported by Certify Only interfaces licensed can be enabled.
LiveTouch

Table 3 — Certify LiveTouch Menu Options

74 | P a g e
EXERCISE 4.4 — Create the WSA_PO_Edit_QuantityAndPrice Process
This exercise will show how to use Certify LiveTouch and how to create a process to edit
purchase orders in the Worksoft Web Sample Application.

Methods of learning the Websoft Basic Sample Application can differ,

Note:
so objects may vary from system to system.

Steps Action Description

1. Go to Certify
2. Processes > Personal development folder in
Find
navigation tree
3. Verify IWCA_PO_CreateEditAndVerify has been selected
4. Right Click In the Processes area in the Summary Pane
5. New Process

Select

6.
Enter
“WSA_PO_Edit_QuantityA
ndPrice” in the name field

7. Enter “Selects a purchase

order
and edits a material’s quantity
and price”

8. Save
Select

9. Navigate to Steps

10. Go to Summary pane

11. Right-click Summary pane
12. Insert Step(s) Below Using LiveTouch

Select

75 | P a g e
Steps Action Description
13.

Click – OK
(to enable Certify Live Touch)

Certify will minimize and the HTML window, along with the Certify LiveTouch dialog box will
appear. Before using LiveTouch to choose fields on the page, wait until LiveTouch loads
and “Ready” appears at the bottom of the LiveTouch dialog box

With the Insert Step(s) Below Using LiveTouch option, you can select
Note:
multiple objects from the window before saving

Figure 22A – Certify LiveTouch Screen

Steps Action Description

14. Pause Button
Click

15. Go To View on menu bar

16. Check both Fields & Fields (show when hovering
Select

mouse)
17. Go To Learn on Menu bar
18.
Check box labeled “Learn Objects as needed”
Save Objects to Application Version > Certify Web
Sample App 1.0
Select

76 | P a g e
Steps Action Description
19. Settings on Menu bar – Start in Paused Mode

Go to

20. Go to Enable on Menu bar

21. Check Web for this exercise
Uncheck all other options

Check or Uncheck

22. Start
Click

Figure 22B – Certify LiveTouch Screen with Fields setting turned on

Each application interface that is associated with the current project will
Note: display on this list. As a best practice, disable all interfaces that will not
be used during the current LiveTouch session

77 | P a g e
Steps Action Description
23. Action Table that Displays the purchase Orders

LiveTouch

24. Click Once

25. Status “Ready (1 Selected)
Review

26. Save & Close Button

Click

27. Application Version: Certify Web Sample App 1.0

Select

Note: If this pop-up window does not display, proceed to

step 29 of the exercise.
28. OK
Click

78 | P a g e
 Figure 23 – Step generated using LiveTouch

Steps Action Description

29. Modify Step 1
30. Go to Action Column
31. Find Row (Advanced)

Select

32. Parameters

Find

33. Store Found Row Number In

Go to

34. Variable Icon

Click

79 | P a g e
Steps Action Description
35. _Row
Select (Dbl Click)

36. Go to Matching Row Instance

37. Last
Select

38. Go to Column Caption 1 (overrides Column Number)

39. “DocNumber” (this is case and space sensitive field)
Enter

40. Go to Match Attribute 1

41. innerText
Select or Verify

42. Match Value 1

Go to

43. Select Variable Icon

44. Type in search field Doc
45. Doc Number
Choose Doc
Number variable
from results

46. Click OK
47. Match Value 1 field looks like this:
Note

48. Select Step 1

49. Right-Click - Insert
Step Below

50. Modify Step 2

51. Find Action column
52. Select Cell

Select

80 | P a g e
 Steps Action Description
53. Find Parameters
54. Go to Row Number
55. Variable Icon
Click
56. _Row
Select (Dbl Click)

57. Column Caption (overrides Column Number)

Go to

58. “Action”
Enter

59. Go to Horizontal % field

60. 10
Enter

61. Go to Vertical % Field

62. 50
Enter

63. Save
Click

The combination of the Horizontal and the Vertical values tells

Note:
Certify the intersection point to click within the Action column

Stop here and test steps – Troubleshoot as needed. Process should display the status
message needed for validation.

Steps Action Description

64. Click WSA_PO_Edit_QuantityAndPrice process
65. Select Steps 1 – 2
66. Right-click Once

81 | P a g e
Steps Action Description
67. Execute Steps with Dialog

Select

68. Click Step button and step through Process

Your step will FAIL unless you enter the Document Number displayed
Note:
in the last line of the Purchase Order table.

Figure 24 – Execution Menu

Steps Action Description

69. View Execution Menu (Figure 22)
70. Plus (or Minus) sign button (lower right)

Find

71. Click To expand the display

72. Step tab

Click

82 | P a g e
Steps Action Description
73. Right-Click Step 1
74. Set Execution Pointer (resets execution point)

Select

75. In the Step tab, for the Doc Number variable, type the
Document Number value displayed in the last row of the
Review Action table in the Worksoft Web Sample Application. This
function allows you to enter data during execution. Step 1
should pass after corrections
76. Input the Document Number in the Value column

Input

77. Click Step button and step through Process

Note: Your steps will now PASS as highlighted below

Figure 25 – Execute steps with Dialog results

Break Break for discussion

83 | P a g e
Steps Action Description
78. Go To Web Sample Application (AUT)
79. Update Quantity
and Price Quantity=2 and Price=2982
80. Save changes in the Web Sample Application (AUT)
Press

81. The Item is edited

Find

82. Go to Certify
83. Select & Right-Click Step 2
84. Insert Step(s) Below Using LiveTouch

Select

85. Ensure LiveTouch is set up properly

86. Click Start to initiate LiveTouch
87. Using LiveTouch, select the Material Table Object

Select

88. Using LiveTouch, select the Status Message

Select “The Item is edited”

89. LiveTouch Status bar shows “Ready (2 Selected)”

Verify

90. Save & Close Button (two steps are created)

Click

91. Step 3

Click

84 | P a g e
Steps Action Description
92. Click Action column drop-down list
93. Find Row (Advanced)

Select
94. Find Parameters for Find Row (Advanced)
95. Store found Row number in
Go to
96. Variable Icon
Click
97. _Row

Select (Dbl Click)

98. Go to Column Caption 1 (overrides Column Number)
99. Material (this will identify the Row number with Material
column)
Enter

100. Go to Cell Sub-Object TagName 1

101. INPUT
Select

102. Go to Match Attribute 1

103. Value
Select

104. Go to Match Value 1

105. P-100
Enter

106. Go to Match Criteria 1

107. Is Equal To
Select or Verify

108. Select On True / On False tab

109. Find On False
110. Go to Log Status As: drop-down menu

85 | P a g e
Steps Action Description
111.
Select - Skipped

112. Go to Action drop-down

113.

Select - Jump

114. In the following steps –

Note
Create a Label Step to give users a Target
115. Select Step 4
116.
Right-click - New

117. Go To Step 5
118. Change Action Column
119.

Select - Label

120. Go to Parameters
121. Find Label Name
122.
Enter - Cancel

123. Go to Step 3
124. Find On True / On False
125. Go to On False
126. Find Target Step
127.

Choose Cancel

128. Save
Click

86 | P a g e
 Break Break for discussion

Steps Action Description

129. Select Step 3
130.
Right Click & Select
-
Insert Step Below

131. Select Step 4

132. Go to Action Column
133. Select from drop-
down –
Input into Cell

134. Find Parameters

135. Go to Row Number
136. Variable Icon
Click
137. _Row
Select (Dbl Click)

138. Column Caption (overrides Column Number)

Find
139. Enter
“Quantity”
140. Find Value
141.
Enter –
‘2’
142. Right-click Step 4
143.
Select-
Insert Step Below

144. Select & Modify Step 5

145. Find Parameters
146. Go to Row Number
147.
Click Variable Icon

87 | P a g e
Steps Action Description
148. Select (Dbl Click)
_Row

149. Select OK
150. Find Column Caption (overrides Column Number)
151. Enter –
“Price”
152. Find Value
153.
Enter –
“2982”
154. Select Step 5
155. Right Click &
Select –
Insert Step
Below Using
LiveTouch

156. Save and Cancel Buttons

Use LiveTouch to
Select
157. Verify LiveTouch Status “Ready 2 Selected”
158. Save & Close – Two steps are created
Click

159. Step 7 (the Cancel button) must execute after the Label
Note:
step
160.

Cut - Step 7

161. Below Step 9 or Drag & Drop.

Paste *Note: Your instructor will demonstrate how to drag and
drop steps correctly
162. Select Step 7

88 | P a g e
Steps Action Description
163. Change Action Column
164.

Select - Verify

165. Find Value parameter

166.
Enter –
“The Item is
edited”

167. Select Step 7

168.
Right Click &
Select -
Insert Step
Below

169. System 1.0 | System | Operating System | Capture Screen Image

Parameter: Active Window

Change the Step

sequence

170. Select Step 8

171.
Right Click &
Select -
Insert Step
Below

172. System 1.0 | System | Execution | Exit Process

Modify Step 9

89 | P a g e
Steps Action Description
173.

Right-Click -
Select New

174. Modify Step 12

175. From Operating System. This will give you the default
Action of Capture Screen, and this last step will take a
screen capture

Change Object

176. Change Action Select Capture Screen Image

177. Select The type of screen capture desired
178. Select - Save

179. Select - Run –

process will fail
until connect to
WSA_PO_Create
process

90 | P a g e
Process Steps should look similar to the image below:

Figure 26 – WSA_PO_Edit_QuantityAndPrice steps

EXERCISE 4.5 — Create the UTL_LaunchWSA Process

This exercise will show how to close an active internet browser using an existing process,
open a new Chrome browser instance and launch the Web Sample application, maximize
the window and verify that it has launched the correct website.

Steps Action Description

1. Go To Navigation Tree
2. Select Processes
3. Select IWCA_PO_CreateEditAndVerify folder
4. Right-Click Summary Pane
5.

Select - New Process

6. Name – “UTL_LaunchWSA”
Description – “This utility launches the browser and
loads the Worksoft Web Sample Application”

Enter

7. Select - Save

91 | P a g e
Steps Action Description
8. Steps Tab
Navigate to

9. On the top right of the screen

Locate Easy Search

10. “close” and click the search icon

Enter

11. Easy search results returned all definitions containing

the word “close”

Note

12.

Drag and drop

UTL_CloseChrome to
the Process Steps Area

*this process closes any active Chrome browser session

13. Step 1 contains the UTL_CloseChrome process
Note
14. Select Step 1

92 | P a g e
Steps Action Description
15.

Select – Insert Step

Below

16. Modify Step 2

17. Change Window column value
18.

Drop-Down menu
Select - Browser

19. Find URL Parameter

20. Worksoft Web Sample Application URL

Paste

*Change Browser Type if using different browser

21. It is a Worksoft Best Practice to copy an
TIP application’s URL and paste into the appropriate step
parameter
22. Right-Click Step 2
23. Insert Step Below
Select

24. Modify Step 3

25. Application Version column
Change

93 | P a g e
Steps Action Description
26.

Drop-down Select-
Certify Web Sample
App 1.0

27. Change Window Column

28.
Drop-Down
Select -
WebAccountManager

29. Change Object Column

30. Drop-Down
Select -
WebAccountManager

31. Action Column

Change
32. Set Window State

Drop-Down and Select

33. Parameters select Maximize (Window State)

Go to
34. Right-click Step 3
35.
Select –
Insert Step Below
Using LiveTouch

94 | P a g e
 Steps Action Description
36. Worksoft Logo
Select

37. Verify LiveTouch Status bar displays “Ready (1 selected)”

38. Click Save & Close – Step 4 is created
39. Modify Step 4
40. Change Action Column
41. Drop-Down Visible
42. Find Visible Parameter
43.
Select –
“Is” from Drop-down
menu

44. Click Save

Process Steps should look similar to the image below:

Figure 27 – UTL_LaunchWSA steps

EXERCISE 4.6 — Create the UTL_CloseWSA Process

This exercise will show how to create a process to close the Worksoft Web Sample
Application.

Steps Action Description

1. Go To Navigation Tree
2. Select Processes
3. Select IWCA_PO_CreateEditAndVerify folder
4. Right-Click Summary Pane

95 | P a g e
Steps Action Description
5. New Process

Select

6. Name - UTL_CloseWSA
Description - This utility closes the browser window
with the Worksoft Web Sample Application

Enter

7. Save
Select

8. Select the Steps Tab Right click on Summary Pane

9. New

Select

10. Modify Step 1

11. Find Window Column
12. Select from Drop-down
menu Browser

13. Find Action Column

14. Close Browser
Select from Drop-down
menu

96 | P a g e
 Steps Action Description
15. Save
Click

16. Exit Process Editor

Process Steps should look similar to the image below:

VariablesFigure 28 – UTL_CloseWSA steps

Creating an Integrated Process

The previous lessons have shown how to create individual processes. These processes will
now be combined into an Integrated Process. An Integrated or Critical Business
Process contains System steps which execute sub-processes (functional processes).

Integrated Process Sub-Processes

UTL_LaunchWSA
IWCA_PO_CreateEditAndVerify WSA_PO_Create
WSA_PO_Edit_QuantityAndPrice
UTL_CloseWSA

EXERCISE 4.7 — Create & Execute IWCA_PO_CreateEditAndVerify

Process
In this exercise, students will create and execute an integrated process.

Steps Action Description

1. Go To Navigation Tree
2. Select Processes
3. Select IWCA_PO_CreateEditAndVerify folder
4. Right-Click Summary Pane
5. Select New Process
6.
Enter
Name -
IWCA_PO_CreateEditAndVerify;
Description - This is the
integrated process

97 | P a g e
Steps Action Description
7. Select - Save

8. Click - Steps tab

9. Will start this process by setting the execution to

Note:
stop if it encounters any failures
10. Right-Click Summary Pane
11. Select New
12. Go to Application Version Column
13.

Verify - Set to System 1.0

14. Go to Window Column

15.

Verify - Set to System

16. Go to Object Column

17.

Drop-down select -
Execution Setting

18. Click Action Drop-Down

19.

Select - Stop on Failure

20. Go to Parameters Tab

98 | P a g e
Steps Action Description
21.
Check - Stop on Failure check
box

22. Right Click Step 1

23. Select Insert Step below
24. Go to Object column
25.

Drop-down select - Execution

26. Go to Action Column

27.

Drop-Down Select –
Execute Process

28. Go to Parameters Tab

29. Select Existing Process icon
Click

30. Development Folder >

Navigate to
IWCA_PO_CreateEditAndVerify folder
31.

Select - UTL_LaunchWSA

32. OK
Click

33. Save
Click

99 | P a g e
Steps Action Description
34. Right-Click Step 2
35. Select Insert Step Below
36. Go to Parameters Tab
37. Find Process Field
38. Select Existing Process icon
Click

39. Select WSA_PO_Create

40. Click - OK
41. Right-Click Step 3
42. Select Insert Step Below
43. Go to Parameters Tab
44. Find Process Field
45. Click Select Existing Process icon
46. Development Folder >
Navigate to
IWCA_PO_CreateEditAndVerify folder
47. Select WSA_PO_Edit_QuantityAndPrice file
48. Click - OK
49. Right-click Step 4
50. Select Insert Step Below
51. Go to Parameters Tab
52. Find Process Field
53. Click Select Existing Process icon
54. Development Folder >
Navigate to
IWCA_PO_CreateEditAndVerify folder
55. Select UTL_CloseWSA
56. Click - OK
57.
Click
(Process should contain 5 steps)
58. Running Man Icon
Find

100 | P a g e
Steps Action Description
59.

Pop-up Box Appears –

Execution Configuration

60.
Select
Output Locations selection icon
in the Logging Settings

61. Navigate Desired Results Folder

62. Click - Ok
63.

Click Start – execution dialog

box appears

64. Click Run

65. The process executes, and the Result Viewer
appears upon completion.
Troubleshoot and resolve any failures.
66. Close the integrated process –
Close IWCA_PO_CreateEditAndVerify and the Result
Viewer

101 | P a g e
Process Steps should look similar to the image below:

Figure 29 – IWCA_PO_CreateEditAndVerify steps

Lesson Summary
This completes the Develop Functional and Integrated Processes lesson.
Key points to remember:
• When defining a process in Certify, the components of the process should describe
how and what items are being validated; these processes typically map existing test
cases to the business functions associated with the AUT.
• There are a variety of ways to create processes in Certify; importing a Process
Capture 2.0 .XML file is one of those methods.
• Each Certify step contains the following information: Application Version, Window,
Object, Action, Narrative, and Step Parameters.
• LiveTouch allows selection of multiple objects in the AUT. Steps can be created in a
new process or inserted into existing processes by clicking on one or more object(s)
in the AUT.
• LiveTouch inserts corresponding process steps for each selected object.
• LiveTouch pre-populates the appropriate step parameters with values entered or
produced by the AUT.
• An integrated process is a process with system steps that executes a sequence of
sub-processes (functional processes) that validates the company’s critical business
process.
Creating utilities to launch and close an application ensures the AUT is opened and closed
during the execution of your integrated process.

102 | P a g e
Lesson 5 - Use Data to Execute Processes
Overview
This lesson will show how to manage data within Certify, including how to create and use:
variables, layouts, recordsets and recordset filters. The importing and exporting of data
within Certify will also be covered.

Objectives
After completing this lesson, the student will be able to:
• Explain how variables work and how they are used.
• Describe what layouts are and how they are used in Certify.
• Describe what recordsets are and how they work with layouts.
• Create a process from steps using the Create Process from Steps option.
• Create a layout, recordset, and variables using the Add to Layout feature.
• Execute processes using data.
• Determine where a Layout/Recordset should be placed for optimum execution.
• Import data.
• Export data.
• Create a recordset filter.

Variables Overview
A variable is a symbol or name that represents a value. In Certify, variables are an
important component of Business Process Testing because they provide a means of
representing the data that you want to use in your processes. Variables contain a specific
type of value that can be inserted into a field, acted on, or stored for future comparison
against another value.
The most common use of variables is for data-driven testing, where process execution loops
through a series of data values. For example, if the steps in a process are the same, but the
data is expected to vary from one execution to another, then the process needs to be
defined only once using variables in place of static values. Certify processes use variables to
create several executions in one single test.
Variables can also be used to store or verify system data, such as the System Date or
Machine Name, or when specific data for a user is required, such as a user ID or password
to log into an external system or application.

Preparing to Use Variables

When preparing to use variables, the first thing to be done is to go through the existing
processes and identify all the places where variables can be used in place of static data. As

103 | P a g e
a guideline, create a table or spreadsheet showing the processes and all the
variables to be used for each process. This method will help later in creating the
recordsets to be used with processes.
For example, Table 4 below shows the WSA_PO_Create process and all the variables
required for that process.

Process Variables Needed Data Type

PO Number Text
Name Text
Ship to Text
WSA_PO_Create Bill to Text
Material Text
Quantity_Numeric Number
Price_Numeric Number
Table 4 — Variables Needed for the WSA_PO_Create Process

Defining Variables in Certify

In Certify, there are several types of variables:
Project Variables — variables that are specific to the project being worked in and the
most commonly used processes. Project variables can be created and managed in the
Variables window or while creating processes in the Process Editor. Project variables can be
used on both the Data window to define the layouts of the recordset(s) and in the Process
Editor to hold the values of objects within the process steps.
System Variables — pre-defined and used as read-only variables for data values during
test execution. The system variables which can be used in process steps are:
• Date
• Process Name
• Recordset Name
• Recordset Row Number
• Last Step Status
• User Name
• Layout Name
• Machine Name
User Variables — user-defined variables that can be used during process execution, such
as other system user IDs and passwords, test dates, test numbers, tester ID number, etc.
User variables are created and managed from the Extensions window by a Certify
Administrator or manager, and they are shared across all projects. The values for user
variables are specified by each user by selecting Set User Variables from the Tools menu.
Each type of variable contains text, number, or date values.

104 | P a g e
 • Text — consists of alphanumeric and special characters. Text variables have a
system maximum length of 65,535 characters (64K).
• Number — consists of integers, floating point values, and exponential notations.
Specific data type formats can be applied to a number variable to display the value in
a certain format (i.e. 12345.00 or $12,435.00). If no data type format is specified,
the default system number format is used.
• Date — consists of any combination of month, day, and year in any Certify-
supported format. Date variables default to today’s date. A specific data type format
can be applied to a date variable to display the date in a certain format (i.e.,
MM/DD/YYYY). If no data type format is specified, the default system date format is
used.
Variables are shared among all processes in Certify. As a best practice, before creating
a new variable, the list of existing variables should be reviewed to see if there is
one that satisfies your need. If a new variable is needed, the naming convention should
be followed as previously discussed. Variables should be named the same as the field
it represents.
An initial value can be set for the variable and/or can be selected to mask the value of the
variable. If an execution step contains a variable with an initial value, the object associated
with the step is populated with the initial value. When the Mask checkbox is selected, the
value is replaced with asterisks (e.g., ****) to hide the real value from view in the Certify
Result Viewer. This feature is useful when the variable value is a user ID or password.

Use of Variables in Certify

Listed below are some additional scenarios where variables can be useful in processes.
Field value is unknown before execution. The value of a variable is changed when an
application returns a value that is randomly generated or generated on the fly. For example,
creating an order generates an order number. The order number can be stored in a variable
for verification or other uses.
A value must be derived from a combination of other variable values and/or
static values. The variable value is based on calculations or concatenations of other
variables or static values. These operations are performed by process steps and the
resulting value is stored in a variable. For example, an application requires the month and
year to be added to a filename to locate the file within a list. The month and year can be
concatenated from two variables and added to another variable containing the file name.
The variable can then be used to locate a file within the list.
Process execution order varies. The names of processes can be stored in a variable so
that each iteration through the recordset can call a different process. For example, there is
a set of processes for an application which add an account, add a transaction, and verify a
portfolio. Instead of creating three separate Execute Process steps, a recordset can be
associated with your master process which allows for a single Execute Process step that
calls an Account Process variable. Since the variable is associated with a recordset
containing the names of all the processes you want to execute, each of the processes are
executed in the order they appear in the recordset.

105 | P a g e
Working with system information. Pre-defined system variables can be used in process
steps to capture information such as the computer name, user name, and process name.
For example, capturing the system date for comparison against another date variable or
getting the status of the last step executed to verify the step passed.
Logging into other systems or applications during execution. User-defined variables
can be used in process steps to log into other systems or applications referenced in the
process execution. For example, a legacy system containing data that needs to be
compared to data from the application being tested. A user variable in the process can be
used to input the user ID and password for the legacy system or application.

Creating and Modifying Variables

Variables are created and modified from the Variables window. The Variables window shows
all the variables that have been created in the project.
Variables can also be created from the Process Editor. While creating a process step that
requires an input, verify, or store value, after clicking the Select Variable button, variables
can then be added or modified in the Select Variable window.

Adding Variables to Existing Process Steps

Variables are applied to process steps in the Process Editor. When creating a new step or
selecting an existing step, use the Parameters option for the selected step to select the
variable to be used. If using static data, replace the static data with the variable which has
been created.
In the prior exercises, the WSA_PO_Create process was created with static data. The
values for the PO Number, Name, Ship to, Bill to etc. fields were hard coded in the process.
This was done to learn how to define processes without the added complication of including
variable data. However, to automate testing, the use of variables within your processes will
be necessary to perform data-driven testing.
For the next exercises, the application requires that the PO Number be unique for each PO
created. We will concatenate a static value and the System Variable Date to create a unique
PO number.

EXERCISE 5.1 — Add Variables to Process Steps

In this exercise, variables will be added to the steps in the WSA_PO_Create process to
generate a unique PO number using the concatenate action in a Certify step.

Steps Action Description

1. Go to Navigation Taskbar
2. Click Processes
3. Go to Navigation tree
4. Development Folder >
Click
IWCA_PO_CreateEditAndVerify Folder
5. Open WSA_PO_Create Process

106 | P a g e
Steps Action Description
6. Click - Steps tab
7. Locate and Select PO Number/Input step (Step 2)
8. Insert Step Above

Right-click

9. Application Version column

Find

10. Drop-down select System 1.0

11. Go to Window Column
12. System

Drop-down select

13. Go to Object Column

14.

Drop-down select -
Text

15. Go to Action Column

107 | P a g e
Steps Action Description
16. Concatenate

Drop-down select

The Parameters tab may have multiple parameters for an action.

The direction of the parameter can be input or Output. An input
parameter provides values to an action (e.g. text for a field). An
Note:
output parameter passes a value from an action (e.g. variable that
can be used in subsequent steps). All output parameters are
required to have a variable selected to save the process.

Steps Action Description

17. Go to Parameters Tab
18. Variable Field
Find

19. Selection Variable Icon

Click

You can scroll down the list to select a variable. You can also type
Note part of a name in the quick entry box at the top of the list. The
narrows the list of variables to match the characters you have typed.

Steps Action Description

20. Find Variables pane
21.
Type “PO” and select –
PO Number

22. OK
Click
23. The Process Editor reappears, and the PO Number
Note: variable is added to the parameters for the
WSA_PO_Create process

108 | P a g e
Steps Action Description
24. Save
Click

25. The Narrative for Step 2 has been updated with the
Note:
PO Number variable
26. Go to Value1 field
27. Enter Any 4-digit number value
28. Go to Value2 field
29. Select Variable Icon
Click

30. Go to Navigation tree

31. Click System Variables
32. Date

Select

33. OK
Click

34. Click Format Drop-down

35. Unique Number-6 Digit

Select

36. Now that you have Step 2 configured, copy the PO

Note: Number variable from Step 2 parameter and
paste it in Step 3’s value field
37. Select Step 2 Go to Parameters

109 | P a g e
 Steps Action Description
38. (V) PO Number variable and select copy

Right click

39. Select Step 3 Go to Parameters

40. On Value parameter and select paste

Right click

41. Save
Click

Execute Steps with Dialog

For these steps, we will use the Execute Steps with Dialog option. With this option, the
Execution dialog box appears and allows us to step through the execution displaying
variables, return status, and errors.

EXERCISE 5.2 —Execute Steps with Dialog to Show Variables

In this exercise, steps will be executed to set the PO variable in the WSA_PO_Create
process.

Steps Action Description

1. Open Worksoft Web Sample Application (AUT)
2. In Certify Make sure the WSA_PO_Create process is open
3. Select Steps 2, 3 and 4
4. Go to Action drop-down on menu bar

110 | P a g e
 Steps Action Description
5. Execute Step with Dialog

Select

6. Step

Click

7. Note Log Status executed as Passed

8. Go to Execution dialog box
9. Step -The second step executes. In the Execution
dialog box, notice that the Log Status field displays
a check mark and the word ‘passed’. The Interface
Click
Return Value field displays the value that will be
stored in the variable PO Number. The narrative for
Step 3 also shows the value
10. Step to execute the next step - The next step
Click executes, and the Log Status and Interface Value
Return fields are populated
11. Click Stop to stop the execution
12. The status bar displays the number of steps
Note
executed and the results. Troubleshoot any failure.

Layout Overview
A layout is a collection of variables that define the data used by a process.
A layout can be visualized as the header row of a table. The layout for the table shown
below would include the variables PO Number, Name, Ship to, Bill to, Material,
Quantity_Numeric, and Price_Numeric.

Recordset Overview
A recordset contains data values for the variables defined in a layout. For example, a
recordset for creating a new Purchase Order might contain multiple data values for PO
Number, Name, Ship to, Bill to and so forth.
A recordset can be visualized as the detail rows of a table. The recordset for the table
shown below would include two rows of data – one for Purchase Order 1234 and one for
1574.

111 | P a g e
 PO No. Name Ship to Bill to Material Qnty Price
1234 Mary Wilson 100 Fifth Street 1444 North Fifth Ave P-100 1 24.82
1574 John Smith 123 Sing Lane 1455 North Main Phone 7 4.50

When a recordset is used with a process, the process will execute one time for each row of
data in the recordset. After completing a test with the first row of data, the process will
execute again with the second row of data.
A layout can have one or more recordsets associated with it. Separate recordsets can be
created for each test scenario needed. For example, a layout that contains Purchase Order
information might have 3 recordsets: one that creates the initial set of data, another that
adds data for regression testing, and one that adds data specifically to test new features.
The recordset for the table shown below would include three rows of data – and the
process would execute three times.

14524 Gerardo Jones 11 Fifth Street Keyboard 70 45

96586 Dustin Brown 754 N Central Road Mouse 52 30
854796 Mark Ebert 143 George Bush Tpk Speakers ^ 12

The caret (^) character is used to designate the skip character for any value in a recordset.
Any step that refers to a recordset whose value contains this character is skipped. For
example, if certain fields or objects are enabled or disabled based on data values, the skip
character can be used in a recordset to designate when disabled fields should be skipped.

Recordset Modes
Recordsets can be used in different modes depending on how the data should be handled
during execution. By default, a recordset is used in Read Only mode so that at the end of
execution the data in the recordset is the same as when the execution started.

Mode When Executed How Executed

Reads recordsets at the Loops process once for each row until
Read Only
beginning of execution the end of the file.
Writes recordsets at the end of Appends to existing recordset and loops
Append
execution process until Abort or Exit.
Creates new recordset for each
Writes recordsets at the end of
Clear and Append execution session and loops process
execution.
until Exit,
Reads recordsets at the Updates the recordset at the end of the
Read and Update
beginning of execution. process.

112 | P a g e
Define Layouts in Certify
Layouts can be created in the following ways:
When a layout is created manually, existing variables are inserted or added into the
layout. Manually creating a layout requires you to select variables in a project and add or
remove the variables in the layout. **Note: A Job Aid example is provided at the end of the
training guide.
When a layout is created from a process, all variables used by the chosen process are
added to the layout. If the process has sub-processes, their variables can be included or
excluded.
Note A Job Aid example is provided at the end of the training guide.

When a layout is created from steps (Add to Layout), steps are selected, and a
variable is created or selected for the parameters in the step. These variables are added to
the layout. A recordset is created with any data that you had in the step. This method will
be discussed in another lesson.
The first two types of Layouts are created in the Data window. All three types can be
managed in the Data window or indirectly through a process. When Data is selected from
the Navigation Taskbar, the existing layouts for the project within which you are working
will be displayed. From here, new layouts can be created, or existing layouts can be
modified. Layout creation and modification takes place in the New/Edit Layout dialog box.

Figure 30 - New/Edit Layout Dialog Box

113 | P a g e
From the New/Edit Layout dialog box, specify a unique name and description for the layout.
As a best practice, layouts should be named the same as the process to which
they are attached. If a layout is created for the WSA_PO_Create process, the layout
should also be named WSA_PO_Create.
After a name and description for the layout has been entered, variables can be added
manually in the Variables pane or an option to add the variables from processes or objects
can be selected from the Create list.
If one of the Process options is chosen, the Select Processes dialog box will open and after
choosing a process, all the variables in that process will be added to the layout.

Figure 31 - Select Processes Dialog Box

Create a Layout Using Add to Layout

The Certify Add to Layout feature allows for the conversion of static data into variable data.
If a process has steps which contain literal values or variables, with no associated layout, a
layout can be created for the process using Add to Layout. This is the simplest way to add
variables/layouts/recordset and data to a process in a few steps.
The exercises in this lesson will include directions on how to:
• Select steps of interest within the Steps tab.

114 | P a g e
 • Replace literal values in those steps with variables.
• Create a layout for the process.
• Create a recordset for the layout.
• Collect variables from selected steps and add those variables to the layout.
• Create one row of recordset data with the values replaced by variables.

Add to Layout Window

The Add to Layout dialog box contains two sections: The Assets Pane and the Step Columns
Area.

Figure 32 – Add to Layout Window

Add to Layout: Assets Section

Layout Folder — Displays the folder path of the existing or new layout for the current
process. If a new layout is being created, it will be created in the same folder path as the
process.
Layout Name — Displays the name of the existing or new layout for the current process.
If there is no layout associated to the process, the new layout will have the same name as
the process.
Recordset Name — Allows input of a name for the recordset. If it is an existing layout
with recordsets, a recordset from the drop-down list can be selected.
Variable Folder — Displays the folder where the new variable will be placed. The value in
the field is the root variable folder of the project. A different location is rarely used.

115 | P a g e
Add to Layout: Columns Section
The following table outlines the columns on the Add to Layout window.

Column Description
Displays the narrative of the selected step. This column is read-only. If the
step is not a typical Input or Verify step, the narrative will be prefixed by
Narrative
“???”. If this prefix is present; this step may not be an appropriate step to
drive the data.
If the parameter can accept a variable, select a variable from the drop-
down list. If the parameter cannot accept a variable, the drop-down list is
Parameter
not displayed, nor is it displayed if a parameter contains a user, local, or
system variable.
If the current value of the parameter contains a variable, the value appears
Value
as (V) plus the variable name. This column is read-only.
Allows selection of one of the following values:
Create Variable — This value will appear in the list if a variable need to
be created for the current parameter.
Use Variable — This value will appear in the list if the current parameter
Action value is a variable.
Select Variable — This value will appear in the list if the current
parameter value is a literal value. If you select this option, the Select
Variable dialog box appears allowing selection of the variable to use in this
parameter.
Shows the name of the variable to be used in this parameter. If the
parameter already contains a variable, the column is not editable. If the
parameter contains a literal value, editing of the variable name is possible.
Variable If the variable name is changed, Certify will check to see if a variable by
that name already exists in the specified variable folder. If the variable does
exist, the Action column value is updated to Use Variable. If a variable
does not exist, the Action column value is updated to Create Variable.
Allows selection of the data type of the parameter. The available values in
the list depend on the data type of the parameter.
Type If the value for the Action column is Use Variable, this column displays the
data type of the selected variable. If the Action column value is Create
Variable, select the data type to use when creating the variable.
Table 5 — Add to Layout Column Options

116 | P a g e
EXERCISE 5.3 — Create the WSA_PO_Create Layout Using Add to
Layout
This exercise will show how to create the WSA_PO_Create Layout and Recordset using the
Add to Layout feature to parameterize the data.

Steps Action Description

1. Select IWCA_PO_CreateEditAndVerify Folder
2. Go to Summary Pane
3. Open WSA_PO_Create Process
4.
Select -
Steps 3 – 6

5. Add to Layout

Right-Click
and Select

6. WSA_PO_Create as the Recordset Name

Enter

7. Go to Parameter Column
8. All four (4) steps should have a Parameter entry of “Value”

Verify

9. All four (4) steps should have an Action entry of “Use Variable”

Verify

117 | P a g e
10. Verify the variable name. If needed, use the Select Variable action at the
step level to choose the correct variable name. The Add to Layout dialog
box should match exactly the screenshot shown below.
Note

11. For Ship to and Bill to, if the database does not have a variable that
matches exactly, choose a variable that is similar. For example, Ship-to
Party, Ship to Party, Bill-to Party and/or Bill to Party
12. OK
Click

13. Save
Select

14. After saving, a small paper sign will be added to the process gear in the

Navigation Tree. This shows that a recordset is

attached to your WSA_PO_Create process. If the small paper sign is
Note

not visible, refresh your process using the Refresh button in the
toolbar

15. Recordset Tab

Click

You will see one row of existing data in the Recordset

16. Locate Position the cursor in the PO Number field
17. The Tab key until the cursor locates in the new 2nd record. This can also
Click
be accomplished by clicking on the asterisk button .
18. A row to WSA_PO_Create Recordset by entering the following
data in the appropriate columns over the existing data.
Name – John Smith
Add
Ship to – 3000
Bill to – 3000

19. Save
Click

118 | P a g e
 While entering data into a recordset, use TAB to move from one
Note column to another; this eliminates the chances of adding additional
spaces or carriage returns.

If you don’t see an empty recordset row, close and reopen the
Important
WSA_PO_Create process

View and Edit Recordset

Steps Action Description

20. Go to Navigation Taskbar
21. Data
Click

22. Select 02. New project folder

23. O2.04 Development Folder
Select

24. IWCA_PO_CreateEditAndVerify (If folders do not exist, Certify

creates them automatically when you use this Add to Layout
Select option)

25. Right-click WSA_PO_Create layout

26. Select Edit
27. WSA_PO_Create layout is displayed (Add, Modify & Delete
Variables)

View

28. Ok to close the layout

Click

119 | P a g e
 Steps Action Description
29. View and Edit The Recordset
30. Recordset Tab
Click

31. Select WSA_PO_Create recordset

32. Right-click WSA_PO_Create
33. Select Edit
34.

Display – Recordset
Editor

35. OK
Click

Users can edit the Layout and Recordset from within the Process
Note Details tab of any process by selecting the Layout button – this will
open the appropriate area within Data.

EXERCISE 5.4 — Create the WSA_PO_Create_C_Materials Layout and

Recordset
This exercise will show how to modify the WSA_PO_Create_C_Materials process to
work with the Material Table object. Using the table object allows Certify to find an empty
row for entering the material’s details: Material Item, Quantity, and Price.

Step Action Description

1. Go to Navigation Taskbar
2. Processes

Select

120 | P a g e
Steps Action Description
3. Navigate to Development folder
4. Select IWCA_PO_CreateEditAndVerify Folder
5. Go to Summary Pane
6. WSA_PO_Create Process

Open

7. Steps Tab
Go to

8. This will display the steps in the child process

Double click on Step 8
WSA_PO_Create_C_Materials
9. Steps 2 – 4

Select

10. Add to Layout

Right-click and select

11. WSA_PO_Create_C_Materials in the recordset name field

Enter

12. Go to Parameter Column for Steps 1-3

121 | P a g e
Steps Action Description
13. Value

Drop-down select

14. Action

Go to

15.
Material, Quantity_Numeric and Price_Numeric
Select Variables

16. Click - OK
17. Click – OK
(Note: This message
indicates that a layout
has been created to a
child process)
18.
Click - Save

19. Press Refresh (until the icon changes in the navigation tree)
20. WSA_PO_Create_C_Materials folder will have a table icon
View on it – indicates a layout and recordset are attached

21. Recordset tab – one row of data exists

Select

122 | P a g e
 Steps Action Description
22. Material = P-700
Quantity_Numeric = 1
Price_Numeric = 1245

Add a new Record

23. Select - Save

EXERCISE 5.5 — Create a Recordset for

WSA_PO_Edit_QuantityAndPrice Process (Optional)
This exercise will show how to create the WSA_PO_Edit_QuantityAndPrice Layout and
Recordset using the Add to Layout feature to add a variable.
Steps Action Description
1. Go To Navigation Tree
2. Select Processes
3. Select IWCA_PO_CreateEditAndVerify Folder
4. WSA_PO_Edit_QuantityAndPrice Process

Open

5. Steps Tab
Go to

6. Steps 4 and 5

Highlight

123 | P a g e
Steps Action Description
7. Add to Layout

Select

8. Recordset name WSA_PO_Edit_QuantityAndPrice

Enter

9. Go to Step 4
10. Find Parameter Drop-down list
11. Value

Select

12. Go to Action Column

13. Select Use Variable

Choose

14. Select -
Quantity_Numeric
Variable

15. Go to Step 5
16. Find Action Column
17. Choose Select Use Variable
18. Price_Numeric
Select

124 | P a g e
Steps Action Description
19. OK
Click

20. Save
Select

21. Refresh until the table is displayed on the process gear in

Press the Navigation Tree for your
WSA_PO_ Edit_QuantityAndPrice process
22. Go to Navigation Tree
23. Select IWCA_PO_CreateEditAndVerify process
24. Save
Select

25. Select Step 4

26. Save
Click

125 | P a g e
EXERCISE 5.6 — Create a Layout and Recordset for the
IWCA_PO_CreateEditAndVerify Integrated Process
This exercise will show how to create the IWCA_PO_CreateEditAndVerify Layout and
Recordset using the From Processes feature when manually creating a layout.

Steps Action Description

1. Go to Navigation Taskbar
2. Data

Select

3. Navigate to Development folder

4. Select IWCA_PO_CreateEditAndVerify folder
5. Go to Layouts Summary Pane
6. Right-Click Summary Pane
7. New Layout

Select

8. IWCA_PO_CreateEditAndVerify as the name of the layout

Enter

9. Create Drop-down menu

Find

126 | P a g e
Steps Action Description
10. From Processes and Child Processes

Select

11. Child Process Depth drop-down menu

Find

12. Enter 1
13. Select
Press

14. Navigate to Development Folder

15. Select IWCA_PO_CreateEditAndVerify folder
16. Select IWCA_PO_CreateEditAndVerify process
17. OK
Click

18. _Row, Material, Quantity, and Price variables. Leave the

following variables:

Delete

19. OK
Click

20. Select Recordsets Tab

127 | P a g e
Steps Action Description
21. New Recordset

Right-click & Select

22. IWCA_PO_ CreateEditAndVerify

Name Recordset

23. Name: Mary Wilson

Enter record #1 Ship to: 3000
Bill to: 3000
24. Name: John Smith
Ship to: 3000
Bill to: 3000
Enter record #2

25. OK
Click

26. Go to Navigation Taskbar

27. Processes

Select

28. Navigate to Development Folder

29. Select IWCA_PO_CreateEditAndVerify folder
30. Select IWCA_PO_CreateEditAndVerify process
31. Right click Edit
32. Layout Button
Select

33. Browse Layout in Data

34. Select IWCA_PO_CreateEditAndVerify layout

128 | P a g e
 Steps Action Description
35. OK
Click

36.

Change Recordset Mode

Read and Update
-

37. Save
Click

Verification Steps: If you add the Layout/Recordset directly to the child process, you can
delete it from the parameters
38.
Press *Refresh until table shows to the process gear in navigation
tree
39. Steps Tab
Go to

40. Row 3
Select

41. In the Parameters:

Delete
Layout: WSA_PO_Create (As highlighted in Figure 33)
42. Save
Click

Figure 33 – IWCA_PO_CreateEditAndVerify steps

129 | P a g e
Execute Processes with Data
The integrated process IWCA_PO_CreateEditAndVerify is now ready to execute with data.
The process will execute the WSA_PO_Create process, execute the
WSA_PO_Create_C_Materials child process, execute WSA_PO_Edit_QuantityAndPrice and
use their layouts and recordsets for data.

EXERCISE 5.7 — Execute Processes with Data

This exercise will execute an integrated process that includes multiple layouts and
recordsets. This exercise uses the Running Man to run the entire process rather than
executing a step at a time.

Steps Action Description

1. Go To Navigation Taskbar
2. Go to Navigation Tree
3. Click IWCA_PO_CreateEditAndVerify folder
4. Go to Summary Pane
5. Right click IWCA_PO_CreateEditAndVerify process
6. Run or the Running Man Icon
Select

7. Click The Start

button
At the bottom of the
Configuration screen

8. Run

Click

At the top of the Execution screen

9. Results Viewer

View

130 | P a g e
 10. Click Close or X in corner of the Results viewer
11. Open Process Editor – Make necessary Corrections
12. Click Refresh to see the current Process status

Figure 34 – Process Status

Recordset Filters
Recordset filters are used to select rows of data from a recordset that will be used during
execution of a child process.
The left pane of Figure 1 contains the variables from the WSA_PO_Create_C_Materials
layout.
The bottom-right pane of Figure 1 is used to select a variable for comparison and the
criteria for the comparison. The criteria list has many options such as Contains, Is Equal
To, and Is Empty. These can be made “negative” by selecting the Not checkbox.
The top-right pane of Figure 35 contains a list of the selection criteria as set using the left
pane and bottom-right panes.
Multiple variables can be compared in a recordset filter.
For example, you may select the Variable Name, Is Empty, and the Not checkbox to
include records where the Name is Not Empty.

In many examples, the variables being compared are from two

layouts. The Variables selected at the bottom for comparison does
Note:
not need to be in a layout and could be based on a value read from
the application. The variable names do not need to match.

131 | P a g e
 Figure 35: Recordset Filter

Recordset Filter for the Worksoft Web Sample

Application
The WSA_PO_Create_C_Materials process will insert and create the same materials each
time the process is executed. This behavior needs to be modified so that when a purchase
order is created, only specific materials are added for that PO.
A common variable is needed to be used as the filtering criteria. Currently, there isn’t a
variable used in both the IWCA_PO_ CreateEditAndVerify Layout and in the
WSA_PO_Create_C_Materials Layout. A good candidate is needed from the
IWCA_PO_CreateEditAndVerify layout that can be added to the
WSA_PO_Create_C_Materials layout for specific materials to be added during execution.
The PO Number field will vary each time the process is executed, so it would not be a good
candidate. The Name does not vary so that can be used to tie the two Layouts/Recordsets
together.

Figure 36 - IWCA_PO_CreateEditAndVerify Recordset

Figure 37 - WSA_PO_Create_C_Materials Recordset

132 | P a g e
In the next exercise, the Name variable will be added to the WSA_PO_Create_C_Materials
Layout and a name will be assigned from the IWCA_PO_CreateEditAndVerify recordset to
each material.

Figure 38 - WSA_PO_Create_C_Materials Recordset - after adding Name variable

EXERCISE 5.8 — Using a Recordset Filter

This exercise will show how to modify the WSA_PO_Create_C_Materials layout to add an
additional column that will be used as a recordset filter.

Steps Action Description

1. Go To Navigation Tree
2. Data

Select

3. Find IWCA_PO_CreateEditAndVerify folder

4. Right-Click & Edit WSA_PO_Create_C_Materials layout
5. Select The First Variable or MaterialMa
6. Insert

Right-Click &
Select

133 | P a g e
Steps Action Description
7.

Select - Name

8. OK to close Variable window

Press

9. OK to close Layout window

Press

10. Recordset tab at bottom of screen

Click

11. Double click &

WSA_PO_Create_C_Materials
Edit
12. Enter Name 1 “Mary Wilson” for Material P-100
13. Enter Name 2 “John Smith” for Material P-700
14. OK to exit
Press

15. Go to Navigation Taskbar

16. Processes

Select

17. Click IWCA_PO_CreateEditAndVerify folder

18. Go to Summary Pane
19. Double-Click IWCA_PO_CreateEditAndVerify process
20. Select WSA_PO_Create process from the left navigation tree
21. Click Steps
22. Step 8
Go to
23. Find Parameters
24. Scroll to Recordset Filter option (Scroll until visible)

134 | P a g e
Steps Action Description
25. Browser Button
Press

26. Name variable in the left navigation

Double-click

27. Verify The Name Variable is in the Value Field

28. Drop-Down List &
Select - Is Equal
to

29. OK
Select

30. Recordset Filter is enabled

Verify

31. Save
Press

32. Go to Navigation Tree

33. Select IWCA_PO_CreateEditAndVerify process
34. Select WSA_PO_Create_C_Materials process
35. Mary Wilson for Material P-100 and John Smith for Material P-
700

Verify

36. Execute IWCA_PO_CreateEditAndVerify process

135 | P a g e
Export Data
Data can be imported to and exported from recordsets while working in the Recordset
Editor. Exporting data is saved to a text file using a delimiter specified by the user. Once
exported, the data can be managed in another data management tool and when ready, the
modified data can be imported back into the original or into a different recordset.

EXERCISE 5.9 — Export Data

In this exercise, data will be exported to a file from a recordset created in a previous
exercise.

Steps Action Description

1. Go To Navigation Taskbar
2. Navigate to Development folder > IWCA_PO_CreateEditAndVerify folder
3. Go to Summary pane
4. Select IWCA_PO_CreateEditAndVerify layout
5. Click Recordset tab
6. Right-Click IWCA_PO_CreateEditAndVerify recordset
7. Select Edit
8. Pop-up Recordset Editor box appears
9. Export

Click

10. Export Recordset dialog box appears

Pop-up

11. File Name Browse Button

Click

136 | P a g e
Steps Action Description
12.

Select – Export
File

13. Find File Name Field

14. Enter IWCA_PO_CreateEditAndVerify.txt
15. Browse My Documents
16. Save
Click

17. Export File dialog box closes, File name is cataloged in Export
Select
recordset dialog box
18. Comma option
Select

19. Include Headers option

Select

20. Select Text Qualifier Field

21. <none>

Drop-down &
select

137 | P a g e
 Steps Action Description
22. OK - file is exported as a .txt file
Click

23. Open Microsoft File Explorer

24. Navigate to The location file was saved
25. IWCA_PO_CreateEditAndVerify.txt

Open & View

26. Add Lines to the file by copying and pasting

27. Delete PO & Doc numbers for each line added
28. Save With NEW name (use this file for import record import)

Import Data
The Import Data process is like exporting a recordset.

EXERCISE 5.10 — Import Data

In this exercise, data will be imported from the file created in the previous exercise. It is
important to select the same options you specified when the file was exported.

Steps Action Description

1. Go To Navigation Taskbar
2. Navigate to Development folder > IWCA_PO_CreateEditAndVerify folder
3. Go to Summary pane
4. Select IWCA_PO_CreateEditAndVerify layout
5. Go to Details Pane
6. Click Recordsets tab
7. Right-Click and
New Recordset
Select
8. Import

Click

138 | P a g e
Steps Action Description
9. Import dialog box appears

Click

10. Click File Name

11. Select Import File dialog
12. File previously created

Browse

13. Click - Open

14. Comma option for the Column Delimiter

Click

15. Check Ignore First Line option

16. Click Text Qualifier drop-down arrow
17. <none>

Select

18. Click OK - file is imported to a recordset

19. Click OK to save and close the Edit Recordset dialog box

139 | P a g e
 There are Certify Steps which allow a process to Import Recordsets
Note:
and Export Recordsets during executions

As a best practice, you should do the following:

• Create a table or spreadsheet showing the processes and all the variables you will use
for each process.
• Use variable names that describe what type of data the variable contains and how you
will use the variable.
• A layout is a collection of variables that define the data in a recordset.
• You can create a layout at any time after creating a project although a layout is not
meaningful until it is connected to a process.
• If you have a process that has steps containing literal values or variables and no
associated layout, you can create a layout for the process using the Add to Layout
feature.
• Recordsets contain data values used in data-driven testing. A recordset is defined by
a layout. Once you have defined at least one layout, you can create recordsets and
add data values for the variables defined in that layout.
• You can attach recordsets to processes or process steps and either read data values
from the recordset to process steps or write values provided by the application you are
testing to the recordset.
• Using recordsets provides a way to loop through your application while a test is being
executed. The looping allows each row of data in the recordset to be used in the
process.
• When a recordset is used with a process, the process will execute one time for each
row of data in the recordset.
• After completing a test with the first row of data, the process will execute again with
the second row of data.

140 | P a g e
Lesson Summary
The Use Data to Execute Processes lesson has been completed.
Key points to remember:
• A variable is a symbol or name that represents a value. The most common use of
variables is for data-driven testing, where process execution loops through a series of
data values.
• Variables can also be used when you need to store or verify system data (such as the
System Date or Machine Name) or when specific data for a user is required (such as a
user ID or password to log into an external system or application).
• When preparing to use variables, the first thing you should do is go through your
existing processes and identify all the places where variables can be used in place of
data. Once you have all the variables for the process identified, you then need to
determine the type of variables you are using: System, Project, Process, or User.
• A layout created using any method can be manually edited to add or remove variables.
• A recordset will automatically be updated with any new variables added to a layout,
but you will need to provide the values.
• Recordset filters provide a dynamic way to process specific records matching a
condition.
• You can export data from Certify to an external file and make changes.
• You can import data from an external file into Certify.

141 | P a g e
Lesson 6 - Configure Execution and View Results
Overview
Previous lessons have covered the execution of Certify processes. This lesson discusses
more advanced execution techniques, as well as how to view execution results in the
Results Viewer and how to generate and view execution results in either detail or summary
reports. You will also learn how to create a .BAT file by exporting a process.

Objectives
After completing this lesson, you will be able to:
• Configure process execution
• Manage execution results
• View execution results in the Results Viewer window
• Edit Process Steps from the Result Viewer
• Manage execution results
• Generate Detail and Summary Reports of the execution
• Export a process to a .BAT file

Execution Configuration
Prior to the actual execution of a process, the configuration parameters will need to set to
ensure the execution meets your requirements. Configuration consists of setting the run
and log settings and providing where to find input data and startup data. As shown in
Figure 33, the Configuration dialog box provides options for choosing the type of
execution, how and when execution is performed, and how the results are handled.

Figure 33 — Configuration Dialog Box

142 | P a g e
Settings Tab
Run Settings Section

Stop/Pause On Failure — By default, execution does not stop on failure. If you want
your execution to stop when a failure is encountered in your process, select this checkbox.
Failure includes failed and aborted steps.
Select this checkbox when you are running your process. This allows
Tip: you to debug the errors and prevents your process from continuing
to execute after a failure.
Run Mode — Select how you want to manage the execution or accept the default of
managed run mode. Modes include managed, manual, and unmanaged.
Managed mode allows user intervention to step through processes, set
breakpoints, and capture screens. Managed mode assists you in debugging your
processes.
Manual mode requires complete user intervention. Manual mode is required when
an application is not being run (or not developed), and you have no automation, or
the automation is not working. If the mode is Manual, the Execution dialog box will
have an additional tab called Manual Execution.
Unmanaged mode prevents stepping through the execution, setting breakpoints,
and capturing screens.
Step Delay — Select the number of seconds to delay execution between each step or
accept the default of 0 seconds. Step delay helps resolve timing issues when testing the
application.

Logging Settings Section

Log Step Mode — Select how the step is to be logged or accept the default of LogAllSteps.
The modes include: LogAllSteps, LogAbortedStepsOnly, LogFailedSteps, LogProcessOnly,
LogStatusOnly, and LogDisabled. When you determine your process is complete, you can
log aborted or failed steps only.
Capture Screen On — Select if and when to capture screens during process execution or
accept the default of CaptureNone. Modes include: CaptureNone, CaptureAbortedSteps,
CaptureAllSteps, CaptureFailedSteps, CaptureAbortedAndFailedSteps, or WindowChange.
The WindowChange option is helpful when you want to see the window or object that is
failing in the application. It is also good for a result, giving a screenshot after every window
change. All screen captures are in *.jpg format.

We suggest selecting CaptureAbortedAndFailedSteps so that any

Tip: steps with errors will include a screen capture for debugging
purposes.

143 | P a g e
Screen Capture Mode — Select how much of the area of the application screen to
capture or accept the default of CaptureDesktop. Modes include CaptureDeskTop and
CaptureActiveWindow.
Output Location — Click the Output Location browse button to change the location of the
results stored for this process execution or accept the default displayed. The Select Results
Folder dialog box allows selection of any project for which the user has permissions. Make
the folder selection and click OK in the Select Results Folder dialog box. The default is the
top-level Results folder for the opened project.
To add interface debugging to the interface log, select the Add interface debugging to
Certify log checkbox.
Data Section
Layout (optional) — Click the Layout browse button to browse for a layout. The default is
the current layout associated with the process. If blank, no layout is associated with this
process. If a layout is chosen but not a recordset, the layout is ignored during execution. To
delete a selected layout, click the trash button.
Recordset (optional) — If a layout is associated with this process and a recordset exists
for that layout, this field is active. Select the down arrow to choose the recordset you want
to use.
Recordset Mode — If a recordset is associated with the layout, this field is active. Select
the down arrow to choose the mode for the selected recordset. Options include Read Only,
Append, Clear and Append, and Read and Update. Table 6 below explains when and how
each mode is executed.

Mode When Executed How Executed

Reads recordsets at the beginning Loops process once for each row until End
Read Only of execution. of File.
Writes recordsets at the end of Appends to existing recordset and loops
Append execution. process until Abort or Exit.
Clear and Writes recordsets at the end of Creates new recordset for each execution
Append execution. session and loops process until Exit.
Read and Reads recordsets at the beginning Updates the recordset at the end of the
Update of execution. process.
Table 6 — Identified Recordset Modes for Processes

Application Version Startup Data Area

Application Version Already in Context — In context implies that the application is

already loaded, and application has been where the selected process begins. Insert
checkmarks for any or all the application versions to be checked for context. By default,
there is no checkmark, meaning that the process will run. If the box is checked then the
process will not run.
Checkboxes will appear under ‘Application Version Already In Context’ for the application
versions which are assigned Start process in the current project. The application version will
have the name of the Start process if one has been created and selected in the project.

144 | P a g e
If no application versions have been checked and there is not a defined start process, the
start process loads the application, performs logging into the system, and navigates to the
main window or starting state before starting execution of the process.

Attributes Tab
Results Attributes — Shows all attributes created for Web links. Set the fields with values
before executing so the values are stored with the results.

Configuration Dialog Box Buttons

• Restore Defaults — Resets the fields back to the system defaults.

• Export — Displays the Save As dialog box to save the current execution
configuration parameters as a program command line in a batch file.
• Start — Displays the Execution dialog box so you can run your process.
• Cancel — Ignores all information and returns you to the previous screen. No
changes are saved.

Execution
After clicking Start in the Configuration dialog box, the Execution dialog box appears, as
shown in Figure 34 below. After execution, the Result Viewer dialog box will appear if the
process was executed using the Run button. Once configuration is complete, you can set
additional execution functionality in the Execution dialog box, such as skipping process
steps, capturing application windows, and setting breakpoints.

Figure 34 — Execution Dialog Box

You can restart after a failed step. If you selected the Stop on
Note: Failure option in a Managed execution mode, you can restart the
execution on a different step. Right-click on the step and select Set
Execution Pointer to restart execution.

145 | P a g e
Execution Buttons
The following Execution buttons offer you different options when running your processes.
Run — Executes the process to completion without using intervention.

Figure 35 – Execution Step Dropdown

Step — Executes the current step of a process. The Step drop-down menu offers
three options:
Step — Executes each step of the process. If the step is an Execute Process
step, then the execution moves to the first step of the called process.
Step Over — Executes the current step. If the current step is an Execute
Process step or is a result of True/False logic, then all sub-processes are
executed, and the execution moves to the next step of the current process.
Step Out — Executes to the end of the current process and stops at the next
step of the parent process or the first breakpoint set in the current process.

Figure 36 – Execution Skip Dropdown

Skip — Skips a step during execution of the process. The Skip drop-down menu
offers two options:
Skip — Allows you to skip the selected step and continue execution at the
next step. If the current step is an Execute Process, then the process will not
be executed.
Skip Out — Ignores the remaining steps of the current process and execution
starts again at the next step of the parent process or the first breakpoint set
in the current process.

Figure 37 – Execution Stop Dropdown

146 | P a g e
 Stop — Stops the execution at the next step, and the Results Viewer appears. Test
will be marked aborted by the user.
Skip results – Stop the process execution and skips the display of the result
window.
No results – Stop the process execution and does not create a result file.

Figure 38 – Execution Capture Dropdown

Capture — Adds a step to capture a screen image of the active window or desktop
during execution. This option is helpful when you want to see the window or object
that is failing in your application. The Capture drop-down menu offers two options:
Capture Active Window — Captures the application screen.
Capture Desktop — Captures the entire desktop.

Figure 39 – Execution Pause Button

Pause — Pauses the managed process execution.

Execution Dialog Box Tabs

The following Execution tabs offer you different views when debugging your process
execution.

Figure 40 – Execution Dialog Steps Tab

Steps — Displays the steps of the current process to be executed. You can expand
the Step view by clicking the Expand/Collapse button on the right of the dialog box.
The Expand view allows you to view the steps while using the other tabs.

147 | P a g e
 Figure 41 – Execution Dialog Variables Tab
Variables — Displays the current values of the variables in the current process
(Process tab), in the current step (Step tab), or added variables (Watch tab).
Watched variables are persistent throughout execution. The Process tab shows local
variables.

Figure 42 – Execution Dialog Recordset Tab

Recordset — Displays the recordset data that is used in the execution of the current
process.

148 | P a g e
 Figure 43 – Execution Dialog Breakpoint Tab
Breakpoint — Allows you to view, set, remove, or clear all breakpoints in any called
process during execution.

Manage Execution Results

After process execution, the Result Viewer shows a log of the execution results. By now you
have seen the Result Viewer a few times. Once you close the Result Viewer, it is stored and
managed in the Results window and is accessible from the Certify Navigation Taskbar.

149 | P a g e
 Figure 44 — Result Viewer
By right-clicking a result in the Summary Pane, you can perform tasks such as:
View execution results — All your execution results that you saved are stored in the
Results window so that you can open them in the Result Viewer or perform routine
maintenance.

Figure 45 – Result Viewer

150 | P a g e
Generate a results report — A report for a selected execution result can be generated
showing either a summary of the result or all the result details. The Report Viewer allows
you to navigate the report, as well as print and/or export the report.

Figure 46 – Result Reports

Compress the results — Helps reduce the size of your database and increase performance
by removing all process step execution results. You can keep only process summary
information or both process summary and failed step information.

Figure 47 – Results Compress Options

Promote to a Result of Record — You can identify a specific execution result as a Result
of Record, which means that result is the official execution result used to determine the status
of processes linked to test requirements, and therefore, the overall satisfaction of the
requirement.

Figure 48 – Promote to Result of Record

151 | P a g e
Export Result Summary — The summary of a selected result can be saved to an .xml file
for external use.

Figure 49 – Export Result Summary

In the Details Pane, you can view the details for a selected result and view the values of
any user-defined attributes associated with the results.

Figure 50 – Results Details Pane

View Execution Results

The Result Viewer allows the expansion of the execution results to show each process and
step executed. The Navigation Tree displays a log header with details about the process
executed. Under the log header is a hierarchy of processes executed. each level of the
hierarchy can be expanded, and information viewed about the executed processes and
steps in the Summary Pane.
Processes in the Summary Pane display information about test status, elapsed time, start
time, end time, and who created and modified the process. The Details Pane displays
additional information about the process and any associated recordset values that were
used by the process.

152 | P a g e
 Figure 51 — Result Viewer

Steps in the Summary Pane display information about test status, elapsed time, start time,
end time, as well as the components of the step. The Details Pane provides additional
information about the executed step, including step execution details, parameters used in
the step, recordset variable data used by the step, and any captured images. Table 7 lists
all of the statuses available for the executed processes.

Status Description
Passed step or process
Skipped step or process
Failed step or process
Aborted step or process
Table 7 — Executed Process and Step Status

Each executed process or step is given one of these statuses. In some cases, a process
inherits a status based on the status of another process or step. For example:
• If a process passes, then all the steps in the process passed.
• If a process fails, then at least one step in the process failed.
• If a process is skipped, then all steps in the process are skipped.
• If a step or process is aborted, then the execution is stopped.

153 | P a g e
 • If a step failed execution in a process, the process also fails unless the process was
aborted.
• If a step is aborted, the process shows aborted even though some steps may have
passed, skipped, or failed execution.
• If a process has more than one sub-process and the sub-process fails execution, the
parent process is shown as a failed process.
• If a process has more than one sub-process and the sub-process is aborted, the
parent process is shown as an aborted process even though some sub-processes
may have passed, skipped, or failed.

Configure Advanced Execution

In a previous lesson, the Execution window was described. In this exercise, advanced
execution techniques which will help with troubleshooting will be examined.

EXERCISE 6.1 — Configure Advanced Execution

In this exercise, you will configure and use advanced execution techniques.

Steps Action Description

1. Go To Navigation Taskbar
2. Select Processes
3. Select IWCA_PO_CreateEditAndVerify folder
4. Go to Summary Pane
5. Right-click IWCA_PO_CreateEditAndVerify process
6. Select or Press Run or Running Man Button
7. Pop-up Configuration Dialog box appears
8. Results folder is selected

Verify

9. Start
Click

10. the first, TWO steps of your integrated process to process

Execute
and verify the Websoft Web Sample Application

154 | P a g e
Steps Action Description
11. Step Button until the first two steps of the integrated
process have executed and passed

Press

12. Step 3 is your second sub-process.

13. Step so the Execution window displays the step in the sub-
Press
process
14. Notice that the Variable names are displayed in the
Narrative column of each step. The values for the variables
will display when a step containing a variable is about to be
executed.

Note

15. Press Step Button to execute the Name Activity Step

16. Press Step Button
17. Click Expand button (lower right-hand corner)
18. Click Variables Tab
19. Step Tab

Click

20. This allows you to view and edit the value at execution.
**Only edit variable values if the Recordset Mode is set to
Read Only, otherwise the edited value will be
written to your recordset.

155 | P a g e
Steps Action Description
21. Right-Click Step 8
22.

Select -
Set
Breakpoint

23. Press Run

24. Click Step Drop-down list
25. Step Out

Select

26. Certify will execute the rest of the sub-process steps and bring the
Note
execution back to the main process
27. Press Step Button – Step 3 will open, select next sub-process
28. Press Skip Button
29. Certify will skip the first step in the sub-process. The Execution
Note
window will be positioned on Step 2 of the current sub process
30. Click Skip Drop-down list
31. Skip out - Certify will skip the rest of the steps for this sub-process.

Select

32. Capture Drop-down list

Click

156 | P a g e
Steps Action Description
33. Capture Active Window - A screen capture will be included in the
Select Results Log. This can be used at any point you want to manually
capture a screen during execution
34. Press Run - Certify will execute steps until the Breakpoint at Step 8
35. Step dropdown list

Click

36. Step Over - Step 8 will execute and the execution will be brought
Select
back to the last step of the current sub-process
37. Right-click Step 8
38. Clear Breakpoint

Select

39. Press Step Button

40. Press Stop Button to end the execution
41. The breakpoint must be cleared, or all future executions will stop at
Step 8.
42. Status is reported as Aborted

43. Navigate The Results Viewer to see where steps skipped, failed and passed.
44. Close Results Viewer

157 | P a g e
Edit Process Steps from the Result Viewer
To quickly edit steps, navigate from a step in the Result Viewer to the corresponding step in
the Process and Data Editor. As shown in Figure 35, selecting and right-clicking the step to
be reviewed and/or edited in the Result Viewer Summary Pane, Edit Step can be selected
from the list. The Process and Data Editor window opens to the step selected. From here
the step can be modified, and the test process can be run again.

Figure 52 — Edit Process Steps from the Result Viewer

Generate Execution Reports

Generating reports on execution results is performed from the Summary Pane of the Results
window. From here a report can be run that shows a summary of the selected results from
the process level or details of the results including step components, as well as a recordsets
report that displays only steps with values of the selected results.
If a PDF View (such as Adobe Acrobat) is not installed on the
Note workstation, the execution report will still be created. If this is a
case, copy the file to an area where a workstation that does have a
PDF viewer can open the file
The execution reports are displayed in .pdf format. As shown in Figure 36, the report
displays the results in the same order they are displayed in the Results Viewer (order of
execution).

158 | P a g e
 Figure 53 — Sample Execution Report

EXERCISE 6.2 — Generate an Execution Results Summary Report

from the Results Window
In this exercise, a summary report of the execution results will be run for reviewing or
reporting needs.

Steps Action Description

1. Go To Navigation Taskbar
2. Select Results File to be Reported On
3. Right-Click Selected Results File in Summary Pane
4.

Select - Reports >

Reports
(Summary)

159 | P a g e
 Steps Action Description
5.

Choose - Location
to save the Report

6. Enter Desired File name

7. Save
Click

8. Open Report (PDF Format)

EXERCISE 6.3 — Generate an Execution Results Detail Report from

the Result Viewer
This exercise will run a detailed report of the execution results for reviewing or reporting
needs. The same report could be run from the Results window.

Steps Action Description

1. Go To Navigation Taskbar
2. Select Results
3. Select Desired Results folder
4. Right-Click Summary Pane
5. Select Desired process
6. Select Reports Menu
7.

Select –
Results Details

8. Choose Location
9. Enter File Name Field
10. Enter Desired File Name
11.
Click - Save

12. Open Report in PDF Format

160 | P a g e
Export the Test Process to a .BAT File
Certify is able to export any process to a Microsoft batch file (.BAT). This file can be
executed by double-clicking on the file name from Windows Explorer or DOS prompt. The
file can also be used by a scheduler to kick off test runs at predetermined times and days.
Refer to the Worksoft Community site http://community.worksoft.com for
Note:
a complete description of Worksoft’s Lights Out methodology for
unattended test execution

EXERCISE 6.4 — Create a .BAT File

This exercise will create a batch file that contains all the configuration information for the
current process.

Steps Action Description

1. Go To Navigation Tree
2. Select Processes
3. Select IWCA_PO_CreateEditAndVerify folder
4. Right-Click IWCA_PO_CreateEditAndVerify in the Summary Pane
5. Select Run or press the Running Man button
6. The Configuration dialog box appears. For Batch File execution,
Note you may wish to create and specify a specific folder to hold
results.
7. Output Location browse button
Click

8.

Select –
Results folder

9. Click OK
10. Export button
Click

11. The Save As screen appears. You may wish to create a

Note
specific folder that contains Certify batch files.
12. Navigate To appropriate folder on your computer or network
13. Input File name

161 | P a g e
 14.

Input –
Save As
Type
“bat files
(.bat)”

15. Save
Click

16. Saved .BAT file using Notepad

Open
(Select file, right click edit)

The example file created here is not completely ready for unattended
Note:
execution. The batch file requires a Certify User and Password to be
entered on the command lines.

Figure 54 – Sample .BAT File

The process expects that the Worksoft Web Sample Application is open to the PO page. For
true unattended execution, this process should be updated to include steps to launch and
close the application.

162 | P a g e
17. Format dropdown

Click

18. Select Word Wrap

19. Text highlighted in blue in Figure 55 and Figure 56
Delete
below

Figure 55 – Sample .bat file

Figure 56 – Sample .bat file

163 | P a g e
 20. The User ID and Password to provide values. These values
need to be your Certify User ID and Password so that the batch
file can access the Certify database. See Figure 40 below.
Update
21. Save
Click

22. Dbl-click .bat file to execute

Figure 57 – Change User ID & Password in .bat file

Lesson Summary
The Configure Execution and View Results lesson is complete.

Key points to remember:

• The Configuration dialog box provides options for choosing the type of execution,
how and when execution is performed, and how the results are handled.
• Once configuration is complete, additional execution functionality can be set in the
Execution dialog box, such as skipping process steps, capturing application windows,
and setting breakpoints.
• After process execution, the Result Viewer shows a log of the execution results.
• The Result Viewer allows expansion of the execution results to show each process
and step executed. Each level of the hierarchy can be expanded so information about
the executed processes and steps in the Summary Pane can be viewed.
• Generating reports for execution results can be performed from the Summary Pane
of the Results window. A report can be run which shows a summary of the selected
results from the process level or details of the results including step components, as
well as a recordsets report that displays only steps with values of the selected
results.
• Certify allows the export of any process to a Microsoft batch file (.BAT) that can then
be executed by double-clicking on the file name from Windows Explorer or DOS
prompt. The file can also be used by a scheduler to kick off test runs at
predetermined times and days.

164 | P a g e
Lesson 7 Certify System Objects and Actions
Overview
This chapter is a reference of Certify system objects and their associated actions.

Objectives
Certify System Classes and Actions
In addition to using the objects in the application under test, such as SAP screens and
fields, HTML objects and links, etc., Certify comes with a set of built-in non-application
specific objects and actions to allow users to work with such things as dates (date math,
date components), Windows system commands, text manipulation (concatenate, compare,
etc.), and other helpful test building objects and actions.
For a complete list of System Classes and Actions, go to Certify Help
> Classes and Actions > System Classes and Actions
Reference Or
On the Naviation taskbar, click Interfaces, then select Syste. View
this area only. Modifying this list will cause problems in Certify.
Use these objects in your processes by adding a step with these characteristics:

Application Version Window Object Action

System 1.0 System Desired object Desired action

Figure 58 – Non-Specific Objects/Actions Step Characteristics

Figure 42 below shows a summary of the Certify system objects and their respective
actions.

System Object Action Usage Example

Compare (V)Ship Date to
Compare Compare one date to another
Todays date
Extract Day from Todays date
Extract Day, Month, or Year
Get Part
from a date Extract Year from (V)Posting
Date
Date
Add 7 Days to today’s date
Add or subtract Days or Weeks
Date Math
from a date Subtract 2 weeks from
(V)Expected Delivery date
Used to Set a variable to a
Set Set (V)Date to (V)Period Date
specific value

Execute Comment Used to insert comments into “Find and press the Post
Certify process steps. Helps Goods Issue button”

165 | P a g e
 describe certain conditions or
objects in the process for “Execute Process ‘XXXX’ if
maintenance purposes count> 5”

System Object Action Usage Example

Used to prompt the Certify user
“Load check paper into the
at runtime to perform some
Dialog Prompt Payroll printer and press Enter
action. The test is paused until
when Ready...”
the prompt is answered.
Allows a process to call a child
process. Once the child process OTC_StandardOrder
is complete, control returns to
Execute VA01_CreateOrder
parent process. A layout and
Execute Layout=VA01
recordset can be added to this
Process Recordset=Sales
step that may be needed to feed
Execute VL01N_ShipOrder
the child process.

Will cause the test to exit

Execute VF01_InvoiceOrder
Exit All regardless of what level of
If (V)Amount = 0 then Exit All
execution.
Exit the current process being
executed and return to the If (V)Available Qty < (V)Order
Exit Process parent process. If the current Qty then
process is the parent process, Exit Process
the test will exit.
Change flow to continue at a
Execute
different step in the process
rather than the next logical step. If (V)Order Qty = 0 then Jump
Jump
Note: works with the object to Label=” Enter Order Qty”
Label (see below) which is the
named entry point
A marker in the process that step
Label
flow might be redirected to Label=” Enter Order Qty”
A prompt that will pause the
Certify test being executed and
“Check Payroll Printer - did all
ask the user to supply a
Manual Step 48 checks print correctly”
true/pass status to a condition
[True/False]
outside the control of
Certify.
Examples of valid locales are
Set AUT Locale Change locale settings for de-DE, en- GB, en-US, es-MX,
various country specific formats fr_FR, it-IT, nl-nl
Cause Certify to change step compare (V)Ship-Date =
Start at first flow in a process to the (V)system Date
Step with Next beginning with the next record in
Record the recordset. EOF will cause the True=Continue | False=Start
process to end and return to the at first step with next record

166 | P a g e
 parent process or end the test if
it is the parent process.
Delay the process execution by x
Wait Wait 10 seconds
seconds between steps.

System Object Action Usage Example

Set option for whether to take

Capture Screen screenshots of the active
CaptureActiveWindow
Mode application or whole desktop
during process execution.
Set option for when to take
Capture Screen
Execution screenshots during the process CaptureAbortedAndFailedSteps
On
Setting execution.
Set optional delay between every
Step Delay Delay .5 seconds
step during execution
Set an option to stop the
Stop on Failure Check Stop on Failure
execution if a step fails.
Add data to the end of a text file
located outside of the Certify Append (V)Order Number to
Append Data
Database (ex: C:\orders\ OrderList.txt
C:\orders\OrderList.txt)
Clears the content of a text file
located outside of the Certify
Clear File Clear C:\orders\OrderList.txt
Database (ex:
C:\orders\OrderList.txt)

Delete File Deletes the text file located Delete C:\orders\OrderList.txt

outside of the Certify Database
(ex: C:\orders\OrderList.txt)
File
File Compare Compare two files. Compare One.txt with Two.txt
Verifies a text file located outside File Exist
of the Certify Database (ex: C:\orders\OrderList.txt (on
File Exists
C:\orders\ OrderList.txt) is True
present | on False)
Masked File Compares two .csv, .xls, or .xlsx
Compare One.xls with Two.xls
Compare files with masked cells.
Clears and appends data to the
end of a text file located outside Overwrite File (V)Order
Overwrite File of the Certify Database (ex: Number C:\orders\
C:\orders\ OrderList.txt
OrderList.txt)

167 | P a g e
 Read the contents of a text file
located outside of the Certify Read File (V)Order Number
Read File Database (ex: C:\orders\ OrderList.txt into
C:\orders\OrderList.txt) into a (V)Order List
variable

System Object Action Usage Example

Store File
Store File Store properties of a file “c:\temp\tempfile.txt”
Property into a variable. Property “CreationTime” into
D[Created On]
Compare (V)Amount Is
Greater Than 0
Compare ValueA against
Compare ValueB with various
Compare (V)Amount Is Less
compare criteria
Than or Equal To (V)Net
Value
Generate a Positive integer Get Random Number between
Get Random
random number between 100 and 9999 and store in
Number
MIN and MAX range (V)Random Number
Add 1 to (V)Counter and store
Perform standard Math
in (V) Counter
Math operations on numeric
Multiple (V)Amount by (V)QTY
values
and store in (V)Total
Round 1.50 to 0 decimals and
store in (V)Value (would be
File
stored as 2)
Round up a value based on
Round
the stated decimals value
Round 1.6899 to 2 decimals
and store in (V)Value [would
be stored as 1.69]
Used to Set a variable to
Set Set (V)Qty to 1
specific value
Used to seed the Random
Set Random Number to be more
Set seed value to 2
Seed random. Not normally
used.
Sum Sum up to 25 numbers Sum 10 20 30 40
(V)Temp Number=21.87
Truncate (V)Temp Number to
Drop off the decimal value 0 Decimal
Truncate depending on the number
of decimals specified [(V)Temp Number = 21]
(V)Temp Number=21.87

168 | P a g e
 Truncate (V)Temp Number to
1 Decimal
[(V)Temp Number = 21.8]

System Object Action Usage Example

Store a table value from an ODBC Database Store Select
external database using an VALUEX from TABLEX Where
Database Store
ODBC connection and CONDITIONX is true and store
standard SQL statements in (V)Table Value
ODBC Data
Verify a table value in an ODBC Database Verify Select
external database using an VALUEX From TABLEX Where
Database Verify
ODBC connection and CONDITIONX is true and store
standard SQL statements in (V)Table Value

Capture Take a screen shot of the Capture Current Screen

Screen desktop or the topmost
Image window Capture Active Window
Executes an external
Execute application C:\Sap\
Windows application by
Execute Sapshcut.exe /User=SA
Operating providing the application
Application Paccount / Password=SAP
System name and any command
password
line options
Get
Store the value of a system
Environmental Variable = Path
environment variable.
Variable
Enter in a standard DOS TASKKILL /f
DOS Command
command C:\windows\notepad.exe
Used to remove the
Clear Clear Recordset Layout=VA01,
contents of a named layout
RecordSet Recordset=TempRecSet
and recordset
Will export the contains of
Export Recordset
Export a Certify Recordset out to a
Layout=VA01,Recordset=Temp
RecordSet text file with selected
RecSet to c:\temp\
formatting
Flush will update the
database with any changed
Record Set values in a recordset rather Flush
Flush
than waiting until the end layout=VA01_SalesOrder,
RecordSet
of the Certify Process run Recordset=ExportOrders
so it can be available
immediately
Import Import data from a file into Import Jan2013Accounts.csv
RecordSet a specified layout/recordset
Will cause Certify to read a Read Record
Read Record
record as a step operation Layout=VA01_SalesOrder,

169 | P a g e
 outside the normal process Recordset=ControlData,
of layout/ recordset Index=2
attachment
Will update the recordset Refresh Recordset
Refresh
values with any variable Layout=VA01_SalesOrder,
RecordSet
changed in a process Recordset=ControlData
Imports any number of SQL “SELECT top 100
rows or columns into a [Name].[CreatedBy] FROM
SQL to
layout and recordset from a [Process] where
RecordSet
SQL Server Select [CreatedBy]<>1” to SQL to
Statement. RecordsetSample
If the recordset does exist,
Verify then subsequent steps
Verify RecordSet Existence
RecordSet (e.g. Execute Process)
RecordsetSample
Existence using that recordset can be
executed correctly.

Writes data into a single

record of Write recordset
Write Record
a layout and recordset. Layout=VA01_SalesOrder_Tem
Options are p,Recordset=OrderNumbers
Overwrite and Append [Overwrite | Append]
Compare (V)TaxCode Is
Greater Than G
Compare TextA against
Compare TextB with various criteria Compare (V)LastName Is Less
and case sensitivity options
Than or Equal To (V)Temp
with Case Matching
Concatenate (V)Full_Name
Concatenate Join up to 15 different text with
elements into one text (V)First_Name+(V)Middle_Na
variable me +(V)Last_Name
Switch text value between Convert Case (V)Last Name to
Text Convert Case
upper or lower case Upper Case
1) Set (V)String=”Record 1234
created”
2) Find Substring Starts with
Use to grab a portion of a
Record and ends with created
text string and place in a
and place in (V)Temp
Find Substring text variable based on a
3) (V)Temp=1234
known starting and ending
Note: If special characters are
text value.
part of the search string (ex:
ABC*1234) then use the \ to
escape the * - ex: ABCD-\**)

170 | P a g e
 1) (v)Temp=”123ABC#”
Find the number of 2) length (V)Temp store in
Length
characters in a string (V)Temp
3) (V)Temp=7
Find and replace text within
Day = Find and replace
up to two
Replace ‘Tuesday’ with
strings and save to
‘Wednesday’
variables
1) Set (V)String =
Use to grab a portion of a “ABCD1234#”
text string and place in a
2) Substring Starts with Index
Substring text variable based on a
5 and ending with Length 4
starting and ending index
and place in (V)Temp
number
3) (V)Temp=1234

1) Set (V)String =
“ABCD1234#”

Substring Find the Index of a text 2) Substring Index (V)String

Index string with Substring “1” place in
(V)Temp Number

3) (V)Temp Number=5

1) Set (V)String = “ ABCD ”

2) Trim Leading (V)String and

place in (V)Temp

3) (V)Temp = “ABCD “

1)Set (V)String = “ABCD ”

Trim off leading and/or
Trim
trailing spaces 2)TrimTrailing (V)String and
place in (V)Temp

3)(V)Temp = “ ABCD“

1) Set (V)String = “ ABCD”

2) Trim Both (V)String and

place in (V)Temp

171 | P a g e
 3)(V)Temp = “ABCD“

Verify the lengths of up to

Verify Length Verify String1 = 17
two strings of text.

System Object Action Usage Example

Change text to number or

number to text. (T)String = “00023”;
Note: changing text to a
Convert (T)String = (N)TempNo;
numeric value will only
work if the text string is a (N)TempNo = 23
Variable
Number.

(N)Counter = 0
Set Assign a value to a variable
(T)Name = “Toby”
Figure 59 – Certify Objects & Actions

EXERCISE 7.1 — Create a System Commands Process

This exercise will create a process using several System commands to interact with a
manually created recordset layout and recordset.
Steps Action Description
1. Go To Navigation Tree
2. Click Processes
3. Find and Select IWCA_PO_CreateEditAndVerify folder
4. Right click On Processes Summary Pane white space
5. + New Process

Select

6. UTL_SubstringFullName_ExportRecordset

Input Process Name

7. This process substrings first name and last name

Input Process
from the full name and exports the recordset to a
Description
.CSV file.

172 | P a g e
8. Save
Click

9. Click Steps Tab

10. Right Click Summary Pane white space
11. New

Select

12. Process Step 1

• Application Version System 1.0
• Window System
• Object Variable
• Action Set
Parameter Area
• Variable (V)Full Name
• Value to input John Smith
Enter Step Parameters

13. Save
Click

14. Right click Summary Pane white space

15. New

Select

173 | P a g e
16. Process Step 2
• Application Version System 1.0
• Window System
• Object Text
• Action Substring Index
Parameter Area
• Result (V)Index
• Input Text (V)Full Name
• Substring {SPACE}

Enter Step Parameters

17. Save
Click

18. Right click Summary Pane white space

19. New

Select

174 | P a g e
 Process Step 3
• Application Version System 1.0
• Window System
• Object Number
• Action Math
Parameter Area
• Value1 (V)Index
• Operation Subtract
• Value2 1
• Result (V)Index

Enter Step Parameters

20. Save
Click

21. Right click Summary Pane white space

22. New

Select

23. Process Step 4

• Application Version System 1.0
• Window System
• Object Text
Enter Step Parameters
• Action Substring
Parameter Area
• Result (V)First Name
• Input Text (V)Full Name

175 | P a g e
 • Starting Index 1
• Length (V)Index

24. Click - Save

25. Right click Summary Pane white space

26. New

Select

27. Process Step 5

• Application Version System 1.0
• Window System
• Object Text
• Action Replace
Parameter Area
• Input Text (V)Full Name
• Find Text (V)First Name
Enter Step Parameters • Replace
• Result (V)Last Name

176 | P a g e
28. Save
Click

29. Right click Summary Pane white space

30. New

Select

31. Process Step 6

• Application Version System 1.0
• Window System
• Object Text
• Action Trim
Parameter Area
• Value (V)Last Name
• Trim Type Trim Left
Enter Step Parameters
• Result (V)Last Name

177 | P a g e
32. Save
Click

33.
34. Go to Navigation Taskbar
35. Click Data
36. Find and Select The IWCA_PO_CreateEditAndVerify folder
37. Right click on Data Summary Pane white space
38. + New Layout

Select

39. UTL_SubstringFullName_ ExportRecorset

Input Name

40. Create dropdown

Click

41. Select From Processes

42. Select
Click

43. Find and select The IWCA_PO_CreateEditAndVerify folder

44. The UTL_SubstringFullName_ExportRecordset process
Dbl-click
in the Summary Pane

178 | P a g e
45. Right Click The Index variable
46. Delete

Select

47. Yes, on confirmation pop-up

Click

48. Click - OK
49. Recordsets tab

Click

50. Right Click White space in the Detail Pane

51. Select + New Recordset

179 | P a g e
52. Recordset Name –
UTL_SubstringFullName_ExportRecordset

Enter

53. OK
Click

54. Go to Navigation Taskbar

55. Click Processes
56. Find and select The IWCA_PO_CreateEditAndVerify folder
57. Dbl-Click The UTL_SubstringFullName_ExportRecordset process
58. The Select Layout button
Click

59. The UTL_SubstringFullName_ExportRecordset layout

Dbl-click

60. Save
Click

61. Right click Summary Pane white space

62.

Select - New

63.

180 | P a g e
 Process Step 7
• Application Version System 1.0
• Window System
• Object Recordset
• Action Write Record
Parameter Area
• Layout
UTL_SubstringFullName_ExportRecordset
Enter Step Parameters • Recordset
UTL_SubstringFullName_ExportRecordset
• Mode Append

64. Save
Click

65. Right click Summary Pane white space

66. New

Select

181 | P a g e
 Process Step 8
• Application Version System 1.0
• Window System
• Object Recordset
• Action Export Recordset
Parameter Area
• Layout
UTL_SubstringFullName_ExportRecordset
• Recordset
UTL_SubstringFullName_ExportRecordset
• File
C:\ProgramFiles(x86)\Worksoft\ExportTest
• Mode Overwrite
• Column Delimeter <COMMA>
• Include Headers Checked
• Text Qualifier <NONE>

Enter Step
Parameters

67. Save
Click

68. Run

Select

182 | P a g e
Run your UTL_SubstringFullName_ExportRecordset process and troubleshoot
any failures. Navigate to the folder specified in your file parameter on Step 8 of
your process. Verify .CSV file was exported successfully

183 | P a g e
Lesson 8 Develop Advanced Processes
Overview
In this lesson, advanced processes will be created that will edit, update, and delete existing
purchase orders in the Worksoft Web Sample Application by collecting data from the
application and using additional Certify conditional logic and verification techniques.

Objectives
After completing this lesson, the student will be able to:
• Understand conditional logic and how it can add value to your tests.
• Plan sophisticated process validation.
• Use Certify’s built-in logic tools to enhance your processes.
• Gather and store data from an application.

Advanced Processes
With processes to create, edit, and verify Purchase Orders in place, it’s time to look at how
to use the data created by those processes to validate the intended functionality of the
Worksoft Web Sample Application.
As seen up to this point, creating simple tests using specific datasets is a valid way to test
an application’s basic functionality, but there are times when something more robust is
needed; a test that can “interpret” data and act accordingly.
For example, here’s a screenshot of the Web Sample Application screen for the created
Purchase Orders.

Figure 60 – Web Sample Application screen

184 | P a g e
In the exercises prior to this one, processes were developed that created the Purchase
Orders above and provided specifics like how many Purchase Orders were created, along
with other details. The only new information generated is the Document Number and the
Amount of the Purchase Order. Developing a process to create purchase orders with known
data is easy enough. However, what if a test needs to edit an existing purchase order or
delete purchase orders using a specific criterion? In such cases, a more robust process
would need to be developed.
Here’s a brief comparison of simple, functional automated tests vs. robust, data-driven
automated tests:

Simple Functional Test Robust Data-Driven Test

Advantages Advantages
Is quicker and easier to create Creates more ‘thoughtful’ tests
Requires minimal upfront thought and
Utilizes reusable functionality
planning
Takes advantage of advanced Certify
Utilizes only basic Certify technology
technology
Faster execution Interfaces better with other tests
Meets testing and BPO requirements Requires less maintenance*
Disadvantages Meets testing and BPO requirements
Is a static, inflexible process Disadvantages
Requires more upfront thought and
Has only step reusability
planning
Every test requires complete automation Initially takes more time to automate
*More often than not
Table 8 – Simple vs. Robust Tests Comparison
When deciding which kind of automated test to develop, there’s no right or wrong choice as
both types can be used to test the functionality of any application, but it’s important to take
the time before automating any tests to determine which option makes the most sense for
your current situation.

Conditional Logic
To create a test sophisticated enough to work with unknown transactions, a process needs
to be able to analyze and make decisions depending on the test data being used. In
automation, this ability is called conditional logic. A great example and the most common
conditional logic in testing are validation steps. If the result is expected, the test passed; if
the result is not expected, the test failed.
Here are some common conditional logic methods. All of them start with checking for some
condition and then acting accordingly:
If–then-else – if the specified condition exists, do this; if not, do something else.
Compare values; if they match, do something; if they don’t match, do something
else.

185 | P a g e
 Do while – repeat processing as long as specified criteria is met. If counter < 10,
repeat processing.
Case – if the current condition is this, go to this location in the process. If Fund =
Money, jump to the “Process Money” steps.
Certify has built-in tools for adding conditional logic to your processes.
In Certify, If-then-else is primarily managed using On True/On False and Labels. Here
is an example of a Certify process using if, then else logic:

Figure 61 – If-then-else Sample Process

This process checks the SAP status bar to make sure there are no errors or warning
messages. Steps 2 – 4 check for the following message types: “S”, “E”, “W”, and “Blank”.
Depending on the message type found, Certify will Exit Process, Exit All, Jump
(Recheck/Enter), or Continue.
To see how this is done, Figure 62 below shows a screenshot of the On True / On False
tab for Step 2:

186 | P a g e
 Figure 62 – On True/On False tab
The On True section tells the process that if the desired condition (MessageType = S) is
true, pass the step and then Exit Process. The On False section tells the process that if the
desired condition is not true, then skip (don’t pass or fail) the step and continue to the next
step
Step 4 also uses the On True / On False tab. If MessageType = W, then the process
Jumps to Step 6 (Label = Enter) and proceeds through Step 7.

Figure 63 – On True/On False sample 1

Step 7 also uses the On True / On False tab. The On True section tells the process that if
the desired condition (Pressing the Enter) is true, pass the step and then Jump back to Step
1 (Label = Recheck).

187 | P a g e
 Figure 64 – On True/On False sample 2

It’s important to know all the Actions available in the On True / On False tab to make the
best use of this feature.

Figure 65 – On True/On False Actions

Some of the Actions have their own options providing even more control of your
processes:

188 | P a g e
 Figure 66 – On True/On False Actions Options

There are two other automation methods featured in our validation processes:
Initialize – set/reset a variable value to blank (text) or “0” (number). String = “”
Increment – increase (or decrease) numeric values by one or more. RowNum =
RowNum + 1
Comments – statements within a process that explain the programming but are not
part of the actual functional steps. “The following three steps create a random text
string containing the current account number.”
Below is a process that utilizes While and If, Then Else conditional logic as well as
Initialize, Increment, and Comments.

189 | P a g e
 Figure 67 – Other Automation Methods
The process in Figure 50 runs up to five times to determine if an SAP process has finished.
The process…
• Has a Comment explaining the purpose of the process (Step 1)?
• Initializes the numeric variable “Counter” (Step 2).
• Has two labels (Steps 3, 9).
• Clicks a Refresh button (Step 4) and then checks for the message “Processing
Complete”. If it finds the message, execution jumps to the label “Processing
Complete - Exit Process”. If it doesn’t find the message, execution continues (Step
5).
• Waits (stops processing) for 10 seconds (Step 6).
• Increments the variable “Counter” by 1 (Step 7).
• Checks to see if “Counter” is < or = 5 (While “Counter” is < or = 5). If it is, the
execution jumps to the label “Press Refresh”; if the counter is greater than 5, then
the execution exits the process (Step 8).

There’s no need to worry about whether a condition is While, If,

Note: Then Else, or something else. The important thing to understand is
how to create the conditional logic in Certify.

190 | P a g e
EXERCISE 8.1 — Create the WSA_PO_ExportRecordset Process
This exercise will create a utility that exports the WSA_PO_Create recordset. We will use
this data in the next process.

Steps Action Description

1. Select Processes
2. Navigate To your development folder
3. Right Click On development folder
4.
Select –
+ New Folder

5.
Enter Name –
IWCA_PO_DeleteBy
PrefixAndAmount

6. Click - OK
7. Open Notepad or Wordpad.
8. A .txt or .csv file with the name:
Create
WSA_PO_ExportRecordset
9. Save In location of your choosing
10. Close The file
11. Certify will create the file automatically if it can’t locate the
Note
file listed
12. Go To Navigation Tree
13. Click Processes
14. Find and Select IWCA_PO_DeleteByPrefixAndAmount folder
15. Right click On Processes Summary Pane white space
16.
Select –
+ New Process

17.

Enter Name –
WSA_PO_ExportRec
ordset

191 | P a g e
18.
Enter Description
Exports the
IWCA_PO_CreateEdi
tAndVerify recordset
to a .txt file.

19.
Click - Save
20. Click –
Steps Tab
21. Right click Steps Summary Pane white space
22.

Select - New

23. Process Step 1

• Application Version System 1.0
• Window System
• Object Record Set
• Action Export Recordset
Parameter Area
• Layout IWCA_PO_CreateEditAndVerify
• Recordset IWCA_PO_CreateEditAndVerify
Enter Step • File WSA_PO_ExportRecordset –
Parameters created earlier
• Mode Overwrite
• ColumnDelimeter <COMMA>
• IncludeHeaders Checked
• TextQualifier <None>

192 | P a g e
 24.
Click - Save

EXERCISE 8.2 — Create the WSA_PO_UpdateRecordset Layout

This exercise will create the WSA_PO_UpdateRecordset Layout using the file created in the
previous exercise.

Steps Action Description

1. Select Data
2. Navigate To development folder
3. Right Click On development folder
4.

Select - + New Folder

5. Name – IWCA_PO_DeleteByPrefixAndAmount

Enter

6. OK
Click
7. Go to Navigation Taskbar
8. Click Data
9. Find and Select The IWCA_PO_DeleteByPrefixAndAmount folder
10. Right click on Data Summary Pane white space

193 | P a g e
11.

Select + New Layout

12.
Input Name -
WSA_PO_UpdateRecordset

13.

Right Click
In the Variables window
white space

14. Click Add

15. The following variables to the Layout
• PO Number
• Name
• Ship to Party
• Bill to Party
• Doc Number
• Amount (Numeric)

Add

16. OK
Click
17. Click –
On the Recordsets tab

18. Right Click Recordset Detail White Space

194 | P a g e
19. + New Recordset

Select

20. Name - WSA_PO_UpdateRecordset

Enter

21. OK
Click

22. Right Click Recordset Detail White Space

23. + New Recordset

Select

24.

Enter Name
WSA_PO_UpdateRecordset
_Export

25. Click - OK
26.
Click - Save

195 | P a g e
EXERCISE 8.3 — Create the WSA_PO_UpdateRecordset Process
This exercise will show how to create a process to update an imported recordset. The Web
Sample Application does not archive created purchase orders and new purchase orders will
continually add to the PO table. Before deleting old POs, we need to export the data for
recordkeeping.
Steps Action Description
1. Select Processes
2. Navigate To IWCA_PO_DeleteByPrefixAndAmount folder
3. Right click On Processes Summary Pane white space
4. + New Process

Select

5. Name – WSA_PO_UpdateRecordset

Enter

6. Description: - Adds each purchase order’s amount to

each record imported to the WSA_PO_UpdateRecordset
process and exports the data to a new .txt file.

Enter

7.
Click - Save
8.
Click – Step Tab
9. Right click Steps Summary Pane white space
10.

Select - New

196 | P a g e
11. Process Step 1
• Application Version System 1.0
• Window System
• Object Execution
• Action Execute Process
Parameter Area
• Process WSA_PO_ExportRecordset

Enter Step Parameters

12. Right click Steps Summary Pane white space

13. New

Select

14. Process Step 2

• Application Version System 1.0
• Window System
• Object Recordset
• Action Import Recordset
Parameter Area
• Layout WSA_PO_UpdateRecordset
• Recordset WSA_PO_UpdateRecordset
• File WSA_PO_ExportRecordset –
Enter Step Parameters created earlier
• Mode Overwrite
• ColumnDelimeter <COMMA>
• IncludeHeaders Checked
• TextQualifier <None>

197 | P a g e
15. Save
Click

16. Right click Steps Summary Pane white space

17. New

Select

18. Process Step 3

• Application Version System 1.0
• Window System
• Object Recordset
• Action Read Record
Parameter Area
• Read Record From WSA_PO_UpdateRecordset
Enter Step Parameters • Recordset WSA_PO_UpdateRecordset
• Mode First
• Index 0

198 | P a g e
19. Click - Save

20. Right click Steps Summary Pane white space

21. New

Select

22. Process Step 4

• Application Version System 1.0
• Window System
• Object Execution
• Action Label
Parameter Area
• Label Name Next Document Number

Enter Step Parameters

23. Save
Click

24. Right click Steps Summary Pane white space

199 | P a g e
25.

Select - New

26. Process Step 5

• Application Version System 1.0
• Window System
• Object Recordset
• Action Read Record
Parameter Area
• Read Record From
WSA_PO_UpdateRecordset
• Recordset
WSA_PO_UpdateRecordset
• Mode Next
• Index 0

Enter Step Parameters

27.
Click - Save
28. Right click Steps Summary Pane white space
29.

Select - New

200 | P a g e
30. Process Step 6
• Application Version System 1.0
• Window System
• Object Execution
• Action Label
Parameter Area
• Label Name Find Amount

Enter Step Parameters

31. Save
Click

32. Right click Steps Summary Pane white space

33. New

Select

201 | P a g e
 Action Description
34. Process Step 7
• Application Version Common HTML 1.0
• Window WebAccountManager
• Object Action
• Action Find Row (Advanced)
Parameter Area
• Store In (V)_Row
• Column Caption 1 DocNumber
(overrides Column Nbr)
• Cell Sub-Object TagName 1 N/A
• Match Attribute 1 innerText
• Match Value 1 (V)Document
Number
• Match Criteria 1 Is Equal To

Enter Step Parameters

202 | P a g e
 Action Description
35. Save
Click

36. Right click Steps Summary Pane white space

37. New

Select

38. Process Step 8

• Application Version Common HTML 1.0
• Window WebAccountManager
• Object Action
• Action Store Cell
Parameter Area
• Store Cell Value In (V)Amount
• Row Number (V)_Row
• Column Caption
(overrides Column Number) Amount
• Store Type Cell Text

Enter Step
Parameters

203 | P a g e
 Action Description
39. Save
Click

40. Right click Steps Summary Pane white space

41. New

Select

42. Process Step 9

• Application Version System
• Window System
• Object Recordset
• Action Write Record
Parameter Area
• Layout WSA_PO_UpdateRecordset
• Recordset WSA_PO_UpdateRecordset
• Mode Append

Enter Step
Parameters

43. Save
Click

44. Right click Steps Summary Pane white space

204 | P a g e
 Action Description
45. New

Select

46. Process Step 10

• Application Version System 1.0
• Window System
• Object Execution
• Action Label
Parameter Area
• Label Name Export Recordset

Enter Step
Parameters

47. Save
Click

48. Right click Steps Summary Pane white space

49. New

Select

205 | P a g e
 Action Description
50. Process Step 11
• Application Version System 1.0
• Window System
• Object Recordset
• Action Clear Recordset
Parameter Area
• Layout WSA_PO_UpdateRecordset
• Recordset WSA_PO_UpdateRecordset

Enter Step
Parameters

51. Save
Click

52. Right click Steps Summary Pane white space

53. New

Select

206 | P a g e
 Action Description
54. Process Step 12
• Application Version System 1.0
• Window System
• Object Recordset
• Action Clear Recordset
Parameter Area
• Layout WSA_PO_UpdateRecordset
• Recordset
WSA_PO_UpdateRecordset_Export
Enter Step
Parameters

55. Select Step 3

56. On True / On False Tab
Click

57. On True parameters

• Log Status As Passed
• Actions Jump
• Target Step Find Amount

Change

207 | P a g e
 Action Description
58. On False parameters
• Log Status As Skipped
• Actions Jump
• Target Step Export Recordset

Change

59. Save
Click

60. Select Step 5

61. On False parameters
• Log Status As Skipped
• Actions Jump
• Target Step Export Recordset

Change

62. Save
Click

63. Select Step 7

208 | P a g e
 Action Description
64. On False parameters
• Log Status As Skipped
• Actions Jump
• Target Step Export Recordset

Change

65. Save
Click

66. Select Step 9

67. On True parameters
• Log Status As Passed
• Actions Jump
• Target Step Next Document Number

Change

68. Save
Click

69. Open Notepad or Wordpad.

70. A .txt or .csv file with the name:
Create
WSA_PO_UpdateRecordset_Export
71. Save In the location of your choosing
72. Close Notepad or Wordpad
73. Certify will create the file automatically if it can’t locate the
Note
file listed
74. Right Click Step 10

209 | P a g e
 Action Description
75. Insert Step Below

Select

76. Process Step 11

• Application Version System 1.0
• Window System
• Object Recordset
• Action Export Recordset
Parameter Area
• Layout WSA_PO_UpdateRecordset
• Recordset WSA_PO_UpdateRecordset_Export
• File
WSA_PO_UpdateRecordset_Exportf.csv – created earlier
• Mode Overwrite
• ColumnDelimeter <COMMA>
• IncludeHeaders Checked
• TextQualifier <None>
Enter Step
Parameters

77. Click - Save

78. Run
Click

210 | P a g e
 Before execution, verify the Worksoft Web Sample Application is
Note:
open. Open the application, if needed.

Execute your WSA_PO_UpdateRecordset process and troubleshoot any failed

steps. Open the exported files to verify the data.

EXERCISE 8.4 — Create the IWCA_PO_DeleteByAmount Process

This exercise will show you how to delete a purchase order from the WSA PO table by the
Amount criterion. As a result, the PO table will be cleared of purchase orders below $6000.

Steps Action Description

1. Go To Navigation Tree
2. Select Processes
3. Select IWCA_PO_CreateEditAndVerify folder
4. Right click On Processes Summary Pane white space
5. + New Process

Select

6. Name – IWCA_PO_DeleteByAmount

Enter

7. Description: - Identifies and deletes any purchase order

with an amount less than $6000. This will limit purchase
orders in the WSA PO table

Enter

8. Save
Click

9. Steps Tab
Click

10. Right click Steps Summary Pane white space

211 | P a g e
11. New

Select

12. Process Step 1

• Application Version System 1.0
• Window System
• Object Number
• Action Set
Parameter Area
• To the Value 1
• Variable (V)_Counter
Enter Step
Parameters

13. Save
Click

14. Steps Tab

Click

15. Right click Steps Summary Pane white space

16. New

Select

212 | P a g e
17. Process Step 2
• Application Version System 1.0
• Window System
• Object Execution
• Action Label
Parameter Area
• Label Name Search Next Row
Enter Step
Parameters

18. Save
Click

19. Steps Tab

Click

20. Right click Steps Summary Pane white space

21. New

Select

22. Process Step 3

• Application Version Common HTML 1.0
• Window WebAccountManager
• Object Action
• Action Find Row (Advanced)
Parameter Area
• Store Found Row Number In (V)_Row
Enter Step
• Matching Row Instance (V)_Counter
Parameters
• Column Caption 1 PONumber
(overrides Column Number)
• Cell Sub-Object TagName 1 N/A
• Match Attribute 1 innerText
• Match Value 1 8403
• Match Criteria 1 Starts With

213 | P a g e
23. Save
Click

24. Steps Tab

Click

25. Right click Steps Summary Pane white space

26. New

Select

214 | P a g e
27. Process Step 4
• Application Version Common HTML 1.0
• Window WebAccountManager
• Object Action
• Action Store Cell
Parameter Area
• Store Cell Value In (V)Amount_Numeric
• Row Number (V)_Row
• Column Caption 1 Amount
(overrides Column Number)
• Store Type Cell Text

Enter Step
Parameters

28. Save
Click

29. Steps Tab

Click

30. Right click Steps Summary Pane white space

215 | P a g e
31. New

Select

32. Process Step 5

• Application Version System 1.0
• Window System
• Object Number
• Action Compare
Parameter Area
• Value 1 (V)Amount_Numeric
• Criteria (V)_Row
• Value 2 6000

Enter Step
Parameters

33. Save
Click

34. Steps Tab

Click

35. Right click Steps Summary Pane white space

216 | P a g e
36. New

Select

37. Process Step 6

• Application Version Common HTML 1.0
• Window WebAccountManager
• Object Action
• Action Select Cell
Parameter Area
Enter Step • Row Number (V)_Row
Parameters • Column Caption Action
(overrides Column Number)
• Click Type Single
• Horizontal % (Default=50) 30
• Vertical % (Default=50) 50
• Follow-up Keystroke None

217 | P a g e
38. Save
Click

39. Steps Tab

Click

40. Right click Steps Summary Pane white space

41.

Select - New

218 | P a g e
42. Process Step 7
• Application Version Common HTML 1.0
• Window WebAccountManager
• Object Status Message
• Action Verify
Parameter Area
• Value An Item is Deleted
• Criteria Is Equal To
Enter Step
Parameters

43. Save
Click

44. Steps Tab

Click

45. Right click Steps Summary Pane white space

46. New

Select

219 | P a g e
47. Process Step 8
• Application Version System 1.0
• Window System
• Object Operating System
• Action Capture Screen Image
Parameter Area
• Capture Screen Type Desktop
Enter Step
Parameters

48. Save
Click

49. Steps Tab

Click

50. Right click Steps Summary Pane white space

51. New

Select

52. Process Step 9

• Application Version System 1.0
• Window System
• Object Execution
• Action Label
Parameter Area
• Label Name Greater Amount
Enter Step
Parameters

220 | P a g e
53. Save
Click

54. Steps Tab

Click

55. Right click Steps Summary Pane white space

56. New

Select

Process Step 1
• Application Version System 1.0
• Window System
• Object Number
• Action Math
Parameter Area
• Value1 (V)_Counter
• Operation Add
• Value2 1
• Result (V)_Counter

Enter Step
Parameters

Select Step 3
On True parameters
• Log Status As Passed
Change
• Actions Continue
On False parameters

221 | P a g e
 • Log Status As Skipped
• Action Exit Process

Save
Click

Select Step 5
On True parameters
• Log Status As Passed
• Actions Jump
• Target Step Greater Amount
On False parameters
• Log Status As Skipped
• Action Continue

Change

Save
Click

Select Step 8
On True parameters
• Log Status As Passed
• Actions Jump
• Target Step Search Next Row
Change
On False parameters
• Log Status As Failed
• Action Continue

222 | P a g e
 Save
Click

Select Step 10
On True parameters
• Log Status As Passed
• Actions Jump
• Target Step Search Next Row
On False parameters
• Log Status As Failed
• Action Continue

Change

Save
Click

Run the process step-by-step to see the decision points and troubleshoot any failures.

223 | P a g e
EXERCISE 8.5 — Create the IWCA_PO_DeleteAll Process
This exercise will show how to delete all purchase orders from the WSA PO. The static value
used in the PO Number concatenation step will be used to identify the purchase order
record for deletion.

Step Action Description

1. Go To Navigation Tree
2. Select Processes
3. Select IWCA_PO_DeleteByPrefixAndAmount folder
4. Right click On Processes Summary Pane white space
5. + New Process

Select

6. Name – IWCA_PO_DeleteAll

Enter

7. Description: - Identifies and deletes all purchase orders in

the PO table.

Enter

8. Save
Click

9. Steps Tab
Click

10. Right click Steps Summary Pane white space

224 | P a g e
11.

Select - New

12. Process Step 1

• Application Version System 1.0
• Window System
• Object Number
• Action Set
Parameter Area
• To the Value 2
• Variable (V)_Row

Enter Step Parameters

13. Save
Click

14. Steps Tab

Click

15. Right click Steps Summary Pane white space

16. New

Select

225 | P a g e
17. Process Step 2
• Application Version System 1.0
• Window System
• Object Execution
• Action Label
Parameter Area
• Label Name Loop
Enter Step
Parameters

18. Save
Click

19. Steps Tab

Click

20. Right click Steps Summary Pane white space

21.

Select - New

22. Process Step 3

• Application Version Common HTML 1.0
• Window WebAccountManager
• Object Action
Enter Step
• Action Select Row
Parameters
Parameter Area
• Row Number (V)_Row
• Click Type Single

226 | P a g e
23. Save
Click

24. Steps Tab

Click

25. Right click Steps Summary Pane white space

26. New

Select

27. Process Step 4

• Application Version Common HTML 1.0
• Window WebAccountManager
• Object Action
• Action Verify Cell
Parameter Area
• Row Number (V)_Row
Enter Step • Column Caption PONumber
Parameters (overrides Column Number)
• Verify Type Cell Text
• Criteria Starts With
• Value {STATIC VALUE used in PO
Number concatenate step}

227 | P a g e
28. Save
Click

29. Steps Tab

Click

30. Right click Steps Summary Pane white space

31. New

Select

32. Process Step 5

• Application Version System 1.0
• Window System
• Object Number
• Action Math
Enter Step
Parameter Area
Parameters
• Value 1 (V)_Row
• Operation Add
• Value 2 1
• Result (V)_Row

228 | P a g e
33. Save
Click

34. Steps Tab

Click

35. Right click Steps Summary Pane white space

36. New

Select

37. Process Step 6

• Application Version System 1.0
• Window System
• Object Execution
• Action Jump
Parameter Area
Enter Step • Start at Step Loop
Parameters

38. Save
Click

39. Click Steps Tab

229 | P a g e
40. Right click Steps Summary Pane white space
41. New

Select

42. Process Step 7

• Application Version System 1.0
• Window System
• Object Execution
• Action Label
Parameter Area
• Label Name Delete this one
Enter Step
Parameters

43. Click - Save

44. Steps Tab

Click

45. Right click Steps Summary Pane white space

46. New

Select

230 | P a g e
47. Process Step 8
• Application Version Common HTML 1.0
• Window WebAccountManager
• Object Action
• Action Select Cell
Parameter Area
• Row Number (V)_Row
• Column Caption Action
(overrides Column Number)
• Click Type Single

Enter Step
Parameters

48. Click - Save

49. Steps Tab

Click

50. Right click Steps Summary Pane white space

51. New

Select

231 | P a g e
52. Process Step 9
• Application Version System 1.0
• Window System
• Object Execution
• Action Jump
Parameter Area
• Start at step Loop
Enter Step
Parameters

53. Click - Save

54. Modifying the True/False of Step 3 exits the process execution

NOTE when there are no more purchase orders in the PO table for
deletion.
55. Select Step 3
56. On True parameters
• Log Status As Passed
• Actions Continue
On False parameters
• Log Status As Skipped
• Action Exit Process

Change

57.
Click Save
58. Modifying the True/False of Step 4 skips the step and jumps to
NOTE
the label “Delete this one” to delete the purchase order.
59. Select Step 4

232 | P a g e
60. On True parameters
• Log Status As Skipped
• Actions Jump
• Target Step Delete this one
On False parameters
• Log Status As Passed
• Action Continue

Change

61. Click - Save

Modifying the True/False of Step 8 skips the step and jumps to

NOTE
the first step in the process to continue execution.
62. Select Step 8
63. On True parameters
• Log Status As Skipped
• Actions Jump
• Target Step First Step
On False parameters
• Log Status As Passed
• Action Continue

Change

233 | P a g e
 64.
Click - Save

Run the process step-by-step to see the decision points and troubleshoot any failures.
Save

Create an Integrated Process

In previous exercises, individual processes were created. These processes will be combined
into an Integrated Process. An Integrated or Cross Functional Process contains
System steps that execute sub-processes (functional processes).

EXERCISE 8.6 — Create and Execute the

IWCA_PO_DeleteByPrefixAndAmount Process
In this exercise, you will create and execute an integrated process.

Critical Business Process Sub-Processes

WSA_PO_ExportRecordset
WSA_PO_UpdateRecordset
IWCA_PO_DeleteByPrefixAndAmount
IWCA_PO_DeleteByAmount
IWCA_PO_DeleteAll

Steps Action Description

1. Go To Navigation Tree
2. Select Processes
3. Select IWCA_PO_DeleteByPrefixAndAmount folder
4. Right click On Processes Summary Pane white space
5. + New Process

Select

6. Name – IWCA_PO_DeleteByPrefixAndAmount

Enter

234 | P a g e
Steps Action Description
7. Description: - This is the integrated process.

Enter

8. Save
Click

9. Steps Tab
Click

10. Right click Steps Summary Pane white space

11. New

Select

12. Process Step 1

• Application Version System 1.0
• Window System
• Object Execution
• Action Execute Process
Parameter Area
• Process UTL_LaunchWSA
Enter Step
Parameters

13. Click - Save

235 | P a g e
14. Steps Tab
Click

15. Right click Steps Summary Pane white space

16. New

Select

17. Process Step 2

• Application Version System 1.0
• Window System
• Object Execution
• Action Execute Process
Parameter Area
Enter Step • Process WSA_PO_ExportRecordset
Parameters

18. Save
Click

19. Steps Tab

Click

20. Right click Steps Summary Pane white space

21. New

Select

236 | P a g e
22. Process Step 3
• Application Version System 1.0
• Window System
• Object Execution
• Action Execute Process
Parameter Area
• Process WSA_PO_UpdateRecordset
Enter Step
Parameters

23. Save
Click

24. Steps Tab

Click

25. Right click Steps Summary Pane white space

26. New

Select

237 | P a g e
27. Process Step 4
• Application Version System 1.0
• Window System
• Object Execution
• Action Execute Process
Parameter Area
• Process WSA_PO_DeleteByAmount
Enter Step
Parameters

28. Save
Click

29. Steps Tab

Click

30. Right click Steps Summary Pane white space

31. New

Select

32. Process Step 5

• Application Version System 1.0
• Window System
• Object Execution
• Action Execute Process
Parameter Area
Enter Step • Process WSA_PO_DeleteAll
Parameters

238 | P a g e
 33. Save
Click

34. Steps Tab

Click

35. Right click Steps Summary Pane white space

36. New

Select

37. Process Step 6

• Application Version System 1.0
• Window System
• Object Execution
• Action Execute Process
Parameter Area
Enter Step • Process UTL_CloseWSA
Parameters

38.
Click- Save

Execute your IWCA_PO_DeleteByPrefixAndAmount integrated process and troubleshoot for

any failures.

239 | P a g e
Lesson Summary
The Develop Advanced Processes lesson is now complete.
Key points to remember:
• Using conditional logic in automated processes allows the creation of sophisticated
tests that can handle intensive business processes and broad datasets.
• Key conditional logic techniques in Certify include:
• Identifying and comparing objects
• The use of labels and jumps
• On True, On False functionality/options

240 | P a g e
Lesson 9 - Resources

Overview
This section identifies useful resources for working with Worksoft Certify and contacting
Worksoft.

Worksoft Certify Resources

Access Worksoft Certify Help
If you need additional information on the features in Worksoft Certify, press F1 or click
Help in the menu bar.

Certify Log File

Certify Log files contain information both on normal operation of Certify and any errors.
There is a general log file and log files for specific interfaces.
In the Certify Help menu, click Help > Show Log
elect either “Show Certify Log File” or “Show Certify Log Folder”

241 | P a g e
Certify Diagnostic Tool
The Certify Diagnostic Tool helps you diagnose issues that you encounter when using
Certify by creating a report about a specific interface.
In the Certify Help menu, click Help > Diagnostics
Select either “All Diagnostics” or a specific Interface such as SAP.
Output can be saved in a file and e-mailed to Support as needed.

242 | P a g e
Worksoft Community and Customer Solutions Site
The Worksoft Community site provides the ability to:
• Discuss and learn about Worksoft products.
• View Worksoft published media.
• Download Worksoft product updates.
• View a knowledge base for Worksoft products.
• Submit a case.
• View answers to frequently asked questions.
• Find support-related solutions.
To utilize the Worksoft Community and Customer Solutions site, you must register:
http://portal.worksoft.com
To request a Portal account login, send an email to [email protected] and include the
following information in your email: full name, email address, department/company (and
Client Name if you are a Worksoft partner), job title, phone number, and address (if
different from your company’s main address).

243 | P a g e
Worksoft Help Portal
The Worksoft Help Portal page provides:
• The latest product documentation for Worksoft products and solutions.
• Helps you “Get Started”.
• Provides product and solution “How To” instructions.
To utilize the Worksoft Help Portal, log on to the site: http://docs.worksoft.com/
Anyone at your company can have access to this site.

244 | P a g e
Additional Online Resources
• Worksoft University
• Business Process Testing video
• Worksoft Analyze videos
• Case Studies
• Worksoft Certification

245 | P a g e
Appendix

Job Aids
Overview
This section provides useful job aids for common Certify tasks.
Techniques Used to Define Processes

To create a process:
1. From the Processes window, in the Navigation Tree, click the 02.04 Development
folder, and then click your name.
2. Click the desired process folder.
3. Right-click in the Summary Pane and select New Process.
4. In the Process Details tab section, in the Name field, type in the name of the
process.
5. In the Description field, type in the description.
6. Press the Save button.
7. Click the Steps tab.

To use LiveTouch to replace the current step:

1. Verify that the application is open to the screen you wish to learn.
2. Right-click in the Steps area and select New.
3. Click the Application Version drop-down arrow.
4. Choose Select Using LiveTouch.
5. In the application, select the object field.
6. In the Certify LiveTouch dialog box, click Save & Close.
7. To Execute the step, right-click the step and select Execute Step.

To use LiveTouch to insert one or many steps:

1. In Certify, in the Steps area, right-click on Step you want to insert after.
2. Select Insert Step Below Using LiveTouch.
3. In the application, select the objects by clicking in the object fields.
4. In the Certify LiveTouch dialog box, click Save & Close.
5. The Certify Process and Data Editor appears.

246 | P a g e
 6. In Certify, in the Parameters tab, enter any parameters.
7. Click the Save button.
8. Once all steps are entered, click the Save button.
9. Click the “X” in the top right corner to exit the Process Editor.

To execute the entire process:

1. In the Summary Pane, right-click the process, and select Run.
2. The Configuration dialog box appears.
3. Click Start.
4. The Execution dialog box appears.
5. Click Run.
6. The process executes and upon completion, the Result Viewer appears.
7. When finished reviewing the results, click the “X” in the top right corner to close the
Result Viewer.

Start a New Integrated Process

1. Create a folder to hold all the processes associated with the integrated process.
2. Create a top-level process in the folder.
3. Create child processes by:
4. Using Capture Process to create the entire process.
5. Using “New Process” or Execute Process then use Insert with LiveTouch or Insert
with Capture.
6. If you haven’t already done so – link your child processes to your top-level process.
7. Add a call to a utility like UTL_Login to the top of your process to login to your
application.
8. Create Layout/Recordsets for each process using “Add to Layout” or one of the other
Layout techniques.
9. Make sure that you have replaced any data with variables and put the variables in a
layout or recordset.

Create a Layout Manually

Creating a layout manually involves adding existing or creating new variables for the layout.
One reason for creating layouts manually is to test a specific area of your application. For
example, the Worksoft Sample Application has seven input fields including PO Number,
Name, Ship to, Bill to, Material, Quantity, Price. You want to test only three input fields
(Name, Ship to, Bill to) to ensure the information you are collecting is valid or invalid. In
this case, you may want to create a layout with these three fields only and create a process

247 | P a g e
that only tests Name, Ship to, and Bill to. One option is to create the layout manually and
use the add capability to select the variables.

1. In the Navigation taskbar, click Data.

2. The Data window appears.
3. In the Navigation tree, select your Development folder, and then select your
IWCA_PO_ CreateEditAndVerify folder.
4. Right-click in the Summary pane and select New Layout.
5. The New Layout dialog box appears.
6. In the Name field, type WSA_VariableTest.
7. Right-click in the Variables Pane and select Add.
8. Select the Name variable.
9. Click OK.
10. Right-click in the Variables Pane and select Add.
11. Select the Ship to variable.
12. Click OK.
13. Right-click in the Variables Pane and select Add.
14. Select the Bill to variable.
15. Click OK.
16. Click OK to save the new layout and close the New Layout dialog box

Create a Layout Using Processes

Creating layouts using processes involves selecting one or more processes from the Select
Process dialog box. The layout is generated based on the variables used in the selected
processes. In this exercise, you will create a layout called IWCA_
PO_DeleteByPrefixAndAmount by selecting the IWCA_PO_DeleteByPrefixAndAmount end-
to-end process. All the variables used in this process and child processes are added to the
layout. **Note: You will need to complete Lesson 7:
Develop Advanced Processes to complete this exercise.

1. In the Navigation Taskbar, click Data.

2. In the Navigation Tree, navigate to your IWCA_PO_DeleteByPrefixAndAmount
folder.
3. Right-click in the Summary Pane and select New Layout. The New Layout dialog
box appears.

248 | P a g e
 4. In the New Layout dialog box, type in field values or select options as follows:

Field/Option Value/Action
Name IWCA_PO_DeleteByPrefixAndAmount
Create From Processes and Child Processes
Child Process Depth 1

5. Click the Select button. The Select Process dialog box appears.
6. In the Navigation Tree, click your IWCA_PO_DeleteByPrefixAndAmount folder.
7. In the Summary Pane, select the IWCA_PO_DeleteByPrefixAndAmount process.
8. The process is highlighted in the Summary Pane.
9. Click OK.
10. The Select Process dialog box closes and all variables that were used in the
IWCA_PO_
11. DeleteByPrefixAndAmount process and child processes are placed in the Variables
pane in the New Layout dialog box.
12. Right-click the _Row variable and delete. You do not need this variable.
13. Click OK to save the new layout and close the New Layout dialog box.

Create a Recordset
With the IWCA_PO_DeleteByPrefixAndAmount layout defined, you are now ready to create
a recordset. In this exercise, you will select the IWCA_PO_DeleteByPrefixAndAmount layout,
create a recordset called IWCA_PO_ DeleteByPrefixAndAmount, and add two rows of data
1. If you are continuing directly from the previous Job Aid, you can skip to step 4.
2. In the Navigation Taskbar, click Data.
3. In the Navigation Tree, navigate to your IWCA_PO_DeleteByPrefixAndAmount
folder.
4. In the Summary Pane, select the IWCA_PO_DeleteByPrefixAndAmount layout.
5. In the Detail Pane, click the Recordset tab.
6. Right-click in the Recordsets tab.
7. A shortcut menu appears.
8. Select New Recordset.
9. The Recordset Editor dialog box appears.
10. In the New Recordset dialog box, type in field values as follows:

249 | P a g e
 Field Value
Name IWCA_PO_DeleteByPrefixAndAmount
Description Recordset to retain data after execution
11. Enter the data as shown in the following screenshot:

12. Click OK to save the recordset and close the Recordset Editor.

Add Layouts and Recordsets to an Existing Process

After defining a layout and recordset, you can attach them to processes or process steps in
the Process Editor. Each process can have one layout and recordset attached. Attaching
recordsets is done by selecting a layout, a recordset, and the mode of operation. The level
at which you attach the layout determines whether a loop will occur, and the mode
determines how it will be executed. For example, if a recordset is attached to a process in
Read mode, then the process will loop once for each row of data values. In this exercise,
you will apply the layout and recordset created in the previous Job Aids to the
IWCA_PO_DeleteByPrefixAndAmount process.

1. In the Navigation taskbar, click Processes.

2. The Processes window appears.
3. In the Navigation Tree, expand Your Development Folder.
4. Select your IWCA_PO_DeleteByPrefixAndAmount folder.
5. In the Summary Pane, right-click the IWCA_PO_DeleteByPrefixAndAmount
process and select Edit.
6. On the right side of the screen, in the Layout field, click the Select Layout button.
7. The Select Layout dialog box appears.
8. In the Summary Pane, select IWCA_PO_DeleteByPrefixAndAmount layout.
9. Click OK.
10. On the right side of the screen, in the RecordSet Name field, verify IWCA_PO_
11. DeleteByPrefixAndAmount is selected.
12. On the right side of the screen, in the RecordSet Mode field, verify that Read and
Update is selected. This will read the Name field and update the other variables
after execution.

250 | P a g e
13. Click the Save button.
14. Click the Close button to exit the Process Editor.

251 | P a g e
Course Evaluation

At Worksoft, Inc. we continually strive to improve the quality of our training programs and
documentation. Your feedback is important in helping us to provide the best possible
training experience for our clients. Please take a moment to complete this course
evaluation.

Company:

Course Name: ___________________________________________________________

Your Job Role: ___________________________________________________________

Date Attended: __________________________ Instructor: ___________________

About the Course

How would you rate the class?
Circle one
Excellent Satisfactory Fair Poor

How would you rate the course format?

Circle one
Excellent Satisfactory Fair Poor

How would you rate the instructor?

Circle one
Excellent Satisfactory Fair Poor

How would you rate the training materials?

Circle one
Excellent Satisfactory Fair Poor

How would you rate the pace of the course?

Circle one
Just Right Reasonable Too Slow Too Fast

Overall, what percentage of the covered material was completely new to you?
Circle one
0 to 25% 0 to 25% up to 75% ALL

Do you feel that you are now adequately prepared to implement and/or use Certify?
Circle One
Yes No

252 | P a g e
List any questions that require follow-up.

What did you like most and/or least about the course?

Would you prefer to

more hands-on time or more lecture time? Why?

Are there any topics covered that you would have liked to spend more time on?

Are there any topics not covered that you would like to know more about?

Would you recommend this course to others? If not, why not?

About the Instructor

Did the instructor demonstrate excellent technical expertise on the product?
Circle One
Yes No
Did the instructor demonstrate industry knowledge and provided adequate explanations?
Circle One
Good Average Poor
Did the instructor present the material and answer questions clearly?
Circle One
Good Average Poor
Was the instructor well-prepared?
Yes No

253 | P a g e
 Yes No

Circle One
Yes No

About the Materials

Is the training guide comprehensive for the course?

Circle One
Yes No

Will you use the training guide as a reference after the class?
Circle One
Yes No

Additional Comments or suggestions

254 | P a g e
Worksoft, Inc.
Worksoft Inc.
15851 N. Dallas Parkway, Suite 855
15851 N. Dallas Parkway, Suite 855
Addison, TX 75001
Addison, TX 75001
www.worksoft.com

www.worksoft.com

255 | P a g e