testbench pc manual

TestBench PC Products

User’s Guide

TestBench-PC

User’s Guide September 2007

Copyright 2007 The Original Software Group Limited. The information in this document is subject to change without notice. No part of this document may be reproduced or transmitted in any form without the express written permission of The Original Software Group Ltd. IBM is a registered trademark of the IBM Corporation. Microsoft is a registered trademark of the Microsoft Corporation. The Original Software Group Limited makes no warranties, express or implied including without limitation the implied warranties of merchantability and fitness for a particular purpose regarding TestBench, this document or any Original Software Group products.

Table of Contents 1 TESTPLAN ........................................................................................ 1-1

INTRODUCTION .............................................................................. 1-1 GETTING STARTED ........................................................................ 1-2 TESTPLAN VERSIONS.................................................................... 1-4

TestPlan User.................................................................................. 1-4 TestPlan Administrator................................................................... 1-4

TESTPLAN MAIN PANEL OPTIONS............................................. 1-5 File .................................................................................................. 1-6 Help................................................................................................. 1-7 Toolbar Options .............................................................................. 1-7

ADMIN OPTIONS............................................................................. 1-8 Menu Options ............................................................................... 1-10 Edit Resource................................................................................ 1-10 Edit Plan........................................................................................ 1-13 Copy Plan Wizard......................................................................... 1-14 Defect Priority............................................................................... 1-18 Defect Status ................................................................................. 1-19 Task Status.................................................................................... 1-20 Data Sources ................................................................................. 1-21 Task and Defect User Fields......................................................... 1-22

MAIN TOOLBAR............................................................................ 1-24 Search............................................................................................ 1-24 How to Navigate once results are found....................................... 1-29 Open/New Plan ............................................................................. 1-29 Open Existing Plan ....................................................................... 1-30 Create New Plan ........................................................................... 1-31

TESTPLAN MAIN PANEL............................................................. 1-33 Main Panel View .......................................................................... 1-33 Folders .......................................................................................... 1-35 Tasks ............................................................................................. 1-39 Add/Edit Task ............................................................................... 1-42 Task Details .................................................................................. 1-42 User Fields .................................................................................... 1-44 History .......................................................................................... 1-45 Steps.............................................................................................. 1-47 Results........................................................................................... 1-50 PC Files......................................................................................... 1-53 TestBench Components ................................................................ 1-55

DEFECT PANE................................................................................ 1-59 Add/Edit Defect ............................................................................ 1-61

REPORTING .................................................................................... 1-65 Reporting Window........................................................................ 1-65 Reporting Options......................................................................... 1-65

DEFECT CHART............................................................................. 1-69 Statistics ........................................................................................ 1-70

MILESTONES.................................................................................. 1-71 Using Milestones .......................................................................... 1-71 Amend Milestone.......................................................................... 1-72

FILTERS........................................................................................... 1-73 Using Filters.................................................................................. 1-73 Activate ......................................................................................... 1-74 Edit................................................................................................ 1-74

VIEW OPTIONS .............................................................................. 1-75 Enabling View Options................................................................. 1-75

USER TASKS................................................................................... 1-79

2 TESTBENCH-PC .............................................................................. 2-1

INTRODUCTION .............................................................................. 2-1 System Requirements ..................................................................... 2-1 Getting Started ................................................................................ 2-2 Product Registration ....................................................................... 2-3

TESTBENCH-PC PANEL ................................................................. 2-6 Menu ............................................................................................... 2-6 Toolbar............................................................................................ 2-7 Search.............................................................................................. 2-8 Home Tab ....................................................................................... 2-9

MAIN PANEL.................................................................................. 2-10 Main Panel – Database View........................................................ 2-11 Main Panel – Project View........................................................... 2-12 Main Panel – Test Case View....................................................... 2-14 Test Case Maintenance ................................................................. 2-16 Main Panel – Action Maps View ................................................. 2-18 Main Panel – Variable Data View................................................ 2-19 Main Panel – Script View............................................................. 2-20

VARIABLE DATA SETS................................................................ 2-22 Edit Variable Data ........................................................................ 2-22 Column Options............................................................................ 2-23 Row Options ................................................................................. 2-23 Data Options ................................................................................. 2-25 Edit Column Details ..................................................................... 2-26

DATA RULES.................................................................................. 2-29 How Data Rules Work.................................................................. 2-29 When is a Data Rule Checked? .................................................... 2-30

Data Rule Maintenance................................................................. 2-30 TEST ENVIRONMENTS ................................................................ 2-35

How to Set Up and Use Test Environments ................................. 2-35 Database View .............................................................................. 2-36 Test Environment View................................................................ 2-37 Test Environment Maintenance.................................................... 2-38 Checkpoints .................................................................................. 2-39

LAUNCH FILES .............................................................................. 2-42 Maintenance.................................................................................. 2-42 Execution ...................................................................................... 2-47 Results........................................................................................... 2-47

TEST CASE RESULTS ................................................................... 2-49 Result options ............................................................................... 2-50 General points for run results detail screens................................. 2-52 Summary....................................................................................... 2-52 Warnings....................................................................................... 2-53 Timeline ........................................................................................ 2-54 Screens .......................................................................................... 2-55 Database........................................................................................ 2-56 Data Rules..................................................................................... 2-57 Server ............................................................................................ 2-58 Log ................................................................................................ 2-59 Response ....................................................................................... 2-60 Pass/Fail ........................................................................................ 2-61

ACTION MAP RESULTS ............................................................... 2-63 Map Entries................................................................................... 2-64 Result options ............................................................................... 2-64

REPORTING .................................................................................... 2-66 DATA CASES.................................................................................. 2-70

Introduction................................................................................... 2-71 Data Case Panel ............................................................................ 2-72 Source Credentials ........................................................................ 2-74 Clone Schema ............................................................................... 2-76 Relationships................................................................................. 2-79 Data Selections ............................................................................. 2-83 Custom Queries ............................................................................ 2-85 Executing a Data Case .................................................................. 2-88 Data Case Results ......................................................................... 2-89

NOTES.............................................................................................. 2-93 Instructions for using Notes.......................................................... 2-94

3 TESTDRIVE-GREEN....................................................................... 3-1

INTRODUCTION .............................................................................. 3-1

System Requirements ..................................................................... 3-2 Are there other products like TestDrive-Green? ............................ 3-2 Is TestDrive-Green a scripting tool? .............................................. 3-2 TestDrive-Green versus ‘Native’ Record and Playback ................ 3-3 Getting Started ................................................................................ 3-3

THE MAIN PANEL ........................................................................... 3-4 Product Options .............................................................................. 3-7

RECORDING ................................................................................... 3-14 Prerequisites.................................................................................. 3-14 Instructions.................................................................................... 3-14

SCRIPT STRUCTURE .................................................................... 3-16 Layout Options ............................................................................. 3-16 Screens .......................................................................................... 3-19 Fields............................................................................................. 3-21 Input .............................................................................................. 3-22 Variable Data ................................................................................ 3-24 Tracked Fields............................................................................... 3-25 Thumbnails ................................................................................... 3-26 Field Properties ............................................................................. 3-29

SCREEN OPTIONS ......................................................................... 3-34 General Options ............................................................................ 3-34 Column Input ................................................................................ 3-38

SCRIPT OPTIONS........................................................................... 3-41 Exceptions..................................................................................... 3-46

AMENDING SCRIPTS.................................................................... 3-49 Deleting a Screen .......................................................................... 3-50 Inserting a Screen ......................................................................... 3-50 Screen Replacement...................................................................... 3-51 Manual Mapping........................................................................... 3-53 Script Verification ........................................................................ 3-54

MATCH RULES .............................................................................. 3-57 Label ............................................................................................. 3-58 Labels and Matching in Subfiles .................................................. 3-59

PLAYBACK..................................................................................... 3-61 Prerequisites.................................................................................. 3-61 Instructions.................................................................................... 3-61 PowerPLAY.................................................................................. 3-63 Test Items...................................................................................... 3-64

RESULTS ......................................................................................... 3-65 Expected/Actual Screen Images ................................................... 3-68 Field Lists (Errors/Actuals/Expected) .......................................... 3-69 Pass/Fail Results ........................................................................... 3-70

VARIABLE DATA .......................................................................... 3-71

Access Variable Data.................................................................... 3-71 Edit Variable Data ........................................................................ 3-73 Column Options............................................................................ 3-74 Row Options ................................................................................. 3-76 Data Options ................................................................................. 3-77 Edit Column Details ..................................................................... 3-78 Playback........................................................................................ 3-80

TRACKED FIELDS......................................................................... 3-81 Edit Tracked Fields....................................................................... 3-82

SCRIPT SECURITY ........................................................................ 3-83

4 TESTDRIVE-GOLD ......................................................................... 4-1

INTRODUCTION .............................................................................. 4-1 Platforms......................................................................................... 4-2 Browser Requirements.................................................................... 4-2 System Requirements ..................................................................... 4-2 Getting Started ................................................................................ 4-2

THE MAIN PANEL ........................................................................... 4-3 Edit User Preferences ..................................................................... 4-6

OPTIONS............................................................................................ 4-9 General............................................................................................ 4-9 General Tab................................................................................... 4-10 Web and GUI Tab......................................................................... 4-11 5250 Tab ....................................................................................... 4-28 Screen Analysis............................................................................. 4-29 Class Rules.................................................................................... 4-30 Messages....................................................................................... 4-35 Validation Rules ........................................................................... 4-36 Validation Functions..................................................................... 4-37 Custom Functions ......................................................................... 4-39 SQL Functions .............................................................................. 4-40

RECORDING ................................................................................... 4-46 Instructions.................................................................................... 4-46 Drag and Drop .............................................................................. 4-50

SCRIPT STRUCTURE .................................................................... 4-51 Layout Options ............................................................................. 4-51 Script ............................................................................................. 4-52 Picture ........................................................................................... 4-54 Markups ........................................................................................ 4-56 Contents ........................................................................................ 4-57 Expected Element Properties........................................................ 4-59 Edit Element ................................................................................. 4-60 Expected Input Properties............................................................. 4-63

Edit Input ...................................................................................... 4-65 Summary....................................................................................... 4-69 Tracked Fields............................................................................... 4-70 Variable Data ................................................................................ 4-71 Validation Rules ........................................................................... 4-72 Blocks ........................................................................................... 4-75 Screen Properties .......................................................................... 4-80

SCRIPT OPTIONS........................................................................... 4-81 Exceptions..................................................................................... 4-83 Options.......................................................................................... 4-84

PLAYBACK..................................................................................... 4-85 Instructions.................................................................................... 4-85

RESULTS ......................................................................................... 4-88 Markups ........................................................................................ 4-91 Pass/Fail Results ........................................................................... 4-92

AMENDING SCRIPTS.................................................................... 4-93 Deleting a Screen .......................................................................... 4-93 Inserting a Screen ......................................................................... 4-94 Script Verification ........................................................................ 4-95 Verification Options ..................................................................... 4-95 Notification ................................................................................... 4-97 Verification Checkpoints ............................................................ 4-102

VARIABLE DATA ........................................................................ 4-103 Access Variable Data.................................................................. 4-104 Edit Variable Data ...................................................................... 4-106 Column Options.......................................................................... 4-107 Row Options ............................................................................... 4-108 Data Options ............................................................................... 4-109 Edit Column Details ................................................................... 4-110 Variable Block Selection ............................................................ 4-112 Playback...................................................................................... 4-114

TRACKED FIELDS....................................................................... 4-115 Edit Tracked Fields..................................................................... 4-116

TESTBENCH INTEGRATION ..................................................... 4-117 JWalk .......................................................................................... 4-117

HOW TO CREATE A NEW TEST CASE.................................... 4-119 TEST RUN RESULTS ................................................................... 4-120 TEST REPORTING ....................................................................... 4-120 SCRIPT SECURITY ...................................................................... 4-121 TROUBLESHOOTING ................................................................. 4-122

Recording Issues ......................................................................... 4-122 Playback Issues ........................................................................... 4-122 Saving Scripts Locally................................................................ 4-123

5 ACTION MAPS ................................................................................. 5-1

INTRODUCTION .............................................................................. 5-1 Getting Started ................................................................................ 5-1

ACTION MAP PANEL...................................................................... 5-3 Toolbar Buttons .............................................................................. 5-3 Menu Options ................................................................................. 5-4 Right-click Options......................................................................... 5-6

ACTION MAP MAINTENANCE ..................................................... 5-9 Adding Components ....................................................................... 5-9 Set Checkpoint / Rollback ............................................................ 5-11 Adding Branches .......................................................................... 5-13 Evaluating Branches ..................................................................... 5-15 Action Properties .......................................................................... 5-16

OPTIONS.......................................................................................... 5-20 ACTION MAP CONTROL.............................................................. 5-22

General.......................................................................................... 5-22 Advanced ...................................................................................... 5-26 Variable Data ................................................................................ 5-27 Properties ...................................................................................... 5-30

ACTION MAP PLAYBACK........................................................... 5-31 Tracked Fields............................................................................... 5-34

RESULTS ......................................................................................... 5-35 Map Entries................................................................................... 5-37 Result Options .............................................................................. 5-38

6 MANUAL TESTING......................................................................... 6-1

INTRODUCTION .............................................................................. 6-1 GETTING STARTED ........................................................................ 6-2

Connection Parameters ................................................................... 6-3 Applications .................................................................................... 6-7 Options.......................................................................................... 6-11 Web and GUI Tab......................................................................... 6-11 5250 Tab ....................................................................................... 6-21 Dictionary ..................................................................................... 6-22 Link Exceptions ............................................................................ 6-23 Toolbar.......................................................................................... 6-24 System Tray .................................................................................. 6-25

PERFORMING A MANUAL TEST ............................................... 6-26 Spell Check Errors ........................................................................ 6-31 Link Errors.................................................................................... 6-31 Markups ........................................................................................ 6-32 Windows Vista.............................................................................. 6-34 Toolbar Options ............................................................................ 6-34

History Tab ................................................................................... 6-35 Saving Results .............................................................................. 6-37 Maintaining Projects and Test Cases............................................ 6-41

VIEWING RESULTS....................................................................... 6-43 Summary....................................................................................... 6-45 Warnings....................................................................................... 6-45 Screens .......................................................................................... 6-46 Response ....................................................................................... 6-47 Pass/Fail ........................................................................................ 6-48 Report............................................................................................ 6-49 Viewing Results from TestBench-PC........................................... 6-52

TEST EXECUTION FROM A TESTING TASK ........................... 6-53 Adding Defects ............................................................................. 6-56

About This Manual The information contained within this manual can also be accessed via the product on-line Help Text which is available throughout the products. Contact Details The Original Software Group Ltd Grove House, Chineham Court Basingstoke, Hants, RG24 8AG United Kingdom Telephone +44 (0)1256 338666 Fax +44 (0)1256 338678 Email [email protected] page www.origsoft.com Origsoft Inc. Suite 170, 601 Oakmont Lane, Westmont, IL 60559, USA Telephone +1 (630) 321-0092 Fax +1 (630) 321-0223 Email [email protected] page www.origsoft.com

http://www.origsoft.com/

mailto:[email protected]


TestPlan

1 TestPlan

Introduction TestPlan is a unique application that enables users to set up, manage and monitor all activity relating to testing plans. TestPlan is far more than just a test planning and defect tracking tool. It offers the ability to control major elements of the testing process from within a test plan, quickly making it the centre of testing functionality and creating large improvements in test process efficiency. With TestPlan, testers can append documents, screenshots and data to a task or defect, to help developers better understand the problem. Additionally integration with other test modules from Original Software means test scripts, data cases and other test components can be attached and launched - all from within TestPlan. TestPlan is compatible with a range of platforms and plan data is stored centrally on the server. The database options include Oracle, Microsoft SQL Server and IBM DB2. This means it can be instantly accessed by any member of the development and testing team, creating direct lines of communication between testers and developers working on a common task. This results in a clearer, more transparent approach.

TestBench PC Products 1-1 The Original Software Group

TestPlan

Getting Started When TestPlan is launched, the following window is displayed.

Connection Shows the name of each server for which there

is an ODBC connection available. When a System is selected, an ODBC connection will be made (may take anywhere from 2 to 30 seconds). Only ODBC Data Sources which include the word ‘TestBench’ will be displayed.

Library If using the IBM iSeries as the server this is the

library in which the TestBench application is stored and should be left as the default TB_5PO. For SQL Server, Oracle and Access this is the name of the TestBench database.

User ID Identifier associated with user name within

TestPlan administration. An alphanumeric field containing at least 1 but no more than 10 characters used as a part of the login.

Password A case sensitive alphanumeric code containing

at least 5 but no more than 10 characters used as a part of the login. The password should be kept confidential.

When TestPlan is first installed, Admin is the only pre-existing User ID. Enter Admin into the User ID field. Leave the password blank when entering TestPlan for the first time. Upon clicking ‘OK’ on the login window the following window will appear.


TestPlan

Your Original Software representative has provided you with a Security Code to be entered into these fields. This code will be four sets of five alphanumeric characters, each set separated by a hyphen. Enter these characters into the fields in the order they appear. Then click ‘OK’. The next step is to set the administrator’s password. This is the first and only time this screen will appear. From this point forward the administrator (or a user with administrator authority) must create any new TestPlan users along with their initial passwords.


at least 5 but no more than 10 characters used as a part of the login. The password should be kept confidential.


TestPlan

TestPlan Versions There are two versions of the TestPlan application. The first, TestPlan Administrator gives access to all the functionality and is described in more detail throughout the rest of this guide. The second is TestPlan User, a reduced functionality version, which enables the user to update tasks and add/maintain defects but does not allow any changes to the structure of the plan. Please note that the functionality available can be further restricted by setting authority levels for the user, see later chapter for more details.

TestPlan User

The following functionality is available in TestPlan User:- • Creation of defects. • Editing defects (including the maintenance of associated elements

such as PC Files, Test Results and Components). • Editing tasks (including the maintenance of associated elements

such as PC Files, Test Results and Components). • Generation of reports. • Generation of charts/statistics. • Search facility for tasks/defects. • Viewing of milestones. • Filtering of viewable task/defect information.

TestPlan Administrator

Functionality which is only available in TestPlan Administrator includes:-

• Creation and deletion of plans. • Adding/deleting tasks. • Deletion of defects. • Adding milestones. • Adding folders and altering folder structure.

For more information on each of these functions please see the subsequent corresponding section.


TestPlan

TestPlan Main Panel Options The following image is the TestPlan Main Panel. (Rotated in the interest of readability)


TestPlan

The panes can be moved to different positions and also overlaid. To move a pane, click on the panel and drag it to the new location. To overlay a pane, click on the panel and position it over another panel, a tab for each pane will appear at the bottom on the pane. The panes can be hidden by clicking on the Pin icon in the panel, when this is done a tab for the panel will appear on the left hand side of the screen. To restore the pane, click on the tab icon that represents the pane. This will re-display the pane in a temporary position while your mouse hovers over it. At this point you can then click on the Pin Icon at the top right corner of the pane to fix the pane as part of the panel.

File

New Add a new Plan - see the following section for more information. The New option is also available by clicking the New icon on the toolbar.

Open Access an existing Plan - see the following section for

more information. The Open option is also available by clicking the Open icon on the toolbar.

Admin Access the administration options - see later section for

more information. This option allows the administrator to add new users, allocate authority for specific users to Plans, edit Plans and change some defect and task options. This option is greyed out if the user does not possess Admin authority.

Properties Create Task and Defect User Fields for this Plan only.

These are fields which will appear on additional tabs on the Task and Defect forms to enable extra information to be recorded. They can also be defined at the system level using the Admin form. See later section for more information.

Report Run a report - see later section for more information.

This option is greyed out when a Plan is not open. The Report option is also available by clicking the Report icon on the toolbar.

Chart View a three dimensional chart of defects by status and

priority. It is also possible to display a tabular view of


TestPlan

the related statistics. The Chart option is also available by clicking the Chart icon on the toolbar. This option is greyed out when a Plan is not open.

Milestones Milestones are a set of important dates or events that

can either be task related or independent of task. Use this option to view existing milestones, add or delete milestones. The Milestones option is also available by clicking the Milestones icon on the toolbar. This option is greyed out when a Plan is not open.

Exit Close TestPlan.

Help

Help Topics Access the online TestPlan help information. The Help option is also available by clicking the Help icon or by pressing F1.

Contact us Send an email to the Original Software support

team. Check for updates Open the Service Packs area of the Original

Software customer support site. Please contact your point of supply for a user id and password.

About TestPlan Open a window showing the TestPlan version

number and license code. The registration button becomes available allowing the user to enter a security code as described previously in this chapter.

Toolbar Options

Most toolbar options also exist on the above menus and these have been described in the previous section. The exception is the Search function which is explained later in this user guide.


TestPlan

Admin Options When the Admin option is selected from the File menu the following window is displayed. If the user does not have Admin authority only the Plans tab is available.

Resources Create, modify and delete TestPlan users, assign

users to individual Plans and edit the user’s authority to those Plans.

Plans Assign users to Plans and edit the user’s

authority to those Plans. Also add new Plans and copy and delete existing Plans.

When errors are found within a task they are assigned as defects. The following two options relate to these defects. Defect Priority Create or modify a list of priority values (e.g.

Low, Urgent, etc.). Each defect will be associated with one of these values. It is in this way that users can easily view which defects are most critical within a task. The defect priority is a user defined item.

Defect Status Create or modify values that illustrate how close

the defect is to being resolved. These statuses will also be associated with either an open or closed stage. Defects are treated differently


TestPlan

based on their current stage. The defect status is a user defined item.

Task Status Create or modify values that illustrate how close

the task is to being resolved. These statuses will also be associated with either an open or closed stage. Tasks are treated and displayed differently based on their current stage. The task status is a user defined item.

Data Sources Create or Amend existing Data Sources from

which to operate and work within. Different data sources can therefore be utilized at different times dependent on individual needs. Once configured TestPlan will be able to attach and launch TestBench Components and Results which are held on different servers to allow for those users with multiple copies of TestBench. This provides a very holistic approach to testing and test planning.

Task User Fields Define additional fields that will be available via

an extra tab on the Task form. These can be used to specify information specific to your business needs. Fields defined here will be available to all Plans, but User Fields can also be defined at the specific Plan level.

Defect User Fields Define additional fields that will be available via

an extra tab on the Defect form. These can be used to specify information specific to your business needs. Fields defined here will be available to all Plans, but User Fields can also be defined at the specific Plan level.


TestPlan

Menu Options

The following options are available via the screen icons or right click menu when an item has been highlighted and are only enabled when they can perform a useful function. New Create a new item, see following sections for

more information. Edit Edit the item, see following sections for more

information. An item can also be edited by double clicking the table row.

Copy This option is only available when viewing

Plans and provides access to Copy Plan Wizard. See later section for more information.

Delete Remove the item, see following sections for

more information. A confirmation window is displayed.

Move Up This option is only available on the Defect Priority, Defect Status and Task Status screens. An existing item may be moved up the list one row at a time. Highlight the intended item prior to proceeding

Move Down This option is only available on the Defect

Priority, Defect Status and Task Status screens. An existing item may be moved down the list one row at a time. Highlight the intended item prior to proceeding

Edit Resource

The following screen is displayed when either the New or Edit options are selected from the Resources panel. All required fields are denoted by a *.


TestPlan

User ID Identifier associated with the user name within

TestPlan administration. An alphanumeric field containing at least 1 but not more than 10 characters. It is used as part of the login and must be unique. This is a required field.

Name Tasks and defects are allocated to a resource

based on resource name. Name is an alphanumeric field. It can be a minimum of 1 and a maximum of 40 characters in length. This is a required field.

Job Description 40 character field used to explain the role of the

resource. Authority Choose from a predefined list of permission

levels which will be the default authority for this


TestPlan

resource. Each authority level also includes all of the authority levels beneath it. This is a required field.


at least 5 but no more than 10 characters used as a part of the login. The password should be kept confidential. This is a required field.

Confirm Password Password verification field. A case sensitive

alphanumeric code containing at least 5 but no more than 10 characters. The entry here must be an identical match of the password field. This is a required field.

Email Address Enter a valid email address for this user. When

a defect is raised or edited and the ‘Send e-mail notification’ box is checked, this field is accessed and copied into an outgoing email.

Comments Free form field used for notes or comments.

This field is 1024 characters in length. Plans A tick next to a Plan indicates that the resource

has access to the Plan, the specific level of authority is shown in the table. This can be changed by highlighting the authority level and selecting an alternative from the drop down list. When a new Plan is checked the resource will be automatically added with their own Default Authority.

It is possible to view only those Plans that the resource has access to by ticking the ‘View selected items only’ option.


TestPlan

Edit Plan

The following window is displayed when either the New or Edit options are selected from the Plans panel.

Plan Name of the Plan for which user authority will

be modified. The Plan can be renamed by changing its name here.

Data Source A Data Source points to the server on which the

TestBench database is stored. The drop-down list will contain those servers which are configured and are available for selection. TestPlan fully supports a variety of Data Source types – iSeries, SQL, Oracle and Access.

Authority A tick next to a resource indicates that the

resource has access to the Plan, the specific level of authority is shown in the table. This can be changed by highlighting the authority level and selecting an alternative from the drop down list. When a new resource is checked the resource will be automatically added with their own Default Authority.


TestPlan

It is possible to view only those resources which have access to the Plan by ticking the ‘View selected items only’ option.

Copy Plan Wizard

The following window is displayed when the Copy option is selected from the Plans panel.

Copy folders If this option is checked the folder structure

from the existing Plan will be copied to the new one and the following three options will be enabled.

Copy PC Files Choose whether or not PC Files attached at the

folder level will be copied to the new Plan. Copy Components Choose whether or not TestBench Components

attached at the folder level will be copied to the


TestPlan

new Plan. Copy Tasks If this option is checked the following window

is displayed where details about the tasks being copied are defined.

Copy PC Files Choose whether or not PC Files attached at the

task level will be copied to the new Plan. Copy Components Choose whether or not TestBench Components

attached at the task level will be copied to the new Plan.

Task Statuses By default all tasks within the Plan will be

copied to the new Plan and their statuses will remain the same as they were at the time of the copy. However, if for example a new version of the software must be regression tested the existing Plan can be copied and all task statuses reset to their initial state.


TestPlan

Alternatively it is possible to copy only those

tasks with specific status values in the existing Plan, these statuses can then optionally be changed in the new Plan.

Task Defects Controls whether or not defects are added to the

new Plan and if so are they left untouched in the original Plan (copy) or removed from it (move).

The following window always appears as part of the Plan copy and will follow the Welcome screen if tasks are not being copied.

Do not copy resources The only resource that will be copied to the new

Plan is the user performing the copy and they will be given Administrator authority.

Copy source resources All resources with access to the original Plan

will be copied to the new Plan, their authorities remain unchanged.


TestPlan

Copy used resources All resources that have been assigned to a task

or defect in the Original Plan or who have raised a defect will be added to the new Plan, their authorities remain unchanged. Resources with access to the original Plan but who have not been allocated within the Plan are not copied.

Copy selected resources The user can select which resources should be

copied to the new Plan and can optionally re-allocate tasks and defects to another resource in the new Plan. To do this click the New Resource name in the table and select from the drop down list.

The following window is displayed once all copy options have been specified. Click Finish to perform the copy, Back to revise your selections or Cancel to end the copy.


TestPlan

Defect Priority

A default list of Low, Medium and High priorities is shipped as standard with TestPlan. This option can be completely customized at the global level. The sequence of the priorities in this list determines the sequence in which they will appear on the defect chart and can be changed with the Move Up/Move Down options.

Edit If the priority is attached to defects in any Plan

they will be adjusted to mirror the updated priority.

Delete If the priority being removed is attached to any

defects, the user will be prompted to change all associated priorities from the one being deleted to an existing choice. If not changing defects to an existing choice, the priority being deleted must first be manually removed from any defect to which it is currently attached.


TestPlan

Defect Status

A default list of To Do, Fixed and Closed statuses are shipped as standard with TestPlan. This option can be completely customized at the global level. Every status is associated with a Defect Stage which is an internal code defining the defect as open or closed.

Edit If the status is attached to defects in any Plan

they will be adjusted to mirror the updated status.

Delete If the status being removed is attached to any

defects, the user will be prompted to change all associated statuses from the one being deleted to an existing choice. If not changing defects to an existing choice, the status being deleted must first be manually removed from any defect to which it is currently attached.


TestPlan

Task Status

A default list of Not Started, In Progress, Testing Finished, and Completed statuses are shipped as standard with TestPlan. This option can be completely customized at the global level. Every status is associated with a Task Stage which is an internal code defining the task as open or closed.

Edit If the status is attached to any tasks in any plan, those tasks will be adjusted to mirror the updated status.

Delete If the status being removed is attached to any

tasks, the user will be prompted to change all associated statuses from the one being deleted to an existing choice. If not changing tasks to an existing choice, the status being deleted must first be manually removed from any task to which it is currently attached.


TestPlan

Data Sources

This option can be completely customized at the global level. Every Data Source can then be utilized by the Test Components and Test Results functionality. Once configured here this will allow full maintenance of components stored on different servers. Choosing one of the Data Sources from the drop down box will point the application to search on the specified database for the Test Component/Result which you wish to attach. TestPlan fully supports the following Data Sources – iSeries, SQL, Oracle, and Access.

New You can enter any alpha numeric name for the

Data Source, however duplicate names are not permissible.

Edit With this option it is possible to edit any

existing Data Source attributes. Delete By highlighting the Data Source required and

selecting this option, the Data Source will be removed and will no longer be available in conjunction with the maintenance of Test Results and Components functionality.


TestPlan

Task and Defect User Fields

User Fields specified at the Admin level are available to all Plans. Once at least one field has been defined, additional tabs appear on the Task and Defect forms containing the new fields, which can then be used as a standard part of the definition. These fields can be made mandatory, are included in the Search, and certain types can optionally also be included in the Filter. These fields can also be defined at the Plan level by selecting the ‘Properties’ option from the ‘File’ menu.

Name The name of the field as it will appear on the Task or

Defect form. Description Free text to further describe the purpose of the field. Type Choose from the available options of Text, Number,

Date, Checkbox, List and Multi-List. Only the List and Multi-List field types can be used by the Filter.

List Values For list and Multi-List field types, define the valid list

of values that the user will be able to select from.


TestPlan

Default Value Optionally specify a value that will appear in this field by default.

Required Use this option to specify whether or not this field will

be mandatory for the Task or Defect. Show in Filter This option is only available for List or Multi-List field

types. It controls whether or not the field will be available to be used by the Task or Defect Filter.


TestPlan

Main Toolbar

Search

Access to the following window is obtained by clicking either the Search button on the TestPlan Main Panel, selecting Search from the Edit menu or pressing Ctrl+F.

For The user can search for specific items within

either tasks or defects. Plan The search being performed may range from

specific to global. There are three options here. Current Plan will only look within the plan that is currently open for update. My Plans will search every plan to which the current user has access. Finally, All Plans will attempt to locate the search criteria within every plan. However only those with high enough authority (such as Administrator) will have access to ‘All Plans’

ID A unique defect number is generated for each

defect within TestPlan. In other words no two plans will share the same defect number. It also means that the defect number will not change, even if the defect is moved to another task,


TestPlan

folder or even Plan. If a specific Defect ID is known, it may be entered and searched upon here.

Text Enter any combination of characters, symbols

and/or numbers to be found. This option is not case sensitive. Do not use quotation marks unless there are quotation marks in the text to be found. This option may be used to search either tasks or defects but not both simultaneously. When searching for Tasks the Text and ID fields are mutually exclusive. If one is used in a search the other will automatically be cleared. The search will be performed against both the description and comments areas for tasks or just the description for defects. The search will also be run over any User Fields. For defects the Text and ID fields are available.

Include History By checking this box the user can include any

textual elements which have appeared in the historical logs of defects and tasks. Note the string of text entered must exactly match that in the historical task or defect log.

There are also two more features to the Search facility. You can Search Items in the ‘Current’ state based on different parameters and also using user configurable search parameters it is possible to search on a ‘Transition’ state – see below.

Current State Clicking on the arrow to the right of this option

enables you to choose which parameters you wish to search on. For instance in the example below, all defects which currently have a Status of ‘To Do’ and with a Priority of ‘High’ will be searched for.


TestPlan

Transition State Expand this section to access these options by

clicking on the arrow next to the label. You are able to select the transitional values between different states. In the example below, the defects displayed are those for the ‘Current Plan’ which have been changed to a Closed status in the time frame specified. This type of search does not necessarily reflect the current status of the tasks or defects.


TestPlan

Include transition search To enable the transition search facility this

check box must be ticked. From This is an optional field. To initiate a

transitional search which will return results between two dates, choose the start date from the calendar.

To This is an optional field. To initiate a

transitional search which will return results between two dates, choose the end date from the calendar. The date chosen must be later than the date entered in the ‘From’ field.

Field The list of available options will depend upon

whether the ‘Tasks’ or ‘Defects’ selection has been chosen . Any of the elements displayed in the drop down box can be selected as part of the transitional state search criteria. The default value displayed is ‘Status’ for either Defect or Task searches.


TestPlan

Before This is the initial state for the given search element. The list of available options within the drop-down box will be determined by the selection made for the ‘Field’ option and the reference data fields configured within the Admin function.

After This is the secondary state for the transitional

state element The list of available options within the drop-down box will be determined by the selection made for the ‘Field’ option and the reference data fields configured within the Admin function.

It is then possible to further refine the search by choosing attributes from the folders below these options. To select an attribute from a folder, double click on the folder and then check as many boxes as required. Note that all elements in the defined search parameters will have to be true to return successful matches. In the example below the search has been further refined to take into account the parameters as used in the previous example and also where the ‘Reported By’ criterion was set to ‘Richard Carbray’.


TestPlan

How to Navigate once results are found

Edit Right click on the result line corresponding to the task or defect to be accessed. Double clicking a task or defect, if it is in the current plan, is another way to open that item for editing. The resource must have edit authority or higher in order to use this option.

Edit Parent Task (Option only available for defects) Right click

on the result line corresponding to the defect and choose this option to view or change the details of the task to which this defect is assigned. The resource must have edit authority or higher in order to use this option

Delete Right click on the result line corresponding to

the task or defect. Confirming the delete prompt at this stage will remove the task or defect from the Plan.

Report Right click on the tasks or defects to be included

on the report. A report window will then display details of the tasks or defects chosen. From this window they can be viewed or printed in the same way as from the main Report function.

Open/New Plan

Access to the following window is obtained by clicking either the Open button or the New button on the TestPlan Main Panel, selecting the relevant option from the File menu or pressing Ctrl+N or Ctrl+O. It is also the default view when TestPlan is launched. When New is selected the New Plan tab is given focus and the New Plan options are displayed. When Open is chosen the Open Plan tab receives the focus and the Open Plan options are made available.


TestPlan

Open Existing Plan

Open last plan The last Plan is based on the most recent plan

accessed on the same PC. It will appear in double quotation marks next to the Open last plan radio button. Select this option and then click on the Open button.

Open other plan Click on an existing Plan in the lower part of the

screen to highlight it. These are the Plans available to the current user based on Plan authority. Click on the Open button with this option selected to access the highlighted Plan.


TestPlan

Only Show Favourites Checking this option means that only those Plans that have been selected by ticking the ‘Favourite’ column are listed.

Rename Plan Right click a Plan in the list and select this

option to rename it. Delete Plan Right click a Plan in the list and select this

option to remove it. A confirmation screen will be displayed.

Create New Plan


TestPlan

Create a new plan To add a new empty Plan select the ‘Create a new plan’ option and then click on the Open button. A prompt will appear requesting a name for the new Plan. This name is alphanumeric and can be between 1 and 35 characters in length. If this name is completely numeric, the Plan name will be right justified. If the name contains a letter the plan name will be left justified in the field. Users must have Create Plan authority to utilise this option. The user that creates the Plan is automatically given authority to edit the Plan.

Create a new plan based on existing plan Select this option to create a new Plan and copy

some information from an existing Plan. When you take this option the Copy Plan Wizard will be launched. For full detail, please see the section heading ‘Copy Plan Wizard’ earlier in this document.

Only Show Favorites Checking this option means that only those

Plans that have been selected by ticking the ‘Favorite’ column are listed.

Rename Plan Right click a Plan in the list and select this

option to rename it. Delete Plan Right click a Plan in the list and select this

option to remove it. A confirmation screen will be displayed.


TestPlan

TestPlan Main Panel

Main Panel View

The following screen shows a fully developed test Plan entitled ‘Customer Relationship Management’. A Plan is broken down into several panes or sections whose arrangement can be configured by the user. These sections include the Folders, User Tasks, View Options, Filter, the Main view and the Details view. The default information displayed in the Main section is task information, but this can be changed by selecting defects, PC files or TestBench components from the drop down list. The details of what is being displayed in the main section are shown in the Details pane, the default being defects for the selected task.

The borders of each pane can be clicked and dragged in order to re-size them. The pane configuration can also be changed by clicking on the title bar and dragging to a new location which is indicated by a grey box. If the grey box has a tab at the bottom the two panes will overlay each other, as with the Folders and User Tasks on the picture below. Any of the panes can be added as tool bar options if you do not wish them to be permanently in view as with the View Options and Filter on the picture


TestPlan

below. Click on the icon to temporarily display the pane. Click on the pin icon if you then wish the pane to become a permanent part of the display. It is also possible for the user to define and save their preferred layout. This is achieved by right-clicking on any of the main panel banners. There are three options available, although the ‘Restore preferred layout’ option is only available once one has been ‘saved’. Restore Default Layout The application creates a default view which is standard

for all plans. If following user configuration of the view you wish to restore back to the default view then right click on one of the pane banners and select the option.

Save Preferred Layout If you wish to continually use a particular view for any

given plan, then by right clicking on one of the pane banners and selecting this option, the application will allow you to restore to this view in future if the view should change.

Restore Preferred Layout Note that this option is only selectable if you have

already saved a preferred layout. Also note that you may only restore back to the last saved layout. Right click on any of the main panel banners and select the option for it to take effect

The sequence of items displayed in the panels can be sorted by clicking on the column title that you wish to sort by.


TestPlan

Folders

Folders are used as a framework to organize testing and planning at the highest level. A folder is an envelope used to hold other folders along with various tasks that need to be accomplished within a certain area or application. Each task may have one or more defects. In order to utilize the options available within a folder, left click the folder to bring it into focus and then right click it. All folders are indented from the top folder which shares its title with the Plan name. There are three options which control the folder view. These can be changed using the View Options. None No statistics are shown. Task Count Two numbers in square brackets before the folder name

show the number of tasks with a stage of ‘Open’ out of the total tasks that have been added to the folder. These numbers are affected by any filters that have been applied to the Plan. The folder icon will contain a green square if all of the tasks have a stage of Closed or a blue square if any tasks are Open. Where the ‘Show all items in sub-folders’ view option has been selected, if all items within the selected folder and its sub-folders are Closed then the coloured square will be green. However where this is not the case and some items within the subfolders are open the square will be split diagonally with the top half being shaded green and the bottom half blue. Conversely if all the items in the sub-folders are Closed but some are Open in the parent folder then the square will be displayed as a diagonal split with the top half blue and the bottom half green.

Defect Count Two numbers in square brackets before the folder name

show the number of defects with a stage of ‘Open’ out of the total that have been added to the folder. They are the aggregate number of defects for all tasks within the folder. These numbers are affected by any filters that have been applied to the Plan. The folder icon will contain a green square if all of the defects have a stage of ‘Closed’. If any defects are still ‘Open’ this square will appear in red. If there are no defects the colored


TestPlan

square is not present. Where the ‘Show all items in sub-folders’ view option has been selected, if all items within the selected folder and its sub-folders are closed then the coloured square will be green. However where this is not the case and some items within the subfolders are open the square will be split diagonally with the top half being shaded green and the bottom half red. Conversely if all the items in the sub-folders are Closed but some are Open in the parent folder then the square will be displayed as a diagonal split with the top half red and the bottom half green

The following are the right click menu options. The resource’s authority within each plan will dictate which of these options are available. For example, to move or copy a folder the resource must have Edit Plan authority or higher. New Folder Click on ‘New Folder’ or press Ctrl+R to add a

folder. This folder will be added as a subfolder to the currently active folder. The new folder will now be highlighted. Key in a name at this time or press Enter and the folder name will default to ‘New Folder [next available number]’. Folder names are alphanumeric and can be between 1 and 35 characters in length. Folder names may be reused but must be unique if at the same level within the same folder.

Cut Click on ‘Cut’ or press Ctrl+X to cut a folder in

order to move it to a new location. Cutting a folder may only be used directly with Paste Folder (below). After completing the paste folder action, the folder that is cut will be removed from the folder it was attached to along with all of its subfolders, tasks, defects and attachments and added to the new location. (See also Drag and Drop below)

Copy Click on ‘Copy’ or press Ctrl+C to copy a folder

in order to place it in a new location. Unlike the Cut option, Copy will not remove the initial folder and its contents. Copying a folder may only be used directly with Paste Folder (below).


TestPlan

After completing the paste folder action, a duplicate version of the folder that is copied will be attached to another folder along with all of its subfolders, and other information such as tasks or defects that has been specified on the View Options. See later section for more information.

Paste Click on ‘Paste’ or press Ctrl+V to paste a

folder. Pasting a folder may only be used directly with either Cut or Copy (above). After cutting a folder, the paste folder operation will add the cut folder along with all of its subfolders, tasks, defects and attachments directly under the active or highlighted folder. After copying a folder, the paste folder operation will add the copied folder along with all of its subfolders and other information specified in the View Options directly under the active or highlighted folder.

Rename Change the name of the selected folder. Folder

names are alphanumeric and may be 1 to 35 characters in length. Folder names may be reused but must be unique if at the same level within the same folder.

Delete Folder Highlight a folder and click this option or press

the delete key on the keyboard. A prompt will appear to confirm the delete request. Click ‘Yes’ and the folder will be removed along with all of its subfolders, tasks, defects and attachments.

Properties Define a default Data Source, Project and Test

Case for the storage of manual test results. Move Up The folder will always stay at the same

level/indentation. In other words, this position change will only occur within the confines of a single parent folder. This folder will exchange places with the folder above it within the same parent folder. If no folder exists above it, the highlighted folder will maintain its current


TestPlan

position. When a folder moves up it carries with it all of its subfolders, tasks, defects and attachments.

Move Down The folder will always stay at the same

level/indentation. In other words, this position change will only occur within the confines of a single parent folder. This folder will exchange places with the folder below it within the same parent folder. If no folder exists below it, the highlighted folder will maintain its current position. When a folder moves down it carries with it all of its subfolders, tasks, defects and attachments.

Report Generates a report for the highlighted folder and

all subfolders. See the Report section later in this User Guide.

Chart Display a defect chart based solely on this

folder. See the Chart section later in this User Guide.

Drag and Drop This option has the same effect as the two step

process of cutting and pasting. Unlike those options, it is not accessed by right clicking the mouse. Instead, determine the highest level folder to be moved, left click the folder and hold down the mouse button. Drag the folder, by moving the mouse until the new parent folder is highlighted. At this point release the left mouse button. After completing these steps, the folder that was selected will be removed from the folder it was attached to along with all of its subfolders, tasks, defects and attachments and added to the new location. (See Cut and Paste above)

NOTE: The top level folder cannot be manipulated the way other folders can. For all intents and purposes the top folder is the Plan. Deleting the top level folder is equivalent to deleting the Plan which must be done from the Open Plan panel. The Plan can also be renamed here. The only available options are New Folder, Chart and Report. The chart works


TestPlan

differently for the primary folder than any other folder, the chart and statistics are displayed based on all subfolders of the primary folder.

Tasks

A task is a detailed item to be accomplished and resides within a folder. Tasks can be allocated to a specific owner or Resource who will then be responsible for seeing the work through to completion. By default, Tasks are displayed in the upper right hand pane of the TestPlan main panel, but this can be changed via the drop down list to view Defects, TestBench Components, PC Files or Test Runs. The following options are displayed after right clicking within the task pane. The resource’s authority within each plan will dictate which of these options are available. For example, to cut or copy a task one must have Delete Task authority or higher. New Task The task will be added to the folder which is

currently active. The active folder is highlighted in the pane on the left and will also appear in the ‘Folder:’ field directly above the task pane. A new task is always added to the end of the list of tasks. Please see below for more information on adding tasks.

Edit To modify an existing task, highlight the task in

the task list and right click, then choose ‘Edit Task’ from the list that appears. Double clicking the task will also open it in edit mode. See below for more information on editing tasks.

Execute Initiate a manual test of the selected Task.

Launch TestDrive-Assist if it is not already active and create Test Items from the Task Steps. At the end of the test the results can be saved back to the Task. This option is only available for Tasks with Steps. See the Manual Testing chapter for more information.

Delete To delete an existing task, highlight the task in

the task list and right click, then choose ‘Delete’


TestPlan

from the list that appears. If the task being removed has any defects, pc files or components associated with it, those items will also be deleted.

Copy Click on ‘Copy’ to copy a task in order to place

it in a new location. Unlike the Cut option, Copy will not remove the source task or its contents. Copying a task may only be used in conjunction with Paste Task. After completing the Paste action, a duplicate version of the task will be attached to another folder along with all of its attachments. The View Options control whether or not any Task history or defect information is also copied, see later section for more information.

Cut Click on ‘Cut’ or to cut a task in order to move

it to a new location. Cutting a task may only be used in conjunction with Paste. After completing the Paste the task that is cut will be removed from the folder it was attached to along with all of its defects and attachments and then added to the new location.

Paste Click on ‘Paste’ to paste a task. Pasting a task

may only be used directly with either Cut or Copy (above). After cutting a task, the paste task operation will add the cut task along with all of its defects and attachments directly under the active or highlighted folder. After copying a task, the paste task operation will add the copied task along with all of its attachments and other information specified in the View Options directly under the active or highlighted folder.

Move Up Move the Task up one item in the list. This

option is not available if the ‘Show all items in sub-folders’ option is checked.

Move Down Move the Task down one item in the list. This

option is not available if the ‘Show all items in sub-folders’ option is checked.


TestPlan

Clear Sort Remove any sorting of Tasks that has been

created by clicking on the grid column headers, so that the Task list reverts to the order in which they were added.


TestPlan

Add/Edit Task

Task Details

The following panel is displayed after the New or Edit option is selected from the Task pane.

Description Alphanumeric field used to explain the

requirements of a test. This is a mandatory field and will appear on both the Task Report and the Defect Report. This field will also be shown on the Milestones table if a milestone is set for this task.


TestPlan

Start/End Date Schedule an expected start and/or completion date for this task. There are two ways to modify dates.

1) Click the check box next to the date to

activate it, then click on one of the individual fields within the date (e.g. click the two digit month field). The date is shown in month, day, year format. Modify the date by using the numeric keys on the keyboard. Each field must be modified on its own. The separate fields may also be selected and modified using the keyboard’s arrow keys. When satisfied with the date, click on another option or if finished modifying the task, click the Save button.

2) Click the drop down arrow to the right of

the date list box to display the calendar function. Use the right and left arrow buttons to scroll from month to month. Once the correct month has been accessed, click on the appropriate day. The check box will automatically be populated.

Duration Total number of days estimated for this task. If

the Start and End Dates have both been added, the duration field will auto-populate with the calculated number of days from start to end. If the Duration field and the Start Date field are both populated, the End Date field will then be calculated and auto-populated.

Status Select from the list of task statuses that have

been defined in the Administration Options. These are used to give a quick understanding of how far along the testing has progressed. This field can be used within the filter functionality to narrow down the scope of the test plan.

Allocated To Allows the Task creator/editor to assign the task

to a resource. Only resources given appropriate access to this plan on the Plan Authority panel will appear in this list. This field can be used within the filter functionality to narrow down


TestPlan

the scope of the test plan. Reference An external reference number that links several

tasks and/or defects. The Reference field is also found on the Edit defect window.

Comments Free form alphanumeric field used to further

define the requirements of a task/test. Set as Milestone Check this box if the date for this task should be

considered a very significant event. Then choose the appropriate radio button (Start date as Milestone or End date as Milestone) to indicate which date is most important. If selected this task will appear in the Milestones table.

User Fields

This tab is only visible if any User Fields have been defined either at the System level (using the Admin form) or the Plan level (Properties option from the File menu). User Fields enable additional information to be recorded about the Task. This information can then be searched upon or included in the Filter.


TestPlan

History

The task history enables anyone involved with a certain task to list their comments in a central location. This allows for a dialogue between the manager and the resource responsible for testing the task. It also gives anyone else involved the opportunity to review what has transpired to that point and even adds comments of their own. Proper use of task history will result in tasks being tested and closed rapidly and accurately. To add a log history record, key some text into the Add Log History field and click on the Save button. Once an entry has been made it can not be edited, this provides an accurate account of the events surrounding your task. To view the detail simply hover your mouse over the entry under the column named Log. If you require a more detailed view you can also double click the entry to show the task history panel. The following items are displayed beneath their corresponding header. In some cases the complete contents or description will not be viewable for


TestPlan

lack of space. If this occurs, move the cursor in between the header titles. A vertical line with arrows pointing outward will appear. Click and hold the left mouse button and drag the header bar to give the appropriate description below more viewable space. The entire window can also be expanded by clicking and dragging the window edges. Date The date that the log history was added. Time The time that the log history was added. By The name of the resource who added the log

history. Status The status of the task at the time the log history

was added. Log The text that was keyed into the Add Log

History field. Can be used to respond to another resource or just to enter additional notes about the task.


TestPlan

Steps

The tab labeled Steps can be used to store detailed information on the execution of a task. This detail being broken down into the different steps required for the successful task completion. This is an ideal method for reminding staff of all the correct steps required to complete a task and can also act as a checklist. Each step can have multiple columns, these can be used for instructions, data input and expected results. When a task is executed and a manual test initiated, the steps are converted to Test Items which can then be passed or failed and stored in the results database for the task. Each step can be one of five different types as listed below, examples of the application of each step type are shown on the screen print above.

• Instruction • Screen • Keyboard


TestPlan

• Mouse • Check

Change the step type by clicking on the step and then on the relevant icon on the toolbar. Change the sequence of the steps by clicking and dragging the grey box to the left of each row. Toolbar Options Insert Add a new step to the grid after the current step. Delete Remove the highlighted step. Add a column to the right Insert a new column to the right of the one that is

currently in focus. Delete the column Remove the column that is currently in focus. Set default column The default column is the one that will be shown in

TestDrive-Assist when a task is executed and on any reports where it is not possible to list more than one column. The default column header is shown in bold on the above display.

Reset Clear all Steps information and revert back to a single

column display. A confirmation screen is displayed. Import Excel steps from the Clipboard This option enables steps information that is already

contained in another format, for example a spreadsheet, to be copied into the steps grid. You will be asked whether or not the data being imported contains column headings.

Import last column headers used This option is only enabled if no steps have been

defined for this task. It enables the last set of user-defined column headers to be copied to the current task.

Execute Initiate a manual test of the selected Task. Launch

TestDrive-Assist if it is not already active and create


TestPlan

Test Items from the Task Steps. Due to the fact that TestDrive-Assist appears as a narrow sidebar, only the default step column will be displayed. Double click the column header from within TestDrive-Assist to show an extra window containing all of the columns. At the end of the test the results can be saved back to the Task. This option is only available for Tasks with Steps. See the Manual Testing chapter for more information.

Right Click Options One or more Steps can be copied or moved to a Task in any Plan by selecting the required Steps and then right clicking to reveal the Cut, Copy and Paste options.


TestPlan

Results

The following panel is displayed when Results is selected from the Add/Edit Task or Defect screens.

Any test Result which is stored on a known Data Source can be attached to a task or defect using this tab. This feature is intended to allow testers to capture the test results associated with a particular test, for example to assist with the explanation of a particular defect. By right-clicking the Results section in the Defect or Task window the following options are available. Attach When choosing this option the screen below is displayed.


TestPlan

By entering parameters for the Data Source, Project and Test Case the required Test Result can be attached to the Task or Defect. Summary details on each are displayed in the window above once the Result has been attached. View Details The following screen is displayed. Dependent on the type of Result chosen, not all the tabs will be appropriate.


TestPlan

Delete Remove the link to any attached Test Result. Note the result itself is not deleted from the server. Paste Use this option to add in Results copied or cut from other tasks or defects. Copy Use this option to copy results to other tasks or defects. Cut Use this option to cut results from any given task or defect.


TestPlan

PC Files

The following panel is displayed when the PC Files tab is selected from the Add/Edit Task or Defect screens.

Any file that is stored on a personal computer or network can be attached to a task or defect using this tab. This feature is intended to allow testers to capture screen shots, collect data and create documents in a file and then append them to a task or defect. In this way a tester can help a developer to better understand a problem related to this task or can include a detailed test specification for the task. The files are not saved within TestPlan. Rather, TestPlan saves the path to the file so that if a file is modified it will not have to be replaced after the change. The following items are displayed beneath their corresponding header. In some cases the complete contents or description will not be viewable for lack of space. If this occurs, move the cursor in between the header titles. A vertical line with arrows pointing outward will appear. Click and hold


TestPlan

the left mouse button and drag the header bar to give the appropriate description below more viewable space. The entire window can also be expanded by clicking and dragging the window edges. File Name Name of the file as it exists on the pc/ network. Modified Date Date the file was created or last changed. This

is not the date that the file was attached to the task.

Full Path Access path to the file on the pc or network. Computer Name Name associated with a particular personal

computer. This name can be found by right clicking on the My Computer icon on the pc’s desktop. Then click Properties and then the Computer Name tab on the System Properties window.

Attached by User Full User Name of the resource who attached

the file to the task or defect. The following menu options are available on right click. Attach Navigate to the location of the target file

through the use of a browsing window. This functionality is nearly identical to double clicking the My Computer icon on the desktop of a pc. If a password is normally required to access a network drive the user will be prompted to enter one through this facility as well. Multiple files can be selected and attached at one time.

Attach URL Specify the name of the URL to attach to the

task or defect. Launch Open the highlighted file for use through

TestPlan or navigate to the URL. The file or URL may also be opened by double clicking anywhere on the file information line. If a file has been relocated or removed a yellow yield sign accompanied by an exclamation point will


TestPlan

appear next to the file name. The user may choose to click attach file to open the window browser and find the file in its new location.

Delete This will delete the link or path to the file or

URL from the PC Files window, leaving the actual file unchanged. Multiple files can be selected and deleted at one time.

TestBench Components

The following panel is displayed when the Components tab is selected from the Add/Edit Task or Defect screens.

Original Software’s test modules can be accessed within TestPlan from this tab. This feature is intended to take advantage of normal testing practices, such as creating test scripts in TestDrive-Green or TestDrive-Gold. Testers can also continue to work with various TestBench


TestPlan

functions, developing Data Cases, Test Cases and more. They will then have the ability to attach any of those components directly to the task or defect for which they are responsible. This will allow the developer to launch these modules themselves and see precisely what the tester found, bringing communication and shared knowledge to a whole new level. In addition the results of any test cases or scripts can be attached and viewed. The modules are not saved within TestPlan. Rather, TestPlan saves the database location of the modules. In this way, a module can be accessed and launched from any pc possessing the appropriate software. The following items are displayed beneath their corresponding header. In some cases the complete contents or description will not be viewable for lack of space. If this occurs, move the cursor in between the header titles. A vertical line with arrows pointing outward will appear. Click and hold the left mouse button and drag the header bar to give the appropriate description below more viewable space. The entire window can also be expanded by clicking and dragging the window edges. Project The TestBench Project containing the

component. Type Description of the function being performed

such as *DATACASE- extract data, *COMPCASE - compare files, *TESTCASE - run a test, *GREEN - execute a TestDrive-Green script.

Case ID The name of the case associated with the Case

Type field. If it is a script, the Case ID will equal the Test Case to which the script belongs.

Name This field contains the name of the script and is

not used for any Case Type other than *GREEN or *GOLD.

Data Source The server on which the component resides. The following menu options are available on right click. Attach Add a TestBench component to the task or

defect. See the following section for more information.


TestPlan

Launch This will open the component if the correct software is installed on the pc. The component can also be launched by double clicking anywhere on the component information line. If the component or a portion of the component has been removed from the Original Software product, the module will still attempt to run and will allow the user to change certain settings. See the following section for more information.

Delete This will delete the information linking the

module to the task yet leave the module unchanged.

The following screen is accessed by right clicking anywhere in the Edit task or Edit defect window when the Components tab is selected and selecting the Attach option.

For all components other than Test Cases, double click the component or right click and choose Select to attach it. Alternatively highlight a component and then click the Add button. Continue to add as many


TestPlan

components as required. For Test Cases, right click and choose Select to attach, or double click to reveal the list of Scripts which are stored against the Test Case which can in turn also be selected. Data Source Choose any of the available ‘Data Sources’

from the drop down list. The display will default to ‘<Current database>’. If you wish to attach a component from the existing database then accept this value, otherwise select an alternative TestBench database.

Show Types Filter the list of TestBench components to only

those of a specific type, for example Test Cases. If either TestDrive-Green or TestDrive-Gold scripts are selected while viewing Test Cases and other iSeries components, the list will be filtered to show only Test Cases, with those which do not contain any of the requested script type greyed out.

Go back Using the following buttons it is possible to drill

down into Test Cases to display a list of scripts and also move back up to the top level as shown in the above display. The Back button displays the previous component list and can continue to be pressed until the display following the Attach Component option is reached.

Go up one level This button is used to return up the hierarchy to

the Project list. Refresh Re-lists the components to include any new

items and remove any which have been deleted. Change the view Click on the button or the down arrow to toggle

the list of components between the Detail view shown above, the List view which includes the component name but not its description and the Icon view.


TestPlan

Defect Pane A defect is attached to a task and should be raised when an issue is found with the task. Defects can be allocated to a specific owner or ‘Resource’ who will then be responsible for correcting the error that is occurring. Defects for a selected task are viewed by default in the lower right hand pane of the TestPlan main panel. However, all defects for the selected folder can also be viewed in the upper right hand pane by selecting Defects from the drop down list. The following menu options are available on right click. The resource’s authority within each plan will dictate which of these options are available. For example, to cut a defect the user must have Delete Defect authority or higher. New Defect This option is only available when viewing all

defects for a task. The defect will be added to the active task which is the one highlighted in the task pane. The associated task will also appear in the field directly above the defect pane. A new defect is always added to the end of the list of defects and is allocated an ID which is unique across all defects in the Plan. See the following section for more information.

Edit Double clicking the defect will also open it in

edit mode. See the following section for more information.

Delete If the defect being removed has any history, PC

files or components associated with it, those items will be deleted along with this defect. A confirmation screen is displayed.

Copy Click on ‘Copy’ to copy a defect to a new

location. Copying a defect may only be used in conjunction with Paste. After completing the Paste action, the defect that is copied will not be removed from the task it was attached to. Specify in the View Options whether or not defect history should also be copied.


TestPlan

Cut Click on ‘Cut’ to cut a defect in order to move it to a new location. Cutting a defect may only be used in conjunction with Paste. After completing the Paste action, the defect that is cut will be removed from the task it was attached to along with all of its attachments and then added, with its attachments, to the new location.

Paste Click on ‘Paste’ to paste a defect. Pasting a

defect may only be used in conjunction with cut or copy. The Paste operation will add the defect along with all of its attachments directly under the active or highlighted task.

Clear Sort Remove any sorting of defects that has been

created by clicking on the grid column headers, so that the defect list reverts to the order in which they were added.


TestPlan

Add/Edit Defect

The following panel is displayed after the New Defect or Edit option is selected from the defect pane.

Defect Description Alphanumeric field used to explain the issue.

This is a mandatory field. It will appear on the Defect Report.

Status Select from a list of user defined defect statuses.

This status field is described in detail in the Admin Options section earlier in this chapter. To change the defect status the user must have Close Defect authority or higher.

Priority Select from a list of user defined defect

priorities. This priority field is described in


TestPlan

detail in the Admin Options section earlier in this chapter.

Allocated To Allows the defect creator/editor to assign the

defect to a resource. Only resources given appropriate access to this Plan on the Plan Authority panel will appear in this list. This field can be used within the filter functionality to narrow down the scope of the test Plan.

Reported By Allows the defect creator/editor to attach their

name as the resource who discovered the defect. In this way, the resource who the defect is allocated to will know who to contact with questions about this defect. Only resources given appropriate access to this Plan on the Plan Authority panel will appear in this list. This field can be used within the filter functionality to narrow down the scope of the test Plan.

E-mail Notification Checking this box and then clicking Save

indicates that an e-mail notification should be sent to the appropriate person(s). There are two e-mail check boxes. The box on the left is related to the ‘Allocated To’ field and the one on the right corresponds to the ‘Reported By’ field. After receiving the save defect request, TestPlan will check the ‘All Resources’ tab within the ‘Administration Options’ window for the resource’s e-mail address. If one is found, the default e-mail system on that computer will be opened, creating an outgoing e-mail message complete with the ‘Allocated To’ and/or ‘Reported By’ e-mail address(es) and some important information regarding this defect. The e-mail must be manually sent at this point, by the defect creator/editor, to allow for any additional comments deemed necessary.

Reference This field can be used to store references to

other systems or applications relevant to your own environment.


TestPlan

The User Fields tab is only visible if any User Fields have been defined either at the System level (using the Admin form) or the Plan level (Properties option from the File menu). User Fields enable additional information to be recorded about the Defect. This information can then be searched upon or included in the Filter.

The defect history enables anyone involved with a certain defect to list their comments in a central location. This allows for a dialogue between the tester and the resource responsible for fixing the defect. It also gives a manager, or anyone else involved, the opportunity, to review what has transpired up to that point and even add comments of their own. Proper use of defect history will result in defects being closed rapidly and accurately. To add a log history record, key some text into the Add Log History field and click on the Save button. Again, for integrity, the entry details cannot be adjusted once they are saved. The following items are displayed beneath their corresponding header. In


TestPlan

some cases the complete contents or description will not be viewable for lack of space. If this occurs, move the cursor in between the header titles. A vertical line with arrows pointing outward will appear. Click and hold the left mouse button and drag the header bar to give the appropriate description below more viewable space. The entire window can also be expanded by clicking and dragging the window edges. Date The date that the log history was added. Time The time that the log history was added. By The name of the resource who added the log

history. Status The status of the defect at the time the log

history was added. Log The text that was keyed into the Add Log

History field. Can be used to respond to another resource or just to enter additional notes about the defect.


TestPlan

Reporting

Reporting Window

The TestPlan Reporting window is displayed by clicking the button containing the Report icon at the top of the TestPlan Main Panel or by selecting Report from the list under File on the TestPlan menu bar. As is illustrated below, creating a report is as simple as selecting two parameters and clicking the refresh button. The footer on every report will show the date the report was created, the name of the resource that created it and the page number.

Reporting Options

Folder Choose a folder from the Folder list box by clicking the

drop down arrow at the right edge of the list box. The selected folder will appear on the report along with all subfolders that exist beneath it. The option to select ‘All Folders’ will run the report based on every folder in the Plan.


TestPlan

View Select an option from the View list box by clicking the drop down arrow at the right edge of the list box. Choose between Folders, Tasks, Defects, Audit Report, Plan Statistics and Defect Graph.

Folders This option gives a tree view of all folders

selected. It also shows a summary of the open, closed and total number of tasks for each folder. After that it gives the open, closed and total number of defects per folder. Finally at the bottom of the report, a total is given for each of these individual numbers described herein.

Tasks As with the folder view, this option is arranged

based upon the folder structure. Unlike the folder view however, the tasks option will display a detailed list of the tasks within each folder. These details include the task number, task description, the status of the task, who the task is allocated to, the start date of that task and any User Fields. As was true within the folders view, the details are still shown as a summary of open, closed and total number of defects.

Defects As with the folder and task views, this option

is arranged based upon the folder structure. Within the folder structure it is also arranged by task. Unlike the folder and task views however, the defects option will display a detailed list of the defects under each folder and task. These details include the assigned unique number based on when that defect was created on the system, the defect description, the status of the defect, defect priority, who the defect is allocated to, who originally reported it as a defect and also any User Fields.

Audit Report This option will provide a dump of

information detailing every recorded update and view to the database files. This report is aimed at providing a report for compliance reporting.

Plan Statistics Will provide you with a high level

summary report of your plan, including defect overview with numbers and percentages by priority and status. In


TestPlan

addition there is an average open time across all the defects in the plan, a high level resource count and a plan duration. The ability to compare to another selected plan becomes available when this option is in use.

Defect Graph Maps the progress of open defects

against total defects. This graph can be used to check that the number of open defects is coming down, whilst also providing you with a view of the number of total defects raised for the same point in time.

Refresh Button Before clicking Refresh, any changes to the Folder list

box, the View list box and/or items that reside within the options button should be made. Clicking the Refresh button then creates a new report based on the report items selected at that time.

Print Button To create a hardcopy of the report click the Print button.

TestPlan integrates with Microsoft Printer Options. Any printer currently defined on the user’s pc may be used to print the report.

Save Button Once generated the report can be saved in Rich Text,

HTML, Acrobat pdf or Excel format. Options Button This button is only available if at least one of the

options within can perform a useful function. Some or all of the following options may be selected as ways to format or otherwise modify the reports.

Sub Folders If this option is turned off, (i.e. Subfolders

equals ‘No’) then only the folder appearing in the ‘Folder’ option at the top of this window will be used when creating the report. If set to ‘Yes’ all subfolders of the selected folder will be shown, if not disallowed by other criteria.

Empty Folders If this option is turned off, (i.e. Empty

Folders equals ‘No’) then only folders containing tasks/defects will appear on the report depending on the ‘View’ option. When the option is set to ‘Yes’ folders containing no tasks and tasks containing no defects will


TestPlan

appear at the bottom of the report. Page Break If this option is set to ‘No’, page breaks

will only occur when a page is full. When set to ‘Yes’ and when the View equals Tasks, the page will break at each new folder. When set to ‘Yes’ and the View equals Defects, the page will break after each new task.

Wrap Text If this option is set to ‘No’, only the first

35 characters of text on the description fields of tasks and defects will be displayed on the report. When set to ‘Yes’, the entire description of a task or defect will be shown by continuing the text on successive lines until the entire description is shown.

Order By When producing a report of folders or tasks,

the information is listed in folder and task sequence. However, when reporting on defects additional sequencing options are priority, status or status and priority.

Print first paragraph only If this option is selected

then only the first paragraph entered will be displayed on the report for the tasks and defects being reported.

Include Comments in description When producing a

report of folders or tasks this allows for the comments which have been entered to be displayed on the report.


TestPlan

Defect Chart The Defect Chart and statistics are displayed by clicking the button containing the Chart icon and name at the top of the TestPlan Main Panel or by selecting Chart from the list under File on the TestPlan menu bar. The Chart can also be viewed for defects residing in individual folders by right clicking the folder and selecting chart. The chart is a three dimensional image of defects by status and priority. Also, a tabular view of the related statistics can be displayed by accessing the statistics tab.


TestPlan

Chart Rotation The chart displays as a three dimensional image. The image may not always appear in a way that allows for viewing of every bar in the graph. Because of this there is an option within TestPlan to rotate the chart. To do so, hold down the Ctrl key on the keyboard and hover the mouse/cursor over the chart. The cursor should change to two intersecting curved arrows, indicating that the chart may now be moved left, right, up or down. The chart may be rotated ninety degrees up and down. It may also be rotated three hundred and sixty degrees left or right.

Statistics

The statistics tab displays the chart details in tabular form. This may be useful if a view with a more precise number of defects per status and priority is needed.


TestPlan

Milestones

Using Milestones

Milestones are a set of important dates or events that can either be task related or independent of task. Use this option to view existing milestones, add or delete milestones. The Milestones option is available by clicking the Milestones icon on the toolbar or from the File menu option. This option is greyed out when a Plan is not open.

The tick to the left of the milestone indicates that this milestone is related to a task and must be updated from the Edit Task panel. The following menu options are available on right click. Add New Create a new milestone that will not be directly related

to a task. See below for more information. Edit Change the description or the date for non task related

milestones. Delete Remove the milestone. A confirmation screen is

displayed. Edit Task Access the Edit Task panel for task related milestones.


TestPlan

Amend Milestone

The following screen is displayed when either the Add or Edit milestone options are selected.

Date Click on one of the individual fields within the date

(e.g. click the two digit month field). The date is shown in month, day, year format. Modify the date by using the numeric keys on the keyboard. Each field must be modified on its own. The separate fields may also be selected and modified using the keyboard’s arrow keys.

Description Text to describe the significance of the milestone.


TestPlan

Filters

Using Filters

The filter feature enables the user to limit the Plan view individually for each PC by various task and/or defect criteria. The Filter selection option is available by clicking the Filter icon Tab on the left side of the TestPlan panel. The filter can be fixed to the pane layout by clicking on the pin icon at the top right side of the filter pane. Use the check boxes that drop down when you click on a folder icon with the filter description to select which filters to implement. Once selections are made the options stay on view beneath their parent folder. Any Task or Defect User Fields appear at the bottom of the panel.


TestPlan

Activate

To enable the filter simply click the ‘Click here to enable the filter’ blue text. This will change the status of the filter which will toggle between the two icon values and with a clear statement to describe the current status. By activating the filter you will only see the tasks and/or defects you described within the selection criteria. When you de-activate the filter you will return to a full view of all the tasks and defects on the plan.

Edit

When editing the filter to include new selections or remove unwanted, you will be given the option to ‘Apply’ or ‘Cancel’ the changes. This provides the chance to revoke the changes at the last minute. By clicking on ‘Apply’ or by selecting the ‘Click here to enable the filter’ the changes will be taken and applied to the view over all the panes. If you select ‘Cancel’ the changes will be ignored and you will be returned to an unchanged view.


TestPlan

View Options

Enabling View Options

The View options feature enables the user to change the type of information on the current plan view. The View Options selection option is available by clicking the View Options icon Tab on the left side of the TestPlan panel. The View Options pane can be fixed to the pane layout by clicking on the pin icon at the top right side of the View Options pane. Use the check boxes to make a selection to change the type of view you wish to work with. By right-clicking on the View Options tab on the left side of the TestPlan panel there are options available which allow each individual user to control the way the panes appear. See below for more information.


TestPlan

Show Tasks as a timeline This option will change the Pane ‘Main’ to reflect a

Gantt chart view of the tasks. If a Task has not been allocated a start date nothing will appear on the Gantt. One the tasks have been plotted on the Gantt chart the start/end dates and the task duration can be manipulated by selecting the blue block on the Gantt and dragging the task to a new start date or dragging one side of the task to extend the task duration see the screen below to see how this looks.


TestPlan

Show all items in sub-folders This view will allow you to change the main pane to

include all the tasks in the related sub folders of the current folder selection.

Automatically expand folders By clicking on this option the folder structure will be

expanded and will allow you to view all the sub-folders. Wrap history Text When displaying a history view in the Details Pane, this

option allows you to see all the text for each entry of history.

Folder Count Choose to have a count against each folder in the

Folders Pane selecting the number of defects or tasks. The count will be displayed as the number of Open items against the number of total items for the folder selected. If used in conjunction with the ‘Show all items in sub-folders’, then the display will include all items in both the parent and sub-folders. When defects are selected the count will also display a small red square when outstanding defects exist in that folder. When Tasks are selected the count will display a small blue square when incomplete tasks exist in that folder. Both types of squares, blue or red, will change to green when the tasks/defects are complete depending on selection of the corresponding view option. However when used in conjunction with the ‘Show all items in sub-folders’ view option the square may appear as a diagonal split of two colours – red and green for defects or blue and green for tasks. If for example for tasks, there are none at an ‘Open’ state in the parent folder but there are some ‘Open’ in a sub-folder then the square will show the top


TestPlan

diagonal as green and bottom half blue. Conversely if there are none ‘Open’ in the sub-folder but there are ‘open’ tasks in the parent folder then the split of colour will be reversed with the top half being blue and the bottom half green

PC File View This option allows you to change the view in the Details

Pane when PC file has been selected to show full details (including modified date, Path and computer name that attached the item) or simply a large/Small Icon.

Copy / Paste Specify the level of information that should be

transferred with the item when a Folder, Task or Defect is copied to a new location.


TestPlan

User Tasks

The User Tasks pane enables task management between resources. Within the User Tasks Pane, all resources assigned to the plan will appear with the number of allocated and completed tasks shown as a prefix to the resource name. If you select a resource the corresponding tasks allocated to the resource will appear within the Main pane. If you would like to see all the un-allocated tasks simply click on the plan name at the top of the resource list in the user Tasks pane and the un-allocated tasks will be listed in the Main pane. To re-allocate a task you can drag and drop the task from the Main pane to the target resource listed in the user tasks pane.


TestPlan


TestBench-PC

2 TestBench-PC

Introduction More and more companies are recognising the need for effective software testing and realise that to achieve it requires tools such as Original Software’s ‘TestBench’ – a unique software testing tool. Without TestBench, developers have to manually verify test results, or use tools that are limited to the playing of scripts and the automatic comparison of screens. A total approach to testing is however required, concerning all aspects of the software, from screens to reports, database and performance. The TestDrive-Green and TestDrive-Gold components provide easy to use script capture, playback and Screen compare. When used on an Oracle or iSeries server, TestBench is also able to focus on the ‘invisible’ underlying system database as well as the ‘visible’ system aspects. Errors in the database are harder to find than screen errors and are more difficult to correct and retest if found, and yet can make business critical systems unusable for days. And, with the database in better shape, it also means that the final user acceptance testing phase isn’t going to be hijacked by fundamental code quality issues. So, overall IT service standards are enhanced and user testing stays correctly focused upon ensuring that business needs are satisfied. TestBench combines wide-ranging functionality with inbred ease-of-use, to encourage consistent, regular and effective use.

System Requirements

Minimum Spec Recommended Spec Pentium III 600 Mhz 64MB Memory

Pentium III 1.0 Ghz 256MB Memory

• Client Access Express V5R1, iSeries for Access with a recent

service pack.


TestBench-PC

Getting Started

When TestBench-PC is launched, the following panel is displayed. The User ID and Password are optional fields and should be entered if your database requires it. For Oracle and SQL Server, if you are using Windows authentication then the User ID and Password should be left blank.

Connection Shows the name of each server for which there

is an ODBC connection available. When a System is selected, an ODBC connection will be made (taking anything from 2 to 30 seconds). Only ODBC Data Sources which include the word ‘TestBench’ will be displayed.

Library If using the IBM iSeries as the server this is the

library in which the TestBench application is stored and should be left as the default TB_xPO. For SQL, Oracle and Access this is the name of the TestBench database.

Username The User ID that will be used as the default for

all server connections. Password The Password that will be used as the default for

all server connections.


TestBench-PC

Product Registration

Without any product registration, TestBench-PC simply provides a view of the product structure which includes Projects and Test Cases, and allows these placeholders to be defined and modified. However, in order to create scripts, run tests and manage the database, one or all of the following products should be registered.

• TestDrive-Gold – Record and play back scripts over Windows and Web applications.

• TestDrive-Green – Record and play back scripts over iSeries applications.

• TestDrive-Assist – Make use of the manual testing functionality to document screen and database test results.

• TestBench for Oracle – Manage an Oracle database by extracting test data and rolling back changes made as a result of testing and run integrated tests which provide database and log information in addition to the visual layer testing.

• TestSMART – Create optimized variable data transactions for use during testing.

The following steps can be used to register any of the above products. 1. Click on the ‘Help’ menu option at the top left of the TestBench-PC

panel. 2. Click on the ‘About’ option. The following screen is displayed

showing which of the products have already been registered.


TestBench-PC

3. Click on the ‘Register’ button to access the following screen into

which the product validation code can be keyed. This code should be obtained from your supplier. Click on the ‘Details’ button to list out the information that will be required by your supplier before a code can be provided.


TestBench-PC

NOTE: If no valid licenses exist for TestDrive-Gold or TestDrive-Green, Projects and Test Cases can be viewed and maintained within TestBench-PC but no Scripts will be displayed and new Scripts cannot be recorded.


TestBench-PC

TestBench-PC Panel The following panel is displayed after you have made your selections on the Data Source Connection panel. The panel can be re-sized as required.

Menu

File Select the ‘Exit’ option to close the TestBench-PC application, in which case a confirmation screen is displayed.

Help Ensure Help is installed on your PC then select the

‘Help Topics’ menu option to view the TestBench-PC help text in Adobe PDF format. Select the ‘About’ menu option to access registration information as described in the previous section.


TestBench-PC

Toolbar

Show Types Filter the list of TestBench components to only those of a specific type. If either TestDrive-Green or TestDrive-Gold scripts are selected while viewing Test Cases and other iSeries components, the list will be filtered to show only Test Cases, with those which do not contain any of the requested script type greyed out.


down into Test Cases to display a list of scripts and also move back up to a higher level as shown in the above display. The back button displays the previous component list and can continue to be pressed until the original display is reached.

Go up one level This button is used to return to the higher level

component list until the database level Project list is displayed.

Refresh Re-lists the components to include any new



Search When this option is selected a new tab is opened

within the TestBench-PC window asking you to enter part of the name and type(s) of object you are looking for. Results are displayed within the window after you click on ‘Find’. See the following section for more information.


TestBench-PC

Search

The following panel is displayed in an additional tab when the Search button is clicked on the main Project Explorer form. It is possible to have multiple search forms open in a single TestBench-PC session.

Text Search Key the full or partial text string that you wish

to search for within the selected component names.

Close Close the Search form. Find List all of the components of the selected types

whose name contains the text string. The list of types varies according to the type of component that is applicable on your chosen server.

Right click an item in the Search form to obtain the following options. Edit Open the relevant maintenance panel or product

for the item type. Locate in Explorer Position the Project Explorer panel and place

this item in focus. Delete Remove this item.


TestBench-PC

Home Tab

Click on the far left tab to display the Announcements Area of the Original Software web site. All of the latest product news can be viewed here and it is also a point of contact for support and sales staff at Original Software. If this page has changed since you last opened TestBench-PC you will be defaulted to this tab on entry, thereafter it can be viewed at any time by clicking on the tab. Select your country of residence at the top of the page in order to display any location specific news.


TestBench-PC

Main Panel The main panel consists of four key areas under the toolbar and toolbar icons. The options and information displayed in the three left hand panels is dependant upon the component currently in focus. There are three tabs, Home, Project Explorer and Test Environments, but the Test Environments tab is only visible when TestBench-PC is installed on an Oracle server. • The main component panel is split into two lists. The list of available

Projects or Test Environments is displayed in the left hand panel, each of these can be expanded to show the Test Cases or Checkpoints within. Click on either a Project, Test Case or Test Environment to populate the right hand panel with the components stored inside it.

• The ‘Actions’ area contains all of the options which relate to the

component in focus. For example, if a Project is highlighted then the Actions panel can be used to Edit, Delete or maintain Notes for the Project. These options are also available via a right click menu.

• The ‘Commands’ area can be used to manipulate the contents of the

component in focus. For example, if a Project is highlighted then the Commands panel can be used to add a new Test Case, Action Map, Variable Data Set or Data Rule (if a TestBench for Oracle license is registered), all of which reside within a Project. These options are also available via a right click menu.

• The ‘Information’ area displays additional details for the item in

focus, for example the description of the item and the date on which it was created.

If the server is an iSeries and TestBench security has been activated, if a User attempts to use any of the options their authority will be checked and a message displayed if they do not have the required authority for the function or Project.


TestBench-PC

Main Panel – Database View

A view similar to the following is displayed when the TestBench database name is highlighted.

Commands New Project Add a new Project, you will be required to enter

the Project name and description.


TestBench-PC

Main Panel – Project View

A view similar to the following is displayed when a Project is highlighted.

Project Actions To gain access to the following functions either click the options in the Actions panel or right click the Project name on the display list. Edit Change the Description for the selected Project. Notes Edit the notes associated with the Project - see later

section for more information on using notes. Delete Remove all information associated with the selected

Project, including Test Cases and Results. Confirmation will be required.

Create Launch Files

Launch files are used to support integration with Mercury Quality Center and can also be used if you


TestBench-PC

want to launch a particular Script, Map or set of results without going through TestBench-PC. This option can be used to create a launch file for all such objects within the Project. The launch files are created in a folder called My Original Software\Launch Files in the MyDocuments folder on the PC. To use it in Quality Center simply add the file as an attachment as you would any other PC file. To launch outside of Quality Center simply right click the file and select the ‘Launch’ option. Launch files can also be created by right clicking a Test Case, Script or Action Map. They can also be used to playback Scripts and Action Maps in unattended mode, see later section for more information.

Commands New Test Case Add a new Test Case, see later section for more

information. New Action Map Launch Action Map and create a new Map. See

separate Action Map chapter for more information.

New Variable Data Create a new variable data set, see separate

section in this chapter for more information. New Data Rule Create a new Project level Data Rule, see

separate section in this chapter for more information. (TestBench for Oracle only)

New Data Case Create a new Data Case to extract some test

data, see separate section in this chapter for more information. (TestBench for Oracle only)


TestBench-PC

Main Panel – Test Case View

A view similar to the following is displayed when a Test Case is highlighted.

To gain access to the following functions either click the options in the Actions panel or right click the Test Case name on the display list. Test Case Actions Edit Change the Description for the selected Test Case. See

later section for more information. Copy Copy the selected Test Case to a new Test Case in the

same or any other existing Project. Notes Edit the notes associated with the Test Case - see later

section for more information on using notes. Delete Remove all information associated with the selected

Test Case, including Results. Confirmation will be required.


TestBench-PC

Create Launch Files Launch files are used to support integration with Mercury Quality Center and can also be used if you want to launch a particular Script, Map or set of results without going through TestBench-PC. This option can be used to create a launch file for all such objects within the Test Case. The launch files are created in a folder called My Original Software\Launch Files in the MyDocuments folder on the PC. To use it in Quality Center simply add the file as an attachment as you would any other PC file. To launch outside of Quality Center simply right click the file and select the ‘Launch’ option. Launch files can also be created by right clicking a Project, Script or Action Map. They can also be used to playback Scripts and Action Maps in unattended mode, see later section for more information.

Commands New Gold Script Launch TestDrive-Gold in order to record a new

Script. Please read other chapters in this publication for more information on using TestDrive-Gold.

New Green Script Launch TestDrive-Green in order to record a

new Script. Please read other chapters in this publication for more information on using TestDrive-Green.

New Data Rule Create a new Test Case level Data Rule, see

separate section in this chapter for more information. (TestBench for Oracle only)

View Results Display the results list in a separate tab for the

selected Test Case. Includes an indication of how many results are available to view within brackets. See later section for more information.


TestBench-PC

Test Case Maintenance

The following screen is displayed when either the New or Edit options are taken for a Test Case. The Protection and Data Rules options are only available when used with Test Cases on the iSeries or Oracle. Timeline can be used on an Oracle server only and when a valid TestBench for Oracle license exists. Error Severity is only applicable to iSeries installations.

Code The Test Case Identifier which must be unique within

Project. This field cannot be changed when in Edit mode.

Title The Description of the Test Case which can be a

maximum of 40 characters. Scope Choose whether the database updates of the programs

running on the server are to be stored by TestBench in the results database and optionally removed, creating a form of data protection. The choices are;-

*NONE No files are protected. The files to be used and updated are those found in the library list, or


TestBench-PC

accessed by the programs on the server. *ENV Use in conjunction with the

‘Environment’ option to specify a Test Environment to be used when running the Test Case. This provides database results analysis and data protection. This option is only available on the iSeries and on Oracle when a valid TestBench for Oracle license exists.

Environment The name of the Test Environment which contains the

list of libraries for which database updates will be monitored and stored in the Test Case results database. All file changes made as part of the test can optionally be removed, creating a consistent starting test database for future test runs.

Data Rules Determines which Data Rules will be executed during

an Integrated Test Run on an Oracle or iSeries database, provided a valid license exists.

Error Severity A warning message will be created in the Test Run

results on the iSeries if any job log messages greater than this severity level were encountered. This option is not available on any other platforms.

Timeline Generate a chronological view of Screens, Input,

Database activity and Log entries for integrated tests on TestBench for Oracle.


TestBench-PC

Main Panel – Action Maps View

A view similar to the following is displayed when an Action Map is highlighted.

To gain access to the following functions simply select the option from the Actions panel or right click the Action Map from the display list. Action Map Actions Edit Launches the Action Map product. For further details

please read the separate chapter in this publication related to Action Maps.

Copy Copy the selected Action Map to a new Action Map in

the same or any other existing Project. Notes Edit the notes associated with the Action Map - see later

section for more information on using notes. Delete Remove the Action Map from the Project. This will not

delete component objects which exist in their own right.


TestBench-PC

Confirmation will be required. Create Launch File Launch files are used for two purposes. They support

integration with Mercury Quality Center and enable you to launch a particular Map without going through TestBench-PC. To use the file in Quality Center simply add it as an attachment as you would any other PC file. To launch outside of Quality Center simply right click the file and select ‘Launch’. By specifying additional options in the wizard that is displayed launch files can also be used for unassisted playback via a scheduler. See the later section in this chapter for more information.

Commands View Results View results for all previous runs of this Action Map.

See later section for more information.

Main Panel – Variable Data View

A view similar to the following is displayed when a Variable Data Set is highlighted.


TestBench-PC

To gain access to the following functions simply select the option from the Actions panel or right click the Variable Data Set from the display list. Edit Change the data in the Variable Data Set. Copy Copy the selected Variable Data Set to a new Variable

Data Set in the same or any other existing Project. Delete Delete the Variable Data Set from the Project.

Main Panel – Script View

The Scripts are displayed from the selected Project and Test Case in the list. TestDrive-Green and TestDrive-Gold scripts can be identified using the different colour screen icon that appears to the left of the script name.

To gain access to the following functions simply select the option from the Actions panel or right click the Script from the display list. Script Actions


TestBench-PC

Edit Launches the Script editor associated with the selected

Script – for details please read the separate chapter in this publication related to TestDrive-Green or TestDrive-Gold.

Copy Copy the selected Script to a new Script in the same or

any other existing Project. Notes Edit the notes associated with the Script - see later

section for more information on using notes. Delete Delete the Script from the Test Case. Create Launch File Launch files are used for two purposes. They support

integration with Mercury Quality Center and enable you to launch a particular Map without going through TestBench-PC. To use the file in Quality Center simply add it as an attachment as you would any other PC file. To launch outside of Quality Center simply right click the file and select ‘Launch’. By specifying additional options in the wizard that is displayed launch files can also be used for unassisted playback via a scheduler. See the section in the TestBench-PC chapter for more information.

Commands View Results View all Results for this Script - see later section for

more information on using Results.


TestBench-PC

Variable Data Sets Variable data sets can be viewed by highlighting the Project name on the main TestBench-PC panel.

Edit Variable Data

The following panel is displayed when a Variable Data Set is edited or a new one is created.

Right click on the single grey box in the top left of the Edit Variable Data window to begin creating variable data fields and transactions for new Variable Data Sets. The following options are available. Insert Column(s) After Add the specified number of columns (fields)

after the column in which the right click occurred.

Insert Row(s) After Add the specified number of empty rows

(transactions) after the row in which the right click occurred for which data can then be keyed.


TestBench-PC

Insert Clipboard Rows If you have data in another windows application, such as a spreadsheet, you can use copy and paste to populate the variable data field names and values. You will be asked whether or not the data being copied contains a header row (field names) or only the transaction data.

Column Options

Copy Column Add the contents of the selected column to the Clipboard.

Paste Column Insert the data in the previously copied column

into the column where the right click occurred.

Row Options

When at least one row has been added some additional options are available on right click on the transaction numbers. This screen is cursor sensitive; the options listed apply to the row on which the right click occurred. In addition to the right click options, rows can be moved simply by left clicking the transaction number and dragging to the desired new position. Multiple rows are selected by using left click in combination with Shift/Ctrl.


TestBench-PC

Remove Row(s) Remove the selected transaction. Copy Row Add the contents of the selected row to the

Clipboard. Paste Row Insert the data in the previously copied row into

the row where the right click occurred.


TestBench-PC

Data Options

This screen is cursor sensitive; the options listed apply to the cell on which the right click occurred. Multiple cells are selected by using left click and dragging the cursor.

Copy Add the contents of the selected cells to the

Clipboard. Paste Insert the data in the previously copied cells into

the cell where the right click occurred. Clear Remove the contents of the selected cells.


TestBench-PC

Edit Column Details

The following screen is displayed by either double clicking a column header or by right clicking and selecting the Edit Column option.

Name Define a new Variable Data field name which

can be a maximum of 10 characters long. Type Used for editing purposes only on the Edit

Variable Data screen to control which characters can be keyed into the cells. The choices are Character, Upper Case, Numeric and Decimal. For numeric values only the keys 0 - 9 and backspace are allowed. For decimal fields the characters. , - are also allowed.

In addition for decimal type fields a special

value of =date can be used. This will populate the data with today’s date. The default format for this date is yy/mm/dd but this can be changed by keying the format into the expression as follows:


TestBench-PC

=date (dd/mm/yy) The valid format codes are listed below and any

separator characters can be used: dd day portion of date ddd day of the week in upper and lower

case mm month portion of date mmm month in upper and lower case yy two digit year yyyy four digit year A specified number of days, months or years

can be added to today’s date by keying in the following expression:

=date (format) + 15 days A - is valid in addition to a +. The valid operators are day, days, month,

months, year, years. The expression is not case sensitive.

Alignment Used for display purposes only on the Edit

Variable Data screen. The choices are General (numeric values right adjusted and characters left adjusted), Left, Center and Right.

Play empty values When selected, this option will play empty

values into the fields on your script. Auto-increment If the Active box is checked, the value in the

first transaction for the column will be duplicated into all other columns. If the Value field contains an entry other than zero (only


TestBench-PC

valid for numeric or decimal fields) then each transaction will be incremented by this value. If the initial value is blank then the numbering will start from 1. If any values already exist in any other rows then the numbering will re-start in that position. The same occurs when incrementing is already active and a value is changed.

On the following screen, the blue arrow

indicates values that have been automatically calculated and those with no arrow have been manually keyed in.


TestBench-PC

Data Rules Data Rules represent a key component of TestBench as they allow the database effects of a test run to be proactively checked without requiring further action by the user. Data Rules are available both on the iSeries and on Oracle if a valid TestBench for Oracle license exists. However, if the iSeries is the server then Data Rules must be defined and their results viewed on the server (see the Testing chapter of the TestBench User Guide for more information), only TestBench for Oracle Data Rules can be managed using TestBench-PC. In TestBench for Oracle, Data Rules can be defined at the Project level or for an individual Test Case. If defined at a Project level then they will be automatically applied to all Test Cases, unless the option on the Test Case is set to exclude them. Data Rules can be defined for any table and there is no limit to the number of Data Rules that can be defined for a single table. Data Rules can be used in all aspects of testing, but they are often constructed by Systems Analysts, Database Designers and Technical staff. However, their power to validate can be maximised if they are also applied during later phases of testing such as regression or UAT. With TestBench this does not mean the persons testing at this stage have to understand or be familiar with the rules, as the tests they perform can still benefit from the knowledge invested in the rules by others. For this reason, it is recommended to define rules at the highest appropriate level (Project) whenever possible and have only very specific rules defined at the Test Case level.

How Data Rules Work

A data rule consists of two main components - WHEN rules (selection conditions) and TEST rules (rules for validating data). The WHEN portion of the rule is used to identify which rows the TEST portion can be applied to. This means that different rules can be set up for data in different conditions, for example one rule for Invoices and another for Credit Notes. If there are no WHEN conditions, the rule will apply to all rows. A data rule is only applied to tables which have been updated by the test. The Test Case within which the script is stored must be using


TestBench-PC

Environment protection and the tables being updated must be included within the Schema defined against the specified Environment. At the end of each test, Data Rules are applied and checked against the database effects captured from the test and any discrepancies are reported as Warnings. The full details of the discrepancy can be viewed side by side with the Data Rule in TestBench-PC results.

When is a Data Rule Checked?

1. A database effect must be generated in the Environment associated with the Test Case as a result of a write, update or delete operation.

2. The rule must be active. The Test Case contains an option to specify whether Project, Test Case, All or No rules should be applied.

3. The data in the row must match any selection (when) conditions for the rule.

If the above conditions are met for the table in the rule, the rule checking will be applied at the end of the test process.

Data Rule Maintenance

An existing Data Rule can be changed by either right clicking and selecting the Edit option from the menu or selecting the Edit option from the Actions area. To create a new Data Rule, click on the Project or Test Case and select the New Data Rule option from the Commands area or the right click menu. When in Add mode the following panel is displayed. When editing an existing Data Rule you are defaulted to the final screen in the wizard where the When and Test conditions for the Data Rule are defined.


TestBench-PC

Code The user defined name of the Data Rule, to a maximum

of 10 characters. Title Description of the contents of the Data Rule. Schema The schema within which a copy of the table resides

over which the Data Rule will be built. This is used specifically for retrieving the definition of the table at maintenance time. When the test is executed, the Data Rule will be applied to the updated table regardless of the schema in which it is found.

Click the Next button in order to display the following screen where the table is selected.


TestBench-PC

Click on the table over which the Data Rule will be built and then click on Next to define the Data Rule details. The top half of the screen defines the optional When clause, which determines under which conditions this rule will be applied. The second half of the screen is where the Test clause, the detail of the Data Rule checks are defined.


TestBench-PC

Clause The first row in the two tables has a defaulted value of

When and Test respectively. For all of the other rows the valid values are ‘And’ and ‘Or’.

Value 1 This can be either a field on the table being check or the

special value of ‘Operation’, both of which can be selected from the drop down list that is displayed by clicking in the cell on the grid. ‘Operation’ will check whether the table activity in question was a Write, Update or Delete, depending on the Value 2 selected.

Condition Choose from a drop down list containing =, >, <=, <,

>=, and <>. This is used to compare Value 1 to Value 2.

Value 2 This can be either a field on the table being compared or

a fixed value against which the field in Value 1 should be compared. If Value 1 is ‘Operation’, this must be


TestBench-PC

either WRITE, UPDATE or DELETE which can be selected from the drop down list.

The Save button is only enabled when the Rule has been entered correctly, any fields in error are highlighted in red. Press the Back button at any time to modify entries on a previous screen, click on Save to store the new Data Rule or Cancel to discard any changes made.


TestBench-PC

Test Environments When a valid TestBench for Oracle license exists, an additional Test Environments tab is available in TestBench-PC. Test Environments consist of a list of Schemas which contain the test data for an application. If a Test Environment is defined for a Test Case, when any scripts stored within that Test Case are played back with the ‘Activate Test_IT’ option checked, results in the form of database effects and data rules are reported. Test Environments also enable data that has been changed by a test to be rolled back to a previous state, thus allowing you to run a program many times knowing that the starting point of all the tables will be consistent. This capability is essential if you are using a ‘record and playback’ tool such as TestDrive-Gold to exercise your interactive programs, as without a data starting point identical to that when the script was created, it is inevitable that many differences will be found during the execution of the script. This can be done even if TestBench is not being used to initiate tests via Test Cases and Scripts, but when testing is being performed in your application directly.

How to Set Up and Use Test Environments

1. Get your data to the state you require (we recommend also taking a back up).

2. Create a Test Environment, specifying the schemas that make up the environment.

3. Define and activate at least one Checkpoint, to identify to TestBench the current state of the data within the environment.

4. Against your Test Case, change the Scope option to *ENV and name the environment you are using.

6. Perform your first set of tests or execute your scripts. 7. Create and activate a new Checkpoint to capture this point in time. 8. Continue testing and creating Checkpoints as required. 9. The test results will include file effects and hence Data Rules may

also be checked. 10. If you need to reset the database at any time, use the rollback option

against a selected Checkpoint.


TestBench-PC

Database View

A view similar to the following is displayed when the TestBench database name is highlighted.

Commands New Environment Add a new Test Environment, see later section

for more information.


TestBench-PC

Test Environment View

Click on a Test Environment name to display a screen similar to the following.

To gain access to the following functions either click the options in the Actions panel or right click the Test Environment name on the display list. Test Environment Actions Edit Change the Description for the selected Test

Environment. See following section for more information.

Delete Remove the selected Test Environment. Confirmation

will be required. Commands New Checkpoint Create a new Checkpoint description, see later

section for more information.


TestBench-PC

Test Environment Maintenance

A panel similar to the following is displayed when either a new Environment is created or an existing one is changed.

Code This is a mandatory field which can be a maximum of

10 characters. It cannot be changed when in Edit mode. Title A description of the Test Environment. Schema Determines which schemas will be controlled by this

Environment. Any tables within these schemas can have their changes rolled back.


TestBench-PC

Checkpoints

The following panel is displayed when the ‘New Checkpoint’ option is selected. A checkpoint consists simply of a description which can be changed in edit mode at any time without affecting the operation of the Checkpoint.

When a checkpoint is first added it is not active and the rollback option is not available, as shown for Checkpoint number 3 below. Only when the ‘Activate’ option is selected can any changes made to the database since the activation be rolled back. It is however possible to roll back to an earlier active checkpoint.


TestBench-PC

Checkpoint Actions Edit Change the Description for the selected Checkpoint. Delete Remove the Checkpoint. Commands Activate Access the logs and store the current position of the

database so that at any point in the future the rollback option can be selected to reset the data to its current state. When a Checkpoint is activated, the date and time is logged and displayed on screen. Checkpoints must be activated in ID sequence, for example you cannot activate a Checkpoint if earlier inactive Checkpoints exist. NOTE: If you re-set an active Checkpoint, any later active Checkpoints will be rendered inactive. This action is prevented if any earlier active Checkpoints exist to avoid the loss of any intermediate database updates.

Rollback All database changes made after the specified

Checkpoint was activated will be removed. This option will not however undo table deletions by re-creating the object, and those added since the Checkpoint was


TestBench-PC

activated will not be removed. If you ‘ALTER’ a table, any data operations after the ‘ALTER’ for the table will be rolled back but anything prior will not. It is possible to have several Checkpoints specified and active at one time. If rollback is performed for the Checkpoint which is not the latest in the series, any subsequent Checkpoints will be rendered inactive.


TestBench-PC

Launch Files Launch files are used for two purposes. Firstly they support integration with Mercury Quality Center and enable you to launch a particular Script, Map or set of Results without going through TestBench-PC. To use the file in Quality Center simply add it as an attachment as you would any other PC file. To launch outside of Quality Center simply right click the file and select ‘Launch’. Secondly they enable complete information to be specified which facilitates the fully automated execution of a Script or Action Map in unattended mode. This means that a scheduler can be used to launch a series of tests at a specified date and time.

Maintenance

Launch files of the first type can be created for an entire Project or Test Case by right clicking the Project or Test Case in TestBench-PC and selecting the ‘Create Launch File’ option. The launch files are created in a folder called My Original Software\Launch Files in the MyDocuments folder on the PC and have the extension .TBC. Files of both types can be created for individual components by either right clicking a Script or Action Map in TestBench-PC, or by selecting the option from the File menu when the Script or Action Map is open. The following wizard is then used to specify the required parameters.


TestBench-PC

Play This option determines which type of launch file will be

created. If this option is unchecked, when the file is launched the relevant Script or Map will be opened and can be edited or executed from there. If the option is checked, when the file is launched the Script or Map will be automatically executed. Checking this option will cause further wizard screens to be displayed which describe how the playback will occur and which results will be saved.

Map contains If the launch file being created is for an Action Map,

this option will automatically be populated with the types of scripts contained within the Map. This is important because it controls which options will be displayed on the following wizard screens. It will only need to be modified if you are editing an existing launch file and the components of the Action Map have changed.

If the Play option is checked, click Next to access the next screen of the wizard, otherwise click Finish.


TestBench-PC

The first three ‘Target’ options are only displayed for TestDrive-Gold scripts or Action Maps which contain them. The last two ‘Target’ options are only shown for TestDrive-Green scripts or Action Maps which contain them. Attachment This can be used to override any settings stored against

the Script or Map to specify which application scripts will play back against.

Attach means searching for an application that matches

the criteria specified by the Application and Caption properties below. At least one of these properties must be entered, but if both are keyed then both must match. When searching for a match for a running application, there must be only one match, if there is more than one or none that match then a warning is issued and playback will halt.

Launch means that the application specified in the

Application field below will be launched. Specify the full path, the executable name if it is found in the System path, or the name of a URL in which case a browser is opened and a navigation to the URL


TestBench-PC

performed. Map/Script setting means that if the script is set to

launch, the application defined in the Command Line of the script will be launched. If it is set to attach, it will attempt to find a running application which matches the application that was running when the script was recorded. Matching is performed by comparing the caption of the first screen in the script with the application that is running, the text must be exactly, although the matching is not case sensitive and ignores leading or trailing blanks. Playback is halted if no match is found.

NB If this option is specified for a Map but the Map has the option ‘Show target application prompt’ checked, the playback will fail because the prompt cannot be displayed for an unattended playback.

Application If either Attach or Launch is specified in the

Attachment option above, this is the application over which the script will be played. It can be the full path, the executable name or the name of a URL.

Caption If either Attach or Launch is specified in the

Attachment option above, this is the caption of the application over which the script should be played. Wildcards can be used and if an executable is being specified, include just the name and not the full patch.

iSeries session Use named session means that the session specified in

the ‘Session name’ below will be the one over which any TestDrive-Green scripts will play back.

Use first free session does not require an entry in the following field and means that the first available 5250 session will be used.

Session name Specify the short name of the 5250 session over which

any TestDrive-Green scripts will play back if ‘Use named session’ is specified above.

Keep results Determines under which conditions results from the

unattended playback will be stored. Choose from ‘Always’, ‘Never’ or only ‘If errors reported’.


TestBench-PC

Click Next to display the final screen of the wizard where the parameters required to connect to the TestBench database at playback time are specified.

Library/Database If using the IBM iSeries as the server this is the


Connection Use existing DSN means that the connection

parameters from the ODBC connection that was selected when you logged into TestBench-PC will be used at playback time. This does require that the name of the ODBC connection must be exactly the same on the PC that initiates the playback.

Stored connection parameters can be used as an alternative to the above if there may not be an exact match to the ODBC connection on another PC. If this option is selected, the connection parameters from the current ODBC connection


TestBench-PC

will be stored and used. User ID/Password Defined in DSN means that the User ID and

Password that will be used as the default for the server connection at playback time will be taken from the current connection.

Defined below enables an alternative User ID and Password to be defined and used at playback time.

Click Finish to store the changes made in the wizard and create or update the TBC file. You will be prompted for a location in which to save the file. Once the TBC file has been created, either double click it or right click and select Edit to change any of the above parameters.

Execution

Once a launch file has been created it can be launched in one of two ways.

• Right click the file directly and select ‘Play’. This will initiate an immediate playback of the Script or Map.

• Launch the file via a command interface. The command can be run from a scheduler to enable Scripts or Maps to be played back at a specific date and time. Do this by calling the Play.exe program which can be found in the location C:\Program Files\Original Software\Programs and pass the name of the file as a parameter. For example:

C:\Program Files\Original Software\Programs\Play.exe "C:\My Documents\Unattended play files\Order Entry Regression.TBC"

Results

Every playback which successfully initiated will have its results stored in the TestBench database. Information about all unattended runs is also written to the Windows Event Log which can be accessed from Control Panel / Administrative Tools / Event View and selecting the Application item in the panel. A log entry is created every time a playback begins and


TestBench-PC

ends and details of any errors and result Run Numbers are also logged. There are three types of event; Information, Warning and Error. If a Script or Map starts and ends without errors, this is logged as an Information event. If playback completes but errors such as screen differences are reported, this is a Warning event. If a Script or Map is unable to start or fails to complete this is logged as an Error and the reason for the error is added to the log.


TestBench-PC

Test Case Results The results of a Test Run are stored in the TestBench database by reference to the Test Case and a unique run number. Select the View Results option for a Test Case or Script to open an additional TestBench-PC tab which lists all Test Runs for the selection. If a Results tab is already open, any data contained within it is replaced with the new list. Use the Close button at the bottom right of the panel to close down the Results tab.

Product/Name/User Selection At the top of the results three drop down boxes

are available to provide the ability to refine your view and selection criteria by Product, Name of the Script, Map or Application, or User Profile who ran the test.

Test Status Describes the current status of the Test Run. The

Warn column will be either blank or contain the text ‘Warnings’ to indicate that either there was an issue with the execution of the Test or that some of the expectations were not met. Run provides the latest status of the Test Run, values can range from Queued and Running through to


TestBench-PC

Abnormal, Cancelld or Complete. Initiated Details about who initiated the test and at which

date and time the test started. Pass This column indicates whether the Test Run has

passed or failed. If the status is N/A this indicates that the Test Run has had neither value assigned.

Cleared? This indicates whether low level details of the

Test Run have been cleared, an option which appears on the right-click menu for a Test Run.

Name This column can contain one of four values

depending on the type of test that was performed. It could contain the name of the script which was re-played during this Test Run. There will only be an entry here if the script results were saved, otherwise the column is blank. Alternatively for an Action Map this would be the name of the Map. Lastly for results generated by TestDrive Sidebar, this column contains the name of the application to which the results relate.

Result options

The following options are accessed by right clicking the mouse over the required Test Run from the list. Details This includes several options which display the

following detailed results for a Test Run:- - Summary - Warnings - Timeline - Screens - Database - Data Rules - Server - Log - Response


TestBench-PC

- Pass/Fail Not all of the above are available for all connection

types (iSeries, Oracle, SQL and Access). See the following sections for more information.

Notes Edit the notes associated with the Test Run - see later

section for more information. Report Produce a test report for the Test Run - see later section

for more information. Clear The ‘Clear’ option will delete some of the information

associated with a Test Run, leaving a reduced record that the run took place. This option will permanently remove for example file and data area effects, data rules and screen results associated with the Test Run. A confirmation screen is displayed before the clear takes place.

Delete The ‘Delete’ option will delete permanently all

references to the Test Run from inside TestBench. A confirmation screen is displayed before the delete takes place.

Open Script/Create Script from results If the screen results were saved, this option can be used

to open a copy of the script which was executed. This is especially useful if the current version of the script in the database has changed since the test was executed. The script can then be saved for future use if required.

If the results were generated as part of a manual test,

where no script is in existence, the option to create a script from the results is available.


TestBench-PC

General points for run results detail screens

The sub-run selection is simply taken from the drop down menu at the foot of the panel. To activate this drop down the ‘All Processes’ check box must be un-checked and the Refresh button clicked. All Screens in the result details have the ability to pass to previous and next test runs. Simply click on the Icon at the bottom of the panel to display the desired run information. Refresh Update the display with the latest information after

modifying the Process selection. Close Close down the tab within TestBench-PC.

Summary

The summary provides a view of the Test Run results and Test Case set


TestBench-PC

up. The summary screen is the first tab on the collection of details from the Results list. This details tab holds the high level summary and has the ability to allow a filter view of sub-run activity across the other tabs on this set of results.

Warnings

TestBench will automatically generate warning messages for:-

• Actual screen images different to those expected • One or more Data Rule Failures • Job Log messages higher than a specified severity • User Exit program errors (defined in TestBench) • Parameter Values (defined in TestBench)

All warnings apart from screen differences will only be generated if the Script has been integrated with a Test Case.


TestBench-PC

Timeline

The Timeline tab is only available if using TestBench for Oracle. It shows a chronological view of all screens, input, database effects and log entries. Each screen in the script is listed. The screen can then be expanded to show its input, provided screen results were saved at the end of the test. Additionally two icons overlaying the green tick, red cross or orange dash for each screen indicate the presence of other data. An orange circle signifies that some database activity occurred at this point in the test while a yellow triangle with a black exclamation mark highlights the presence of some log entries.


TestBench-PC

Screens

Display the detailed results for screens from the Test Run or Sub-Run using the product which created the script, either TestDrive-Green or TestDrive-Gold. Please refer to the relevant chapters for more information on these products.


TestBench-PC

Database

If a Script has been integrated with a Test Case on the iSeries or Oracle and this Test Case uses Environment Protection, all database updates made by the server programs in the associated Environment are tracked and stored by TestBench. This option provides a summary display of this database activity. In addition, at any time a Checkpoint can be defined for a Test Environment and at any future point in time the User can rollback changes to files and data areas up to the specified Checkpoint. This enables the same test to be repeated without it being necessary to re-create the initial test database. The number of file updates which have been removed or rolled back are also shown on this panel. To see record level details including before and after images you need to select the file from the top panel and then the Row ID from the lower left panel. Each difference is denoted by the update symbol to the left of the detail row.


TestBench-PC

Data Rules

Although Data Rules can be used on both the iSeries and Oracle, they can only be maintained in TestBench-PC on Oracle and therefore this tab is not visible when the server is the iSeries. All of the Data Rules for this Test Case and the Project in which it resides are listed. The symbol to the left of the row indicates whether the rule has passed (grid with a green tick), failed (grid with a red cross), or was not applied (empty grid) due to the fact that the table over which it was based was not updated by the test. The Rule Filter at the top of the screen can be used to control which of these rule types are visible in the list. Click on a rule in the list to display the rule definition to the right of the screen. The conditions which have caused the rule to fail are highlighted in red. The rows in the table which have failed the rule are listed in the bottom left panel. Click on one of these to display the database effect, with the failed columns also highlighted in red. The Field Filter at the top of the screen can be used to show only Passed, Failed or All fields.


TestBench-PC

Server

Every server program on the iSeries initiated by the test is listed on the screen above along with information about the program execution. This information includes Call Sequence, Start Time, Elapsed Time, CPU Cycles and Auxiliary I/O.


TestBench-PC

Log

All iSeries messages which have been received by the Job Log or Oracle SQL errors for this test can be viewed here.


TestBench-PC

Response

The performance statistics are a combination of both server and browser activity and can be displayed in either a tabular or graphical format. When viewing TestDrive-Gold results for browser tests the bar can be spilt into three separate sections to show transmit, server and build times. Response Complete time taken in seconds for the screen or URL

to appear on screen after the last navigation. This is equal to the sum of the transmit and build values. The server component is included within these as there is an overlap in activity.

Transmit Seconds taken since the last navigation for a response to

be received from the server, TestDrive-Gold runs only. Server The time taken in seconds for any server components to

run, TestDrive-Gold runs only. Build The time difference in seconds between a response

being received from the server and a screen or URL


TestBench-PC

being completely built. TestDrive-Gold runs only.

Pass/Fail

When a test is executed, it is possible to define a list of Test Items against a Test Case which at the end of the test can be passed or failed. In addition to this, the Test Run as a whole can also be given a status of Pass or Fail. These values can be updated on the following screen.

Current Run Status Display either Pass, Fail or N/A (not yet

defined) to represent the relative success of the Test Run.

Change Run Status Change the current status of the Test Run to

either Pass, Fail or N/A. Once the status has been altered, the comments box is enabled and a comment must be entered before the status change can be updated.

Update Status Click this button once the new status and

comment have been entered in order to update the current status of the Test Run.


TestBench-PC

Pass/Fail History Displays the details of all previous Test Run

status changes. Test Items Change the status and optionally add comments

for each Test Item defined to this Test Run. There is no history display for Test Item status changes. There is also no requirement for the Test Items to be updated prior to updating the status of the Test Run as a whole.


TestBench-PC

Action Map Results Select the View Results option for an Action Map to display a list of all Action Map Runs as shown on the following screen. The results are stored in the TestBench database by reference to the Action Map and a unique run number.

User Selection At the top of the results a drop down box is

available to refine your view by the User Profile who ran the test.

The following options are available from the right click menu for an Action Map Run. Map Entries Show the details of the Action Map Run in another tab

as described below. Delete Remove the Action Map Run and all of the Action Map

Entries.


TestBench-PC

Map Entries

Right click any of the Action Map Runs to display the following screen showing results for each individual Action Map entry.

Sequence The order in which the individual Action Entries

were executed. When the sequence numbers are the same it indicates that the entries were part of the same Test Run, for example two scripts running one after the other over the same test process. The number in brackets then further describes the execution order of these entries.

Result options

The following options are accessed by right clicking the required entry in the list. However some options are not applicable to every type of entry and may therefore not always be available. Details This includes several options which display the

following detailed results for a Test Run:-


TestBench-PC

- Summary - Warnings - Timeline - Screens - Database - Data Rules - Server - Log - Response - Pass/Fail Report Produce a test report for the Action Map Entry - see

later section for more information.


TestBench-PC

Reporting The reporting function for a Test Run can be accessed from the Results List panel by right clicking a Test Run or Action Map Run. The options are stored and remembered on each PC.

Title An optional user defined field which appears on

the Cover Page and at the top of each page of the report.

Company The name of the Company by whom the report

has been produced, which appears on the Cover Page and at the top of each page of the report. This is an optional field.

Printed By The name of the person who has generated the

report which appears on the Cover Page and at the top of each page of the report. This is an optional field.

Include cover page If this option is selected, a single page

containing the above three fields and the date


TestBench-PC

will be printed at the beginning of the report. Click Next to display the second screen of the wizard.

Screens All Generate all information including all screen details and database effects for integrated runs.

Screens in Error Generate all information including screen details and database effects for integrated runs, however only include those screens for which differences exist.

Summary Generate only the Run Summary and Run Details sections of the report.

Picture Size Choose between Small and Large pictures.

Small pictures will typically display the Actual and Expected side by side if both exist, whereas large pictures will be displayed one after the other. However this is a guideline only, the report structure is optimized according to the shape of the screen being reported upon. This may mean that although large pictures have been selected, very long and thin web pages


TestBench-PC

might still be displayed side by side. Show For results generated by TestDrive-Gold only,

this option determines whether the additional expected and actual screen pictures showing only the differences are included. The choices are ‘Screens only’ ‘Errors only’ or ‘Screens and Errors’.

Keystrokes For results generated by TestDrive-Green,

choose whether or not to include the additional screen picture containing the input.

File Effects If database effects have been stored for this run,

choose which level of information to include on the report.

Data Rules If Data Rule results have been stored for this

run, choose which level of information to include on the report.

Click the Next button to complete the wizard selections and then the Finish button to begin the report generation. Please note that only the options available on your server are enabled. Once the report has been generated the following screen is displayed. Use the arrows at the bottom of the report to navigate through the report and the magnifying glass to alter the zoom level.


TestBench-PC

Refresh Click this button to re-generate the report. The wizard

is displayed again enabling an alternative set of options to be selected.

Print Print the report. Save Store a copy of the report in pdf format. Close Close down the Report tab of TestBench-PC.


TestBench-PC

Data Cases When a valid TestBench for Oracle license exists, additional options to enable test data to be extracted are available in TestBench-PC. When carrying out testing to ensure that the correct data is being written to a database and that functionally the system is performing as it should, it is not usually practical to perform these tests on large volume files (such as full copies of a live database) as you cannot see the wood for the trees. It is necessary to know what the expected result of any test should be in order to determine whether the test was successful or not, something which cannot be easily defined with large volumes of data. Later, once you are happy that the correct functions are being performed, volume testing has a meaningful place to check performance, capacities and operational/environment issues, but until then, you need small volumes and appropriate data which you can use and re-use. With Data Cases you can automatically define a logical structure of tables, specify selection conditions that give a good mix of transactions or areas of business, and then use Data Cases to build a coherent set of records that meet the required selection, cover the needs of testers, yet do not occupy large portions of valuable disk space. It is easy to reproduce up to date versions of the same data, or to create variations of the data for specific testing projects. Once you have created test tables in the format you require, Test Environments can be used to manage the test data and provide the option to re-set the database to pre-defined check points. To enable a testing process to be fully automated one of the first considerations is the Test Data. Think of it as an asset, do not make random changes to it and keep it safe so you can re-use it at any time, knowing what results it will produce. Any time the data changes you may need to re-check the results of your Test Cases, so the less changes the better.


TestBench-PC

Introduction

There are two steps to performing a data extraction using TestBench for Oracle:

1. Take a copy of the source database (the schema that you wish to extract from) and create the target test database. This is called cloning a schema and is only required if a brand new database is required. Existing schemas can be re-used if the tables are unchanged and you simply wish to update the data within.

2. Create a Data Case and extract the test data.

Both of these tasks are performed from the Data Case panel. This is accessed in a number of ways:

• Highlight a Project and click the ‘New Data Case’ option from the Commands panel.

• Right click a Project and select the ‘New Data Case’ option. • Highlight an existing Data Case and click on the ‘Edit’ option from

the Actions panel.

• Right click a Data Case and select the Edit option.

• Double click a Data Case.


TestBench-PC

Data Case Panel

If a new Data Case is being created, the following panel will be empty.

Toolbar Change Data Source As soon as any option is selected within the

Data Case panel, you are forced to connect to your chosen Data Source, before this has been done this toolbar button will read ‘Connect to Data Source’. Thereafter the source database can be changed by clicking this button. See the following section for more information.

Clone Schema Take a copy of all of the tables in an existing

schema and create a new schema which can then be used as the target database for a data extraction. See later section for more information.

Save Save all changes to the Data Case to the

TestBench-PC database.


TestBench-PC

Execute Run the data extraction to place all selected data into the target database, see later section for more information.

Help Display the TestBench-PC online help text. Information Area Data Case Name In Add mode you should key an identifier for

the Data Case which must be unique within the current Project and is a maximum of 10 characters in length. This field cannot be altered in Change mode.

Data Case Description Key appropriate text to describe the data that

will be extracted by this Data Case. Data Source TNS Name The TNS Name of the source schema from

where data will be extracted. This is displayed here for information purposes and can only be change by clicking the ‘Change Data Source’ toolbar button.

Data Source Schema The name of the schema from where data will

be extracted. This is displayed here for information purposes and can only be change by clicking the ‘Change Data Source’ toolbar button.

Default Target TNS Name The TNS Name of the target schema to where

data will be extracted. This is a default value and can be changed at execution time. It can be different to the Source TNS.

Default Target Schema The name of the target schema to where data

will be extracted. This is a default value and can be changed at execution time.


TestBench-PC

Source Credentials

The following panel is automatically displayed the first time you attempt to interact with a new Data Case session, because no actions can be performed until a connection has been made to the source database. To alter these details once a connection has been established, click on the ‘Change Data Source’ toolbar button on the main panel.

TNS Name The TNS Name of the source schema from

where data will be extracted. Schema The name of the schema from where data will

be extracted. Username The User ID that will be used to make a

connection to the source database. Therefore this user profile must have all appropriate authorities for data extraction to take place. If a username was specified on the TestBench-PC login panel, it will be defaulted here but can be overridden.

Password The Password that will be used to make a


TestBench-PC

connection to the source database. If a password was specified on the TestBench-PC login panel, it will be defaulted here but can be overridden.

Click ‘Next’ to display a confirmation panel. On this panel, click ‘Finish’ to make the connection to the source Schema. A progress bar is displayed while the schema is being analysed, once this has finished and the connection has been successfully established the following panel is displayed. If there were any problems establishing a connection, an error message is shown.


TestBench-PC

Clone Schema

Before a Data Case can be executed, the target schema must exist. A copy of an existing schema can be created using the ‘Clone Schema’ toolbar button, this can then be used to hold the extracted data. Alternatively this option can be used to update an existing schema with new table definitions. Click ‘Next’ on the first screen of the wizard to reach the following panel.

All of the following values are defaulted from the Source Credentials already specified but can be overridden here. TNS Name The TNS Name of the source schema that will

be copied to create the target schema. Username The User ID that will be used to make a

connection to the source database. Therefore this user profile must have at least export authority on the source schema.



TestBench-PC

connection to the source database. Schema The name of the schema that will be copied to

create the target schema. Click ‘Next’ to display step 3 of the wizard.

TNS Name The TNS Name of the target schema to where

tables will be copied. Username The User ID that will be used to make a

connection to the target database. The technique that is used to link the source and target databases when they are on different servers requires that the same User ID is used to connect to both.


connection to the target database. Create new schema/owner as the target If an appropriate schema does not already exist,

specify the name of a new schema and password


TestBench-PC

that will be created by the wizard. All tables from the source schema will be copied into the target. If this option is taken, security settings may need to be modified.

Use an existing schema as the target If this option is selected, all tables in the target

will first be deleted before all those in the source are copied to the target. When this option is selected, security settings are retained.

Click ‘Next’ to display a confirmation screen. When ‘Finish’ is clicked, a progress bar is displayed while the source schema is being cloned and the target tables created. Once this process has finished the following panel is displayed. If there were any problems creating the target schema, an error message is shown.


TestBench-PC

Relationships

When a new Data Case is created, the Relationships panel will be empty. This can be populated manually by right clicking and adding files using the ‘Add Top Level Table’ and ‘Add Child Table’ options, these are described further below. However, a faster method is to use the ‘Auto Analyse’ option from the right click menu. This will automatically add all files in the source schema into the Data Case. Additionally, if the source tables have constraints defined, these will be used to build a relationship tree for the database as shown below.

In the example above, the table OEUNITP is a parent file, OECTYPP is a child of it. OECTYPP is also a parent of OECUSTP. This means that for every record in OECUSTP (Customer table) there must be a parent record in OECTYPP (Customer Type table). Click on any table to populate the right hand panel, this shows which columns in the selected table are used to link to its parent. In the example shown, the Order Lines table is linked to the Order Header by Order Number, although it is possible that the link is made up using more than one field from each file. It is also possible that due to their being multiple constraints on a table, the table may appear in the relationship tree multiple times. In the example, the Order Header (OEORDHP) is not only a child of Customer,


TestBench-PC

but also of Sales Person, Unit and Customer Type. New parent files can be added by right clicking and selecting the ‘Add Top Level Table’ option. The following panel is displayed which lists all tables in the source schema, click on one to select it and then click ‘Finish’.

New child tables can be added to the Data Case by right clicking and selecting the ‘Add Child Table’ option. Step 1 of the wizard lists all tables in the source schema, click on one to select it and then click ‘Next’.


TestBench-PC

On the following screen, the fields which define the link between the two tables are specified. Right click in the Parent Field column to select from a list of fields in the parent table which are the same type as the one in the child table. There is also a ‘Clear’ option on the right click menu which enables a previously defined relationship to be removed. It is possible that more than one pair of fields is required to correctly defined the relationship between the two tables. Once all file pairs have been defined, click ‘Finish’ to add the table to the Data Case.


TestBench-PC

The above screen is also displayed if a table in the relationship tree is right clicked and the ‘Edit Parent Table Relationship’ option is selected. Any table can be removed from the tree by right clicking and selecting the ‘Remove Table’ option. A confirmation screen is displayed prior to the deletion taking place, please note that for parent tables, all children will also be removed. Care should be taken when deleting tables because if a constraint is broken, the data extraction may fail.


TestBench-PC

Data Selections

The purpose of creating the relationship tree above is to ensure that the correct data gets extracted from the source to the target database with the minimum of effort. For each table there are three options which control the data that will be extracted. There are all available from the right click menu for each table: Only Required For parent tables where a child table has a

selection on it, this means that only the data required to satisfy any constraints should be extracted. This is the default value for all new tables when they are added to the Data Case.

All Possible For tables where either there is no parent or no

parent files have selections, this will result in all data being extracted. For child tables where a parent has a specific selection, this means extract all records which match the extracted parent records.

Custom Use the wizard to select specific records from a

table, see the following section for more information.

In the example below, a specific query has been defined to specify which data should be extracted from the Customer table (OECUSTP), denoted by the magnifying glass icon. Moving upwards through the relationship tree, the Customer Type table (OECTYPP) has the default setting of Only Required, denoted by an icon with one orange line in the grid. This means that only the customer type records that are required for those customers matching the selection criteria will be included in the target database. The table OEUNITP at the top of the hierarchy is set to All Possible, denoted by the fully orange grid icon. All records in this table will be extracted. Moving downwards through the relationship tree, the Order Header and Order Lines tables are set to All Possible, this is reflected by the grid which is half filled, half empty. All orders for the customers that match the selection criteria will be extracted.


TestBench-PC

Note that although a table can appear in the relationship tree more than once, its extraction criterion remains the same. Therefore when defining selections it is sometimes easier to view the tables in a flat structure, this is achieved by selecting the ‘Data Selections’ tab.


TestBench-PC

Each table in the Data Case appears in this list only once. The data selections can also be modified from here from the right click menu.

Custom Queries

Specific data can be extracted from any table in the Data Case by defining a Custom Query, accessed via the right click menu for the table or from the Queries tab as shown below. This tab lists all custom queries in the Data Case across all tables.

When a new query is being defined from the screen above, the following panel is displayed. If however this is being done from the right click menu for a table, this screen is bypassed as the table has already been selected. Click on the table for which the query is being defined and then click ‘Next’.


TestBench-PC

The selection criteria can then be defined on the Custom Query panel shown below. In the query it is possible to not only use fields from the table for which the query is being defined, but also any of its parents, simply expand the list of fields by clicking on the plus icon next to each of the parent tables.

To use a field in the query, click on it in the right hand list and drag it to


TestBench-PC

the desired location in the query definition. The first ‘Value’ entry for any line in the query must be a field on the table, but the second ‘Value’ can be either another field or a specific value as shown above. Multiple lines preceded by either ‘And’ or ‘Or’ can be defined and unwanted lines can be removed by right clicking and selecting ‘Delete Line’. When the query is complete click on ‘Next’.

Use the above screen to specify whether or not you wish to obtain all possible data from the child tables of the table for which the query has been defined. Either select the table individually or right click to select or de-select them all. Please note that this will only affect tables which are currently set to ‘Only required’, any other settings will not be modified by changes made on this screen. Click ‘Finish’ to add the query to the Data Case. Queries can be removed in two ways. Right click the query on the Queries tab and select the ‘Delete’ option. Alternatively right click a table on one of the other two tabs and change to an alternative selection method. An existing query can be changed by selecting the ‘Edit’ option from the right click menu.


TestBench-PC

Executing a Data Case

Once the Data Case relationships and selection criteria have been defined, the Data Case can be executed to extract the data from the source to the target schema. Click on the ‘Execute’ toolbar option to display the following screen.

Run Description Text to describe this execution of the Data Case

which appears with the run in the results. TNS Name The TNS Name of the target schema to where

data will be extracted. If previously entered this is defaulted but can be changed at execution time. It can be different to the Source TNS.

Schema The name of the target schema to where data

will be extracted. If previously entered this is defaulted but can be changed at execution time.

Click ‘Next’ to be taken to the confirmation screen and then click ‘Finish’ to begin the extraction. A progress bar is shown while the extraction is occurring, when it is finished a message box is displayed as shown below.


TestBench-PC

If for any reason there was a problem with the extraction, an error message is displayed on the Extract Data panel and this should be reviewed before committing any changes to the target database. If however the extraction was successful and you wish to add the records to the target database, click ‘Yes’ on the above Data Extraction window. Whether the changes are committed or rolled back, a record is added to Data Case Results in TestBench-PC.

Data Case Results

For each execution of a Data Case, an entry is added to the results database which can be viewed by either right clicking a Data Case and selection the ‘Results’ option, or clicking ‘View Results’ from the Commands panel. Each extraction has a unique Run ID and the most recent extractions appear at the top of the list.


TestBench-PC

Status This column contains a value of either

‘Complete’, ‘Rollback’ or ‘Abnormal’, the latter representing extractions for which errors were encountered.

Warnings An extraction will typically only generate

warnings if it has a status of ‘Abnormal’. See the following section for more information.

Rows The total number of rows in all of the original

tables and the total number extracted. Right click any of the result lines and select the ‘Details’ option to view more information about the run. Alternatively if these results are no longer required, select the ‘Delete’ option. The Summary panel displays more detailed status information about the run such as target schema.


TestBench-PC

The Warnings panel lists any problems that prevented the extraction completing successfully, often meaning that the run has a status of Abnormal.

Click on the Tables tab to view the detailed statistics about how many rows were extracted for each table.


TestBench-PC


TestBench-PC

Notes Text Notes can be stored for an Action Map, Project, Test Case, Script and Test Run and either viewed online or included on the test report. Typical uses for Notes are:- * Statement of Action Map/Project objectives * Project definition and background * Defining Project Standards * Project scope definition * How to run a particular Test Case * Documenting particular subjects to check for in a Test * Capturing details of faults during a test The text in Notes is divided up into paragraphs for ease of movement or copying and can consist of any number of paragraphs. The text can be formatted with left and right margins, left adjust, right adjust, centering, underline, capitals and bullets.


TestBench-PC

Instructions for using Notes

1. Select the required level of Note by right clicking the desired Project, Test Case, Action Map, Script or Test run.

2. The current text if any is shown and separate paragraphs are indicated by the grey bar to the left of the screen.

3. A paragraph can be selected for amendment by double clicking with the cursor within the paragraph text.

4. A new paragraph can be created by clicking the icon. 5. The space on the Screen is the maximum space allowed for a

paragraph, although as many paragraphs as required can be created in a Note.

6. Line endings should be ignored, any words straddling a line end will be reformatted when the text is displayed or printed.

7. Clicking OK stores the text in the paragraph and returns to the display of the Note.

8. The formatting options can be set for any paragraph by first selecting the paragraph by clicking on it in the Notes display. Then use the formatting icons at the top of the panel.

9. Text can be copied by clicking and dragging the grey bar on the left of the paragraph.

10. Save the changes made to the Note by clicking the icon or ignore any changes using the icon.


TestBench-PC

- Save Saves an updated note.

- Close Close the note without saving any of the changes that have been made.

- New Paragraph Add a new paragraph at the next paragraph end

after the current position of the cursor.

- Delete Remove the currently selected paragraph.

- Bold Make the text appear in bold, or highlighted when displayed.

- Underline Underline all the words in the paragraph with a

single continuous line. In the Note editor, the appearance of the text will not alter.

- Bullet Format the paragraph with a single leading

bullet (·). For multiple bullet points, make each point a separate paragraph.

- All Capitals Convert all the text to capital letters when


TestBench-PC

printed or displayed. In the Note editor, the appearance of the text will not alter.

- Left Adjust The text on each line in the paragraph will start

in the left most position allowed by the margin settings.

- Centre The text on each line will be centered within the

margin settings.

- Right Adjust The text on each line will be adjusted to the right margin setting.


TestDrive-Green

3 TestDrive-Green

Introduction TestDrive-Green is part of TestBench, the only integrated testing suite for the IBM iSeries. TestDrive-Green provides:- • Recording of screens and screen entries that form business

transactions. • Re-play of those business transactions with automatic verification of

the actual results against those expected. • As part of TestBench, TestDrive-Green ensures that a consistent

environment is set at the start of each business transaction. • As part of TestBench, TestDrive-Green optionally triggers Test_IT

to ensure that the database and reports are verified along with the screens.


TestDrive-Green

System Requirements

Minimum Spec Recommended Spec Pentium III 1.0 Ghz 128MB Memory

Pentium IV 2.0 Ghz 512MB Memory

• Windows 2000, Windows XP or Windows Vista. • Client Access Express V5R1, iSeries for Access with a recent

service pack.

Are there other products like TestDrive-Green?

We classify TestDrive-Green as a ‘record and playback’ (“R&P”) tool as, along with verification, that is precisely what it does. There are many other R&P tools but here are some things which make TestDrive-Green unique: • Designed specifically for the iSeries so it understands iSeries

function keys, iSeries fields and iSeries data types. • Integrated with TestBench so for example your data base, data

areas and reports are checked along with your screens with the results stored together in an iSeries database.

• Integrated to run with Test Cases in TestBench to enable automatic data protection at the start of a run.

• Designed to be simple to use and to require minimum training. • Compatible with ‘Native’ Record and Playback, including the

batch script playback capability. • Scripts can be run from a command interface using the command

Play_IT (see separate section in the Utilities and System Values of the TestBench for iSeries User Guide).

• Talks directly to the 5250 emulation so you can do other things on your PC at the same time.

Is TestDrive-Green a scripting tool?

All R&P tools are script based, in that they must understand the sequence of actions that combine into a business transaction. TestDrive-Green is script based but you are not required to learn a new language, if you can use a CD player, you can use TestDrive-Green


TestDrive-Green

TestDrive-Green versus ‘Native’ Record and Playback

TestDrive-Green has a user friendly GUI interface as an alternative to the ‘green screen’ ‘Native’ R&P functions. It is also possible to run TestDrive-Green created scripts using the ‘Native’ playback function if you wish to run scripts in batch. However, if you do not use one of the supported emulators then ‘Native’ R&P provides an alternative method. The following table summarises the differences between TestDrive- Green and ‘Native’ R&P. TestDrive-Green ‘Native’ R&P Specific Emulator on PC Y N Non programmable terminal N Y GUI Interface Y N Keyboard Errors Y N Batch replay N Y Windows shown without N Y backdrop Scripts recorded in TestDrive-Green can be maintained and replayed in ‘Native’ R&P and vice versa, and any differences between the two methods will not be reported as errors. For more information regarding TestDrive-Green and ‘Native’ R&P compatibility please refer to Appendix C in the TestBench User Guide.

Getting Started

TestDrive-Green is installed when TestBench-PC is installed. TestBench-PC provides a GUI interface into some of the features that can also be accessed by TestBench on the iSeries. Once a validation code has been registered, TestDrive-Green is launched by clicking on the TestDrive-Green button at the bottom of TestBench-PC. See the TestBench-PC User Guide for more information.


TestDrive-Green

The Main Panel The TestDrive-Green window is a fixed size and can either remain on top of any windows from other applications when either recording or playing back a script so that the controls are available, or it can be minimised.

Toolbar Buttons Open Opens an existing script, which is attached to a

Test Case and Project. This function is always enabled. If a Script is already open and changes have been made to it since it was last saved, you are prompted to save the changes before it is closed and another Script opened.

Save Saves an updated Script to its existing name and

location. Delete Deletes the current script. A confirmation screen

is displayed before the deletion takes place. Record Initiates the recording of a new Script. Clicking

record while a Script is open allows new screens to be inserted into the Script.

Playback Initiates the playback of the currently opened

Script. Stop Ends the recording or interrupts the playing of a


TestDrive-Green

Script. This can also act as a Pause button, as the playback of the Script can be resumed.

Session (x) ‘x’ is the iSeries session to which TestDrive-

Green is attached and will record from and playback to. Where no session is connected the button will be named ‘No Session’. Clicking this button allows you to connect to any available iSeries session using the screen below, which must be done prior to recording or playing back a Script.

Options Display the Product Options for TestDrive-

Green – see later section for full details. Help Access the online TestDrive-Green help

information. The TestBench Help application needs to be installed separately.

Menu Options Note: This section only lists the options which have not already been explained above. File Close Closes the existing script but leaves the

TestDrive-Green application open. If changes have been made to the Script since it was last saved, you are prompted to save the changes before it is closed.


TestDrive-Green

Save As This differs from the ‘Save’ option as it enables

the Script to be saved with an alternative name or to a different Project and Test Case. As such it can be used to create a copy of an existing Script.

Create Launch File Launch files are used for two purposes. They

support integration with Mercury Quality Center and enable you to launch a particular Script without going through TestBench-PC. To use the file in Quality Center simply add it as an attachment as you would any other PC file. To launch outside of Quality Center simply right click the file and select ‘Launch’. By specifying additional options in the wizard that is displayed launch files can also be used for unassisted playback via a scheduler. See the section in the TestBench-PC chapter for more information.

Exit Close TestDrive-Green. This option is not

available when recording, inserting screens, playing back a Script or viewing Results. If a Script is open and changes have been made to it since it was last saved, you are prompted to save the changes before it is closed.

Script Tracked Fields This will open the Tracked Field dialog

window, which displays all the tracked fields available for selection, and allows others to be added or existing ones edited. See later section for more details.

Tracked Field History This provides a history of all of the tracked field

activity during the current execution of the Script. The option is only enabled during Playback.

Disconnect Session Disconnects the attached iSeries session, for

example so that another application can attach to it or so that an alternative session can be


TestDrive-Green

selected. Button is only enabled if a 5250 session is attached.

Properties Open the Script Options panel, see later section

for more information. Tools Layout Options These enable the format of the main TestDrive-

Green panel to be selected. See the later Screen Content section for details.

Help Check On-Line Connects to the support area of the Original

Software web site, from where for example support questions can be submitted or latest product versions downloaded.

Contact Us Invokes your default mail client to send an email

message to The Original Software Group support team.

About Product Information such as the version and

build number are listed here.

Product Options

The Product Options control global settings that affect all TestDrive-Green connections on this PC and they remain in effect until they are updated. Access this panel from the Tools menu, by clicking the Options button on the toolbar or by right clicking the name of the currently opened script. The following System options are supported:


TestDrive-Green

Title Search The position on the screen where the screen title can typically be found. Screens in the Script will automatically be saved with this name.

Decimal Separator Specify whether a period or a comma is used in

your application as the decimal separator. Extract AS/400 Screen Colours If this box is checked, the Check Colours option

for all scripts will be enabled. For PCs running version 3.1.3 of Client Access colour information cannot be retrieved, and some earlier service packs may cause TestDrive-Green to become unstable if colour checking is enabled.

Test_IT active for new scripts Determines the default ‘Activate Test_IT’ Script

level option for all newly created Scripts.


TestDrive-Green

Content Detects End Of Screen This option should be left unchecked for normal

use of the system. The following options will only be visible if the PC is running a DBCS language (Japanese, Korean, Simplified Chinese or Traditional Chinese). Display Font Allows the user to specify the font

in which screen images should be displayed as some DBCS characters are only available in specific fonts.

Configure for DBCS data Increases the size of the text on the

screen view window and causes the text in the tree view to be displayed in the selected DBCS font. DBCS characters contain more detail than SBCS characters and if the scripts contain a lot of DBCS data then this option may make it easier to read.

Configure for non-DBCS data Configure the screens with the

same size and font as for standard (non-DBCS) TestDrive-Green.


TestDrive-Green

The following Record options are supported:

Record Delay Used for the specific situation where a screen is

built in stages and the delay ensures that the screen is complete before a picture is taken. This option should be left as zero for normal operation.

Record Mode During recording the TestDrive-Green

application can be compacted to a view which only displays the list of screens as they are added to the Script. This enables both the iSeries session and the TestDrive-Green window to more easily be viewed at the same time. Alternatively select ‘Nothing’ to remain in full screen mode.


TestDrive-Green

The following Playback options are supported:

Play Delay Used to slow down Playback. Add a value in whole seconds to indicate a delay prior to the keystrokes being input to the screen.

Environment creation time out The maximum amount of time that TestDrive-

Green will wait before it cancels the script playback while the test environment is being created during an integrated test run. This can be extended to a longer period of time for test environments which take a long time to create.

Input inhibited time out The maximum amount of time that TestDrive-

Green will wait for the input inhibited indicator to clear before alerting the user. You then have the option to issue a keyboard reset (for example to clear an unexpected error condition), stop the script, or continue to wait for the same amount


TestDrive-Green

of time before receiving another message. Prompt For Test Items Check this option to be prompted to select test

items at the beginning of a test run and to record the status of the items at the end of the run. See later section for more information.

Check non-display fields If this field is checked, any differences between

expected and actual values for non-display fields (fields that are hidden from view) will be reported as errors. If it is not checked these differences will be ignored.

PowerPLAY Active If this option is checked, each time the

keystrokes for an expected field are sent to the application and there is no actual field to accept them, TestDrive-Green will search for a matching field to which the keystrokes can be sent. See the separate PowerPLAY section for more information.

Halt on Unmatched Input If this option is checked, each time the

keystrokes for an expected field are sent to the application and there is no actual field to accept them a warning screen will appear. The operation of this option varies according to whether the PowerPLAY option is selected.

• If PowerPLAY is selected the warning is

only generated if the field matching process fails to find a match.

• If PowerPLAY is not selected the warning

is generated as soon as a mismatch between the actual and expected fields is found.

See the separate PowerPLAY section for more

information. Match Rules Change the range of properties that are used

when trying to map expected and actual fields.


TestDrive-Green

See the section later in this document for more information.

Pause on initial screen Determines under which conditions the

playback of the script will pause on the initial screen of the application, at which time the user must choose whether or not to allow playback to commence. The three possible options are ‘Always’, ‘Never’ or ‘Only on error’ (i.e. if any initial screen differences occur).

If keyboard errors occur Determines the action that will be taken if an

unexpected keyboard error occurs during playback. Unexpected errors usually mean that the application behavior has changed since the Script was recorded. If the difference between actual and expected behavior is small then it may be possible for TestDrive-Green to recover from the problem and continue. In this case selecting ‘Send a Reset’ or ‘Do Not Play Keystrokes’ may enable the Script to keep running. If differences are significant then it is possible that errors will accumulate on subsequent screens, in which case selecting ‘Stop Playback’ is most appropriate. Generally, selecting ‘Show a Warning’ will give maximum flexibility in the event of problems with playback. If this option is selected, a choice of the other 3 options will be presented at this time.

Playback Mode During playback the TestDrive-Green

application can be compacted to a view which only displays the list of screens as they are added to the results. This enables both the iSeries session and the TestDrive-Green window to more easily be viewed at the same time. Alternatively select ‘Nothing’ to remain in full screen mode.


TestDrive-Green

Recording

Prerequisites

• Connection to a 5250 screen emulator session. • Connection to an iSeries.

The iSeries system application under test to be at the correct screen from which recording is to commence.

• Error messages must appear in the body of the 5250 display or they will not be recorded. (There is an option on some emulators, for example Client Access Express, to show error messages in the status bar.)

Instructions

1 Press the Record button. You will be asked to confirm this choice. 2 After confirmation, focus will be placed on the 5250 session, which

you can operate as normal. Note, keystrokes and cursor movements are not recorded, only the data when you press the next “Action On” key (Eg. Function Keys, Enter, Page Up/Down), so don’t worry about keying mistakes.

3 When finished, press the Stop button. Remember to always record the exit from the last screen, e.g. F3, if you are recording integrated scripts.

Notes 1 The Stop button can be used at any time, even when the 5250

session is in an Input Inhibited state. 3 No additional load is placed on the iSeries while a Script is being

recorded. 4 The time required to save a Script is based on many factors and

includes: • The size of the Script. • The current performance of the iSeries. • The current network traffic. 5 If you are running TestDrive-Green on a very low powered or low

memory PC, you may see a slight delay between pressing the keys in


TestDrive-Green

the 5250 session and their appearance on the screen. This is not a problem and can, if required, be eliminated by upgrading the PC used.

6. Until the script is saved, it will not be possible to store any results following playback. Nor will it be possible to store attached input, such as variable data, or use any tracked fields.


TestDrive-Green

Script Structure While a Script is open it will be shown in the format illustrated below, expanded to the screen level.

Layout Options

The panes on the display can be moved to different positions and also overlain. To move a pane, click on its title and drag it to the new location. To overlay a pane, click on its title and position it over another pane, a tab for each one will appear at the bottom of the pane. The panes can be hidden by clicking on the Pin icon, when this is done a tab for the pane will appear on the left hand side of the screen. To restore the pane to the main view, click on the tab and then on the Pin icon. TestDrive-Green can store three possible formats for this window. The options can either be selected from the Tools menu or by right-clicking on any of the orange window labels.

• Original – This view shows a graphical screen image plus all screen fields in list form. There are four other panes showing


TestDrive-Green

screen thumbnail images, variable data, tracked fields and screen input that can be accessed via icons to the left of the display.

• Advanced – In addition to the screen image and field list that

are present on the original layout, the other optional panes (with the exception of the thumbnail view) are also a permanent part of the display

• Preferred – This is only available if the ‘Set Preferred’

option has previously been selected. It enables an alternative to the above two formats to be created and stored, this will be specific to the PC being used. Simply adapt the display to suit your requirements and then select ‘Set Preferred’ to create or overwrite the preferred layout.

• Set Preferred – This selects the current view as a preferred

layout which can then be loaded at anytime via the ‘Preferred’ layout option explained above.

While both the Original and Advanced layouts can be manipulated, they will continually return to their default setting so the Preferred layout should be used to store any permanent changes to the view. The following screen prints show the Original layout followed by the Advanced layout.


TestDrive-Green


TestDrive-Green

Icons

Every panel has one of these toggle icons associated with it. Click the left side to maximize this panel to fill the entire view, click the right side to restore back to the previous multiple panel view.

The functionality for each of the panes is explained in more detail below.

Screens

All screens in the script are listed. Click on a screen in the list to show information for that screen in all of the other Content panels.

Right click any screen in the list to obtain the following options. Options Display the Product Options for TestDrive-

Green – see later section for full details. Edit/View Display the Screen Options window. See later

section for full details.


TestDrive-Green

Delete Delete the screen from the script. A

confirmation screen is displayed before the deletion takes place.

Toggle Checking If this screen is not to be checked for differences

during playback this will be indicated with a yellow cross on the above display. If any differences are found between expected and actual values on playback, these will not be reported as errors. Screen checking can also be changed from the Screen Options panel.

Replace Content The details of the current iSeries session will be

captured after a confirmation screen has been displayed and the fields compared with the existing screen in the Script. The old screen will be replaced with the new one after the fields have been matched. See separate Screen Replacement section for more information.

Verify From Here This option enables a Script to be re-run and the

old screens to be automatically updated with the contents of the actual screens when differences are encountered. See separate Script Verification section for more information.

View the details about any screen by placing the focus on the Screen name.

Click on different sides of the icon to toggle the background colour of the screen image between white and black.

Click on different sides of the icon to toggle

between the At Start and Keystrokes views, i.e. the image of the screen when it first appeared versus the information that was keyed into the screen.

Transaction The Variable Data transaction for which data is

currently being displayed. This box will contain a value of 1 if Variable Data is not in use.


TestDrive-Green

Any fields with the ‘Do NOT test this field’ option checked on the Field Properties window will appear in italics, which means that differences between the actual and expected versions of this field on playback will not be reported as errors. Click on any field on the screen to highlight the details for this field on the Fields and Input panels described below. Double click any field on the screen to access Field Properties for the field (see later section). Alternatively right click and select the ‘Edit/View’ option.

Fields


TestDrive-Green

All individual pieces of information present on the screen are listed. The tick or cross next to each field indicates the status of the ‘Do NOT test this field’ option that can be found on the Field Properties window. A cross means that differences between the actual and expected versions of this field on playback will not be reported as errors.

This field is a constant type field and has an At Start value.

This field is a data type field and has both an At Start value and Keystroke value.

Click on any field in the list to highlight the details for this field on the Screen and Input panels described above and below. Double click any field in the list to access Field Properties for the field (see later section). Alternatively right click and select the ‘Edit/View’ option.

Input


TestDrive-Green

All input actions for the screen are listed, the final input in the list being the key that was used to exit the screen. The progression from this screen to the next will most commonly occur as a result of a function key or other action key being pressed. Click on any input in the list to highlight the details for this field on the Screen and Fields panels described above. Double click any item in the list (with the exception of the exit action) to access Field Properties (see later section) from where the input can be changed. Alternatively right click and select the ‘Edit’ option. For the exit action, the Screen Options panel is displayed from where the exit key can be changed.


TestDrive-Green

Variable Data

All variable data fields in use in this script are listed on this screen in bold. Beneath each field is the screen number and name on which this variable data field is in use, of which there could be more than one. Beneath the screen name are listed the start values of the fields for which the variable data will be used. For example, the variable data field ‘Cust Num’ is in use on screens (2) and (5). Click on any screen or field in the list to highlight the details for that screen or field on the other Content panels. Right click options Edit Variable Data Maintain or view the variable data set associated

with this script.


TestDrive-Green

Edit/View The screen that will displayed when this option is selected is dependant upon the item that is in focus in the list. If a screen is highlighted the Screen Options window is displayed, whereas if a screen field is selected the Field Properties window is shown. Double clicking these items will also have the same effect.

Tracked Fields

All Tracked Fields in use in this script are listed on this screen in bold. Beneath each field is the screen number and name on which this tracked field is in use, of which there could be more than one. Beneath the screen name are listed the start values of the fields for which the variable data will be used. See later Tracked Fields section for more information.


TestDrive-Green

Click on any screen or field in the list to highlight the details for that screen or field on the other Content panels. Right click options Edit Tracked Fields Maintain or view the Tracked Fields associated

with this script. Edit/View The screen that will displayed when this option

is selected is dependant upon the item that is in focus in the list. If a screen is highlighted the Screen Options window is displayed, whereas if a screen field is selected the Field Properties window is shown. Double clicking these items will also have the same effect.

Thumbnails

This panel enables small images for each screen to be viewed in a scrollable list to assist with navigation through the script. For performance reasons the thumbnails are not created automatically when the script is opened, the first time the panel is accessed after a script has been loaded the following screen is displayed.


TestDrive-Green

Once the icon has been clicked, the view is expanded to show the following display. Click on any screen image in the list to show information for that screen in all of the other Content panels.


TestDrive-Green


TestDrive-Green

Field Properties

Field Properties can be accessed by double clicking a field on the screen display or field list view or by right clicking and selecting the Edit option. Keystrokes are not valid for constant type fields and cannot be seen on this screen. Start You have the ability to change what value will be used for this field for verification when the Script is executed and the screen containing this field appears. If this value does not appear then an error will be reported.

Fixed Value Use this option to check the start value against

the characters in the adjacent box. Variable Field Select a Field Name if you want the value to be

checked to come from the Variable Data entered for each execution of the Script. To change the Variable Data or add a new Variable Field, click on the Edit button.

Tracked Field Select a Field Name if you want the value to be

checked to come from the value in the Tracked Field. If the Tracked Field has not yet been


TestDrive-Green

populated, the value to be checked will be compared against a blank. To modify any Tracked Fields, click on the Edit button.

Field Error Actions If this field is in error the Script can either be

paused, at which point the option to continue is available, or aborted. These values can also be set at the screen level and by default any screen actions will be followed.

Do NOT test this field If the field is not to be checked for differences,

it will appear in italics on the graphical screen display and this will also be indicated with a cross on the field list.

Keystrokes You have the ability to change what keystrokes will be sent to this field if it is a Data field rather than a Constant. Care must be taken with these values as they may affect what screens will subsequently appear. The Keystrokes tab is not shown for Constant fields.

Fixed Use this option to use the keystrokes shown in

the adjacent box.


TestDrive-Green

Variable Field Select a Field Name if you want the keystrokes to vary according to Variable Data entered for each execution of the Script. To change the Variable Data or add a new Variable Field, click on the Edit button.

Tracked Field Select a Field Name if you want the keystrokes

to vary according to the current value in a Tracked Field. If the Tracked Field has not yet been populated the keystrokes will be blank. To modify any Tracked Fields, click on the Edit button.

Keystroke To Send Indicate when a Field Exit key should be played

after the keystrokes, for example for Auto-record Advance fields, or fields where field exit causes data to become right adjusted.

Track Use these options when you wish to use either the ‘At Start’ or ‘Keystrokes’ values of a screen field to populate a Tracked Field. This Tracked Field can then be used elsewhere in the Script to populate other screen fields with the stored value. See separate section on Tracked Fields for more information.


TestDrive-Green

Store Start Value In Select a Tracked Field into which the initial

value of this field will be stored. To modify any Tracked Fields, click on the Edit button.

Store Whole Field Place the entire contents of the screen field into

the named Tracked Field. Store Part Field Place only the specified section of the screen

field into the named Tracked Field. Store End Value In Select a Tracked Field into which the final value

of this field will be stored. To modify any Tracked Fields, click on the Edit button.

Location These options can be used to change the length, screen position and colour of fields on the screen.

Row The screen line on which the field is expected to

appear. Column The position (left to right) on the screen that the

field is expected to appear.


TestDrive-Green

Length The expected length of the field on the screen. Colour The colour that this field is expected to be on

screen. Any differences will be reported if the Check Colours option is checked in the Script Options window. This refers to the base 5250 colours of the field and does not take account of any customised colour changes made to the 5250 session. To avoid confusion it is recommended you use the 5250 session with its default colour settings.


TestDrive-Green

Screen Options You can access the Screen Options by double clicking the Screen name in the tree view.

General Options

Title TestDrive-Green automatically titles screens

during recording by taking the text from the position specified in the TestDrive-Green ‘Options’ window on each screen. You can amend this title here.

Screen is ended by The method by which the Script progresses to


TestDrive-Green

the next screen. This will most commonly occur as a result of a function key or other action key being pressed. You can choose any key from the list that sends a request to the iSeries. Care should be taken as an alteration may change the next screen that appears and subsequent screens in the Script may no longer be appropriate. The screen can also be ended due to keystrokes being placed into an Auto Record Advance Field, or by typing a keystroke into a particular area of the screen. For example, attempting to key outside of a window or typing an alphabetic character into a numeric field may cause an error message to be displayed.

Final cursor position The position of the cursor when the screen was

ended. Use in conjunction with function key option when this action is cursor sensitive. For example, pressing F4 on different fields may yield different results.

Wait time before processing next screen This specifies the amount of time in seconds that

TestDrive-Green will wait before keying input into the screen and progressing to the next one.

Special action at end of screen These options only need to be used if a Web or

GUI application is launched from this screen in the script which will tested via a TestDrive-Gold script. If these scripts are going to be combined into an Action Map, check the ‘Restore emulator focus option’ and specify the number of seconds required to give the Web or GUI application time to launch. This will ensure that once the application has been launched, focus will be placed back onto the iSeries session so that another TestDrive-Green script can be replayed after the TestDrive-Gold one if required.

Checking If this screen is not to be checked for differences

this will be indicated with a cross on the screen list. If any differences are found between


TestDrive-Green

expected and actual values on playback these will not be reported as errors.

Check Differences between expected and actual values

for any field on screen can be reported as errors, unless this field has been excluded from the comparison. Alternatively, differences between Constants or Data fields only can be reported. These options are also present at the script level and checking the ‘Script Check Option’ button will cause the values specified there to be used.

It is also possible to bypass error checking for all fields on the screen.

Take the action/ Select a value between 0 and 999 and use this to If errors exceed force an action to be taken should the number of

errors at a screen level surpass the number specified here. The script can either be paused, at which point the option to continue is available, or aborted.

Variable data options Use this option if in a script driven by Variable

Data this is the point at which processing should either begin for each transaction (Loop top) or return to the first screen (Loop bottom).

Screens before the Loop top point form initial processing only initiated prior to variable data entry.

Screens after and including the Loop bottom point form exit processing only initiated once all variable data records have been completed.

Play / Pause Options Normal: Play back all the keystrokes for the

screen with no delay between them. Pause at start: Suspend playback at the start of the screen before any keystrokes have been played. At this point playback can either be halted or continued. Step: Before playing each keystroke TestDrive-Green will prompt to confirm whether the keystroke should be played back or not. Fine Step: Similar functionality to ‘Step’ except that it provides a higher level of detail.


TestDrive-Green

With Fine Step, TestDrive-Green prompts to confirm the keystrokes that are being sent and the cursor movements which are made prior to sending the keystrokes.

If one of the step modes (Step or Fine Step) is selected, when the screen is reached the following form will be displayed.

Play / Continue Play the keystrokes as specified. Do not play keystrokes Skip these keystrokes and continue to the next

keystrokes that are available for the screen. Change step mode Switch from fine step to normal step or vice

versa. Stop playback Playback stops and TestDrive-Green will

display the keep or discard results prompt.


TestDrive-Green

Column Input

When to use column input The column input feature may be set up and activated screen by screen in a script. If activated, the normal input (whether keystrokes, variable data or a tracked field) will still be played except for the input specified under the column input tab. Column input is designed to be used in sub-file type displays, where a line in the sub-file needs to be processed, but the required line does not always appear on the same row. You can use column input to search a sub-file for a known value, and then play input to another column on the same row. For example, if you need to amend an order number ‘000123’ with option ‘2’ from a list of orders for that customer, you can search and find the order and continue processing by playing the input value of ‘2’ into the appropriate field on the same line. How to use column input

1. Identify the data or value which the script will need to search for. If fixed, this can be entered as is, if variable use either variable data or tracked fields to store the value you are looking for.

2. Access the screen options window and select the Column Input tab. 3. Check the check box to enable Column input 4. In the search for grid, find the column heading (these are determined

automatically for sub-files) which represents the column in which the value you are looking for will be contained. Select the type of value and the value or field containing the value.

5. In the playback section, select the field into which input is to be performed and similarly to above define what the required input should be.

6. In case the row you are looking for is not found, you can specify a ‘not found’ action. Typically this will be page down together with a maximum attempts at this action.


TestDrive-Green

Use Column Input If checked then Column Input will be used for

this screen. If not checked then the Column Input information will be retained but the standard keystrokes for the screen will be played.

Search For Specify the Columns you wish to search for.

Once the column has been identified, you then specify the value in this column that needs to be found. This can be a Fixed value, Variable field or Tracked Field.

Playback Once the value has been found, specify which

column on this row you wish to play keystrokes into. Again this input can be a Fixed Value, Variable Field or Tracked Field.


TestDrive-Green

If not found play It is possible that the value you are searching for is not on the screen. This option enables you to press a Function key a specific number of times to try and find the value.

Before playing key Use this option if the cursor needs to be moved

to a specific position before playing the Function key.


TestDrive-Green

Script Options Script Options can be accessed in several ways: 1. Shown when the ‘Playback’ button is pressed for a selected Script.

Any amendments made here will be temporary and apply to this run only.

2. Double clicking the Script Header in a selected script. 3. Clicking on the Options button when saving the Script.

Activate Test_IT Choose whether TestBench Test_IT facilities

are to be enabled when this Script is executed. Using this option will instruct TestBench to start the Test Case running on the iSeries before replaying the script. Test_IT gives the capability to ensure a consistent initial


TestDrive-Green

environment, together with database, data area and program parameter verification. The 5250 session must be on the TestBench Main Menu for this option to work. If not, an error message is displayed. The default value for this option can be set on the TestDrive-Green Product Options panel.

Use Variable Data Choose whether the Variable Data associated

with the Script is to be used during Playback. Note that multiple Variable Data records will cause the Script to execute once per record. This option is only available if at least one variable field has been defined. See relevant section on Variable Data.

Error count Select a value between 0 and 999. Use this to

force an action to be taken should the number of fields in error exceed the number specified here. The Script can either be continued to be played, paused, at which point the option to continue is available, or aborted.

Description Optional field which appears on the Sub Run

display if entered. User Reference Optional user controlled text which is displayed

by pressing F7 on Test Run Details in results. It can be used for any purpose, for example to group multiple runs together via a single work request number.

First/Last Transaction For Scripts which use variable data, specify the

first and last transaction in the data set to be used during playback.


TestDrive-Green

Number of Runs Select a value of 1 or greater to indicate how many times the Script should execute. Each execution will be represented as a separate Sub Run in Test Case Results. This is useful for destruction testing (a maximum value of 999 is available), or where Test_IT integration is selected to match the number of Processes.

Use Tracked Fields Choose whether the Tracked Fields associated

with the Script are to be used during Playback. See relevant section on Tracked Fields.

Tracked Fields This button will allow any Tracked Fields that

are associated with the script to be edited. See the separate section on Tracked Fields.

Checking Inactive If this option is ticked then any differences

between expected and actual field values will


TestDrive-Green

not be reported as errors. Match Field Length If a field has changed in length but its contents

remain the same, leaving this option unchecked will not report this as a difference during playback. However, checking this option will cause a difference to be reported.

Exceptions This button enables data on the screen to be

excluded from the comparison when a Script is played back, with the result that any differences are not reported as errors. See specific section below.

Check All Fields Differences between expected and actual values

for any field on screen will be reported as errors, unless this field has been excluded from the comparison.

Only Check Constants Only report differences between constant

(output) fields. Only Check Data Fields

Only report differences between data (input) fields.

Check Colours Tick this box to ensure that differences in screen

colours will be reported during playback and stored as errors.


TestDrive-Green

Variable Data This screen enables any variable data that is

associated with the Script (Local) or data that can also be used by other Scripts (Public) to be edited. See the separate section on Variable Data.


TestDrive-Green

Displays the name of the current Script along with the Project and Test Case in which it is stored.

Exceptions

These Script and Global (system) level exclusions are an important addition or alternative to that achieved by excluding individual fields. For example, the time of day may appear on every screen in a Script. One option would be to tune each screen to ignore any differences in the time, but Script level exclusions allow this to be achieved via a single entry. The Global exclusions are displayed here for information purposes only. These must be updated on the iSeries by taking option ‘4’ on the System Values screen. This can be reached by taking option ‘51’ from the TestBench Main Menu and then keying option ‘21’ for System Values.


TestDrive-Green

Type This can only be Item, Date, Time or *Any. An

Item refers to any piece of text or value in the Script and *Any refers to any field or part of a field appearing on a specified line or lines on each screen. See Compare Data below for a full explanation.

Start Line The start line in the 5250 session line range to

examine fields that start in the range for exclusion data. This can range from 1 to 27.

End Line The end line in the 5250 session line range to

examine fields that start in the range for exclusion data. This can range from 1 to 27 and must equate to, or exceed the End Line.

Compare Data For Item exclusion types, this can be any value.

For Date exclusion types this must be ‘/’, ‘:’ and ‘.’. For Time exclusion types this must be set to ‘:’, ‘/’ and ‘.’. For *Any exclusion types this can be blank, in which case all fields beginning in the line range will be excluded. Alternatively, if a value is specified only fields containing this character string will be excluded from the comparison.

Scope Global exceptions apply to all Scripts and can be

viewed here but can only be updated through the TestBench System Values screen. Script exceptions can be updated here and apply to this Script only.


TestDrive-Green

Notes 1. The Date exclusions only apply to fields that are 8 or 10 characters in

length and have the Data character (e.g. ‘/’) in the format nn/nn/nnnn or nnnn/nn/nn where all the other characters are numeric apart from an allowed leading blank.

2. The Time exclusions only apply to fields that are 5 or 8 characters in length and have the Data character (e.g. ‘:’) in the format nn:nn:nn where all the other characters are numeric apart from an allowed leading blank.


TestDrive-Green

Amending Scripts It is important to remember that TestDrive-Green only records the iSeries screens on the pressing of the ‘Action On’ key or keying into an auto record advance field and therefore keystroke mistakes made during the entry of data when recording a screen are NOT captured. This leads to fewer Script amendments being required. In the event that changes occur to the system under test for which scripts already exist, it is possible to easily change these scripts. Changes that can occur are: • Extra screens can be recorded and inserted into existing test scripts

(see below). • Incorrect or surplus screens can be deleted from existing test scripts

(see below). • Individual screens can be replaced in a Script. See following section

on Screen Replacement. • Scripts can be run in Verify mode which enables old screens to be

automatically updated with the contents of the actual screen. See following section on Script Verification.

• Both the Constant and Data field contents can be changed to cater for changes (see paragraphs relating to Field Properties).

• The length and position of a field on screen can be changed using the Location tab (see later paragraphs relating to Field Properties).

• Any Variable Data or Tracked Fields that have been set up for a Script can be altered (see relevant paragraphs in ‘Native’ Record and Playback chapter and later in this chapter).

• A Script Scan/Replace option is available on the iSeries to allow strings of characters to be found and replaced within At Starts, Keystrokes and Variable Data. It is also possible to scan for a fixed value and replace with a variable field name to quickly change the Script to use variable data (see relevant paragraphs in ‘Native’ Record and Playback section).

• The Screen Names can be changed (see Script Options paragraph). • The function key to progress from screen to screen can be changed,

or the field used to trigger auto record advance (see Screen Options paragraph).


TestDrive-Green

• The Scripts that will be run in an Action Map can be changed. If a system application screen has been changed so that new fields added have resulted in the original screen being split into two screens then the originally recorded screen can be deleted and two new screens inserted in its place. Alternatively the Screen Replacement or Script Verification functions can be used.

Deleting a Screen

To delete a screen from an existing Script: 1 Open the Script that requires changing and click on the relevant

Screen name. 2 Press the ‘delete’ key on the keyboard. You will be asked to confirm

that deletion is required. 3 On confirmation the screen will be deleted. 4 Save the Script. Care must be taken in the event that Top and Bottom Loops have been specified within the Script, especially if the screen being deleted is marked as either one (see Variable Data section).

Inserting a Screen

To insert a screen into an existing Script: 1 Open the Script that requires changing and optionally click on the

Screen name before the point at which you want to insert a new screen.

2 Ensure that the system application under test is on the correct screen for recording.

3 Press the Record button. The following screen will be displayed.


TestDrive-Green

4 Click OK after entering the desired options and TestDrive-Green will go directly into ‘Record’ mode with the focus placed on the 5250 session.

5 Commence required processing on the iSeries. 6 When finished press the ‘Stop ‘button. 7 You will be asked whether you want to keep the last screen

recorded. In most instances the answer would be ‘No’ unless inserting at the very end of the Script. If the last screen is kept then it is essential to check that the ‘Action On’ field has been set correctly. (See Script Options for further information).

8 Save the script and use ‘Playback’ to verify screens captured correctly.

Care needs to be taken to use the same data starting point as the screens recorded previously in the Script.

Screen Replacement

Screen replacement is performed by right clicking a screen in the list and selecting ‘Replace Content’ from the menu. TestDrive-Green must be connected to an iSeries session for this function to be enabled. When this option is selected, TestDrive-Green compares the details on the current iSeries session to those on the existing screen in the Script. If a match can be found for all fields on the screen then keystrokes, tracked fields and variable data definitions are automatically moved from the old


TestDrive-Green

screen to the new screen and then the old screen is replaced by the new one. If one or more fields cannot be successfully mapped, the screen display form is opened and the fields that could not be matched are highlighted as shown below. More information about how field mapping can be viewed and modified and the rules which govern field mapping can be found in the later Match Rules section.

The user has the option of ignoring the fields (screen will be replaced but no data for these fields will be mapped), manually specifying a mapping for the unmapped fields or canceling the replacement. Proceed The old screen will be replaced with the new

one and the keystrokes, tracked fields and variable data definitions will be automatically moved for fields that can be matched.

Cancel The screen replacement is cancelled and the old


TestDrive-Green

screen will remain in the Script.

Manual Mapping

If a field cannot be auto-matched it is possible to define the correct mapping for the field manually. This only needs to be done for fields where keystrokes, tracked fields or variable data definitions need to be transferred to a field on the new screen. This option can also be used to change the mappings for fields that have been incorrectly matched by TestDrive-Green • Click on a field on the expected display for which manual mapping

will be defined, this field then appears in orange reverse image on the display.

• Right click and select the ‘Alter mapping’ menu option as shown below.

• Click on the Actual radio button to view the new screen.


TestDrive-Green

• Right click on the new field that should contain the properties of the old field and select the ‘New target’ menu option. Alternatively select the ‘Cancel’ option if you do not wish to manually map the selected field.

Script Verification

A verification run is started by right clicking a screen in the list and selecting ‘Verify From Here’. The confirmation screen that is displayed allows the user to control the conditions under which playback will halt to request manual intervention. One of three possible conditions for halting playback can be specified. • Whenever differences are detected • If any fields cannot be auto-matched • If core fields (fields requiring input, tracked or variable constants) cannot be auto-matched The Advanced tab also enables the Match Rules as described in a following section to be modified. These determine the conditions used for matching actual and expected fields. If differences are detected during the run, TestDrive-Green will decide whether to alert the user based on these settings. Fields that fail to satisfy the criteria will be highlighted as shown below.


TestDrive-Green

There are three types of action which can be taken here: • The settings controlling which expected fields map to which actual

fields can be changed using the Rematch button. Note that if the match rules are changed the modified rules will continue to be applied on subsequent screens in the Script.

• The new screen can be used to change the Script using the Action list.

• Playback can continue or end. If the decision is made that the Script should be changed, one of the following actions must be chosen: • Replace • Ignore • Insert • Delete Insert is intended to deal with screens that have been added to the


TestDrive-Green

application since the Script was recorded. The Delete option removes unwanted screens. When a screen is removed the playback/verify action is repeated on the next screen in the Script. When a new screen is added the screen definition must be edited to specify any keystrokes for fields which need them and to specify an exit action for the screen. A screen is generally ended by playing an action key but it is also possible to leave the screen by keying values into an Auto-RA (Record Advance) field or by typing a keystroke into a non-input-capable area of the screen. The drop-down list box labeled ‘Exit Action’ allows either of these options to be specified. Selecting one of these options will display a separate form where the location of the field or the keystrokes can be specified. TestDrive-Green will then add the screen definition to the Script before playing back the new screen and will repeat the validation routine against what was the current screen. Any fields on the screen can also be manually mapped - please refer to this paragraph within the previous Screen Replacement section for more information. In addition when manually mapping fields in verify mode it is possible to set up a Match Rule. This is useful where a particular change has been made on a variety of fields, e.g. a version number may appear on all screens in an application and the version has now changed. A Match Rule allows the same change to be applied consistently over many screens in the application. Match Rules can be created by choosing the ‘Create Match Rule’ option from the menu that appears when selecting an actual field to map expected fields to.


TestDrive-Green

Match Rules The Match Rules are used when TestDrive-Green attempts to map expected to actual fields within the following functions: • PowerPLAY • Screen Replacement • Script Verification TestDrive-Green maps expected to actual fields by building a list of target fields from the actual screen for each of the expected fields and then picking the one that is nearest. The target list is built by comparing a range of different properties in the two fields. The properties that are compared when TestDrive-Green builds the list can be changed via the Match Rules. The setting of field mapping conditions can be changed from the System tab in TestDrive-Green Product Options or when playback has been interrupted in Verify mode to display the error screen. The following can all be specified as match conditions which mean that the property must be the same on the expected and actual fields for a match to be identified.


TestDrive-Green

The following options may require further explanation.

Const/Data Data fields are those which can accept input whereas constant fields are display fields only.

Visibility Whether or not the field is hidden from view.

Start Values The initial content of the field is used as matching criteria if this option is checked.

Label

A label is the piece of text associated with a field. Label matching is probably the most flexible way of matching expected and actual fields and is particularly useful for matching the keystrokes, variable data and tracked fields which are associated with data fields. Since the fields on a green screen do not have accessible names, the matching process generally relies on the label to match the actual and the expected field, although in some cases (e.g. if the data fields are populated with values) it may be possible to rely on the start value for matching. For example, if a screen in the application has three fields: Title: --- First Name: --------------- Last Name: --------------- and the application is modified so that the screen now reads: Last Name: --------------- First Name: --------------- Title: --- TestDrive-Green will still be able to play back the keystrokes for the field correctly because, even though the data fields have moved they still have the same positions relative to their labels.


TestDrive-Green

This matching of data fields based on their position relative to a label becomes particularly powerful when the screen contains subfiles and a whole column of data fields may be associated with a single label (see note on ‘Labels and Matching in Subfiles’ below). If the field is a constant then the label is the start value of the field. If the field is a data field the label is calculated as follows: • Look to the left of the field. If the next field found is a constant

then the label is the start value of the constant. • If no constant is found to the left then look at the field directly

above. • If there is no field, the data field does not get a label. • If there is a constant field above the data field, the label of the data field is the start value of the constant. • If there is a data field above the data field, then the data field which

is being assigned acquires the same label as the data field above it. As well as the label text, a field acquires a label offset value. If the field is a constant the offset value is zero. If the field is a data field, if the constant that provided its label is on the same row, then the label offset value is also zero. If the constant is on a different row, the label offset value indicates the number of rows between the data field and the constant that defines its label. In other words, the label offset value defines the positional relationship between a field and its label. When TestDrive-Green matches a field by ‘label’ both the label text and the label offset value have to match.

Labels and Matching in Subfiles

When a screen contains a subfile, TestDrive-Green performs additional processing to assign the labels for matching expected and actual fields. TestDrive-Green identifies a subfile on the screen where it can find a column of consecutive data values that have the same field length on each row, with a constant header at the top of them. The first such column that is found defines the vertical range of the subfile. This means that the logic will not handle pure output subfiles. All other fields within this vertical range which form into continuous columns are identified as being part of the subfile and the labels they are given are always derived from the column name.


TestDrive-Green

This matching process works well where the subfile is uninterrupted, but may work incompletely or not at all where the subfile is interrupted by a window. In such cases manual intervention will be needed by the user to decide whether the fields need to be manually mapped or if the differences can simply be ignored.


TestDrive-Green

Playback

Prerequisites

• Connection to a 5250 screen emulator session. • Connection to an iSeries. • The Script you are about to replay has been opened. • If using an integrated Test_IT run, make sure that TestBench is on the

Main Menu.

Instructions

1 Click the ‘Playback’ button. 2 On the Script Options panel select the options required. For the

functions provided by these options refer to the section on Script Options.

3 Select any Test Items which are to be looked at for this test run. See the section below for more details.

4. Confirm Playback should start. The screen defaults to playback in either compact or full screen mode depending on your Product Option setting. If you wish to change this mode during playback, click on the icon at the top right of the display.

5 Depending on your Product Options, playback may automatically stop when the first expected screen of the Script is displayed. This screen is compared to the actual screen on the attached session and any differences are highlighted. If there are no differences the TestDrive-Green panel shows a green light but if there are it will be red. If this is the correct starting point for the script, press ‘Yes’ to continue. If this is not the correct starting point, click ‘No’ to stop the run. The details of any errors on this screen can be viewed by clicking on the Screen name it is possible to continue with the playback even if errors have been found on this first screen.

6 The Script will now run in the attached 5250 session. Each screen result collected will be shown in the TestDrive-Green panel with an indicator light. Similar indicator lights are used at the field level.

• Green – No differences

• Red – Differences


TestDrive-Green

• Orange – Screen not checked

7 The Playback can be interrupted at any time by pressing the ‘Stop’ button.


TestDrive-Green

PowerPLAY

PowerPLAY allows an existing Script to be played back against an application that has changed, therefore enabling testing during the early parts of the development cycle where fields may move around on the screen and frequent cosmetic changes may be made. When a Script is run in PowerPLAY mode, TestDrive-Green uses Match Rules to identify where the keystrokes should be played. The Match Rules that will be applied can be viewed and, if necessary, changed by clicking the Product Options icon on the main TestDrive-Green panel. If a match can be found, TestDrive-Green will report a difference (because the screens have changed) but it will still play the input back into the relocated field. See the later section in this document for more information on Match Rules. There are two fields on the playback tab of the TestDrive-Green Options panel that control how PowerPLAY operates. These options both affect playback and can be applied independently of each other. • PowerPLAY Active • Halt on Unmatched Input If PowerPLAY is selected, each time the keystrokes for an expected field are sent to the iSeries and there is no actual field available to accept them, TestDrive-Green will search for a matching field to which the keystrokes can be sent. If such a match can be found, the keystrokes will be sent to the new field. If ‘Halt on Unmatched Input’ is selected a warning prompt is generated every time a field cannot be found into which keystrokes can be played. The way this option operates varies depending on whether or not PowerPLAY is selected. • If PowerPLAY is selected the warning is only generated if the field matching process fails to find a suitable matching field. • If PowerPLAY is not selected the warning is generated as soon as a mismatch between the actual and expected fields are found. Each time the warning is generated the user needs to decide whether to continue or stop the Script. If Continue is selected, TestDrive-Green will try to play on without sending the keystrokes for the field. If Stop is selected the script playback will halt and the Keep/Discard buttons will appear.


TestDrive-Green

Test Items

Test Items which have been created for a Test Case can be accessed via TestDrive-Green, and the status updated and comments added. The following window appears after the Script Options when the Play button is pressed and provided the option has been selected in the TestDrive-Green Options window. The list of documented items for this run can be tailored either by left/right clicking individual items, or by using the two buttons to select or de-select all items. New Test Items can be added or removed for this run only. If not performing an Integrated run and Test Items have already been selected during Test Case initiation in the 5250 session, any selections or alterations made now will replace those made earlier. Any changes are stored back on the iSeries at the end of the run when the results are saved.

Once the playback of the script has been completed a similar window is displayed which enables the status and comments to be entered (see later Pass/Fail Results section).


TestDrive-Green

Results Once the execution of a Script is complete or the execution has been interrupted by the user, a panel in the following format is displayed:

Each screen which was presented during the execution of the Script is listed together with a symbol indicating: Green tick All Data and Constant items that were actually

presented matched your expectations as defined in the Script or expanded through Variable Data or Tracked Fields.

Red cross At least one Data or Constant item did not

match your expectations. Orange dash The screen was not verified as you had

instructed it to be omitted (not checked). This includes the final screen which is never tested during an integrated run.

View the details about any screen by clicking on the screen name in the


TestDrive-Green

list. The results window can have three possible formats depending on the layout option that is selected:

• Original – This shows a graphical image of the Expected screen plus all screen fields in list form with those in error indicated by a red cross. There are four other panes showing a screen list, actual screen image, actual field list and errors only view that can be accessed via icons to the left of the display.

• Advanced – Both the Expected and Actual screen images are

shown one above the other, with the screen list to the left and the field lists to the right, controlled by three tabs.

• Preferred – This is only available if the ‘Set Preferred Layout’

option has been selected from the Options menu. It enables an alternative to the above two formats to be created and stored; this will be specific to the PC being used. Simply adapt the display to suit your requirements and then select ‘Set Preferred Layout’ to create or overwrite the preferred layout.

Each individual panel can be moved to different positions and also overlain. To move a pane click on the panel and drag it to the new location. To overlay a pane, click on the panel and position it over another panel, a tab for each pane will appear at the bottom of the pane. The panes can be hidden by clicking on the Pin icon in the panel, when this is done a tab for the panel will appear on the left hand side of the screen. To restore the panel, click on the tab and then on the Pin icon. While both the Original and Advanced layouts can be manipulated, they will continually return to their default setting so the Preferred layout should be used to store any permanent changes. The following screen prints show the Original layout followed by the Advanced layout.


TestDrive-Green


TestDrive-Green

Icons

Every panel has one of these toggle icons associated with it. Click the left side to maximize this panel to fill the entire window, click the right side to restore back to the previous multiple panel view.

The functionality for each of the individual panes is explained in more detail below.

Expected/Actual Screen Images

Note that any differences between the Actual and Expected results are highlighted and any individual fields that are not being verified appear in italics. The highlighting of differences is affected by the checking options in place. Double clicking any field on the Expected screen image will cause the Field Properties panel to appear in view only mode (see later section). Alternatively right click and select the ‘Edit/View’ option.


TestDrive-Green

Click on different sides of the icon to toggle the background colour of the screen image between white and black.

Click on different sides of the icon to toggle

between the At Start and Keystrokes views, i.e. the image of the screen when it first appeared versus the information that was keyed into the screen.

Click on any field on either of the screens to highlight the details for this field on the field list panels.

Field Lists (Errors/Actuals/Expected)

All fields present on the Actual and Expected screens are listed with a green tick indicating a match between the two and a red cross indicating a difference. The Errors view lists the Actual version of only those fields with a red cross. The highlighting of differences is affected by the checking options in place.


TestDrive-Green

Double clicking any field on the Expected list will cause the Field Properties panel to appear in view only mode (see later section). Alternatively right click and select the ‘Edit/View’ option. Click on any field in the list to highlight the details for this field on the screen images.

Pass/Fail Results

If the option has been selected in the TestDrive-Green Options window - see earlier section TestDrive-Green Options - after clicking on the button to save results, a window will be displayed so that the status and comments can be recorded for each Test Item selected at the start of the run. The list of selected Test Items can also be changed here.


TestDrive-Green

Variable Data Variable Data allows you to record shorter, more flexible Scripts and is thus a key feature of TestDrive-Green. For example, let’s imagine that you want to stress test the ‘Add a Customer’ function. One option would be to record a Script that adds a single customer and then set the Script Option, ‘Number of Runs’ to 100. However, there is a problem with this approach. The Script would successfully add the first customer, but all the following 99 attempts might be rejected with a ‘Customer already on file’ error message as the Script uses a fixed value for the Customer Number. Without Variable Data the only alternative is to record a Script that is one hundred times longer and contains the details of one hundred different customers. This would take much longer to record and be almost impossible to maintain if the screen layouts for the ‘Add a Customer’ function were changed at any time in the future. Variable Data allows you to feed selected Data and Constant fields with external information, rather than using the fixed value that was recorded. You can therefore record a Script that adds a single customer but then select the Customer Number and perhaps the Customer Name to be fed not as the record constant, but by fields.

Access Variable Data

There are two types of Variable Data Sets that can be used in TestDrive:-Green Local Variable Data is stored with the individual Script and can only be used by the one Script. Public Variable Data Sets are stored at the Project level and can be utilised by any Script within the Project. Variable Data Sets for use in TestDrive-Green can be accessed in two places: 1. Public Variable Data Sets can be accessed at the Project level in


TestDrive-Green

TestBench-PC - see separate TestBench-PC chapter for more information.

2. Both Local and Public Variable Data Sets can be accessed from the

Script Options panel in TestDrive-Green - see screen print below.

Use Variable Data Indicates whether the Local or a Public Variable

Data Set will be utilised by this Script. The default value is Local and this will be displayed even if no variable data has been defined. The Variable Data Set being used can be changed by right clicking the desired Set in the list and clicking on the Select button.

Right click on any of the Variable Data Sets in the list to obtain the following options: Select Use this Variable Data Set during the playback

of the Script (the ‘Use Variable Data’ Script


TestDrive-Green

Option must also be checked). Create Create a new Public Variable Data Set. The

Edit Variable Data Panel will be displayed - see the following section for more information.

Edit Change the Variable Data Set. The Edit

Variable Data Panel will be displayed - see the following section for more information.

Delete Remove the Variable Data Set. A confirmation

screen is displayed prior to the deletion taking place.

Edit Variable Data

The following panel is displayed when a Local or Public Variable Data Set is edited.


after the column in which the right click


TestDrive-Green

occurred. Insert Row(s) After Add the specified number of empty rows


Insert Clipboard Rows If you have data in another windows application,

such as a spreadsheet, you can use copy and paste to populate the variable data field names and values. You will be asked whether or not the data being copied contains a header row (field names) or only the transaction data.

Column Options

When at least one field has been added some additional options are available on right click on the field name column headings. This screen is cursor sensitive, the options listed apply to the field on which the right click occurred. In addition to the right click options, columns can be moved simply by left clicking the column header and dragging to the desired new position. Multiple columns are selected by using left click in combination with Shift/Ctrl.


TestDrive-Green

Edit Column Access the Edit Column Details panel which

enables the properties of the field to be defined. This is explained in more detail below.

Remove Column(s) Delete the selected fields and associated

transaction data. When no transactions have been keyed, multiple column deletion is not possible.

Copy Column Add the contents of the selected column to the

Clipboard. Paste Column Insert the data in the previously copied column



TestDrive-Green

Row Options


Remove Row(s) Remove the selected transaction. Copy Row Add the contents of the selected row to the




TestDrive-Green

Data Options






TestDrive-Green

Edit Column Details








separator characters can be used:


TestDrive-Green

dd day portion of date ddd day of the week in upper and lower







Auto-increment If the Active box is checked, the value in the

first transaction for the column will be duplicated into all other columns. If the Value field contains an entry other than zero (only valid for numeric or decimal fields) then each transaction will be incremented by this value. If the initial value is blank then the numbering will start from 1. If any values already exist in any other rows then the numbering will re-start in that position. The same occurs when incrementing is already active and a value is changed.




TestDrive-Green

Playback

When the playback of a Variable Data Script is selected, the Script Options panel enables the starting and ending Variable Data transaction numbers to be selected. If these are left blank then all transactions will be processed. This screen also enables any Variable Data fields containing blank values to be ignored.


TestDrive-Green

Tracked Fields Tracked Fields enable system generated values to be stored and re-used later in the Script. This has two benefits. Differences during playback as a result of these unpredictable values can be avoided. Also, these values can then be used as input on subsequent screens, whereas without Tracked Fields testing would need to be paused while the correct value was added to the screen in question. For example, when a new customer is created the system generates a customer number which is one greater than the last customer used. If data protection is not being used then the customer number will be different every time the Script is re-played. As the customer number appears on all of the customer details screens this would cause differences on playback. One option would be to exclude the customer number from the comparison, but this means that if the customer number were displayed incorrectly this would be missed by TestDrive-Green. Therefore the customer number can be placed into a Tracked Field and this field can be used for comparison purposes for all occurrences of the customer number on subsequent screens.


TestDrive-Green

Edit Tracked Fields

This tracked field could also be used as input on the customer enquiry screen so that the customer details could be viewed within this Script.

Add Create a new Tracked Field which can then be used by any Script in the Project.

Delete Remove the field. If the field is currently in use

by any Scripts then the delete is prevented.


TestDrive-Green

Script Security If security has been activated within TestBench then the access for a specific User to Scripts within TestDrive-Green may be restricted. There are several authority states which are indicated by the text at the bottom left of the TestDrive-Green panel. No authority The User has no authority to the Project. The Project

and Test Case can be selected but no Scripts will be shown.

View The User can view Scripts within this Project but

cannot change them or play them back. Execute The User can view and play Scripts but cannot

change them. All authority The User has full access to the Scripts within this

Project.


TestDrive-Green


TestDrive-Gold

4 TestDrive-Gold

Introduction TestDrive-Gold comes with a simple, easy-to-learn interface, behind which lies a powerful leading edge Windows and Web testing solution. TestDrive-Gold is designed to deal with standard Windows controls and any application which has implemented the Microsoft Active Accessibility Standard, including languages such as .NET, Visual Basic, Delphi, Visual Lansa, Coolplex, JWalkTM or typical ‘screen-scrape’ products. The major elements - record and playback, maintaining & editing scripts, storage, analysis and presentation of results - have all been designed to offer maximum efficiency and functionality with minimum complexity. With TestDrive-Gold, you will speed up the application development process immediately - and improve quality dramatically. And you do not even have to learn a scripting language! TestDrive-Gold also integrates with our market-leading testing suite, TestBench. In this configuration, transactions are followed from arrival on the server, through all database effects, program calls and other interactions to final results – true end to end testing of complete client server and e-commerce transactions. In summary, TestDrive-Gold provides:- • Recording of windows, input and navigations to form Scripts. • Re-play of those Scripts with automatic verification of the actual

results against those expected or against pre-defined rules. • Optionally when integrated with TestBench, TestDrive-Gold ensures

that a consistent environment is set at the start of each test execution • Optionally when integrated with TestBench, TestDrive-Gold triggers

Test_IT to ensure that the database and reports are verified along with the screens.


TestDrive-Gold

Platforms

The TestDrive-Gold repository can run on the following platforms:- • IBM iSeries (includes integration with TestBench) • Oracle (includes integration with TestBench) • SQL server • Access database (for evaluation purposes only)

Browser Requirements

TestDrive-Gold can be used with Microsoft Internet Explorer version 5.5 or later with a recent service pack. No other web browser products are supported.

System Requirements

Minimum Spec Recommended Spec Pentium III 1.0 Ghz 128MB Memory

Pentium IV 2.0 Ghz 512MB Memory

• Windows 2000, Windows XP or Windows Vista. • Client Access Express V5R1, iSeries for Access with a recent

service pack.

Getting Started

TestDrive-Gold is installed when TestBench-PC is installed. TestBench-PC provides a GUI interface into some of the features that can also be accessed by TestBench on the iSeries. Once a validation code has been registered, TestDrive-Gold is launched by clicking on the TestDrive-Gold button at the bottom of TestBench-PC. See the TestBench-PC User Guide for more information.


TestDrive-Gold

The Main Panel The TestDrive-Gold window is a fixed size and can either remain on top of any windows from other applications when either recording or playing back a script so that the controls are available, or it can be minimised.

Toolbar Buttons Open Opens an existing script, which is attached to a

Test Case and Project. This function is always enabled. If a Script is already open and changes have been made to it since it was last saved, you are prompted to save the changes before it is closed and another Script opened.

Save Saves an updated Script to its existing name and

location. You may use the right click options on the save panel to add, amend or delete Projects and Test Cases.

Delete Deletes the current script. A confirmation screen

is displayed before the deletion takes place. Record Initiates the recording of a new Script. Clicking

record while a Script is open allows new screens to be inserted into the Script.

Playback Initiates the playback of the currently opened

Script.


TestDrive-Gold

Stop Ends the recording or interrupts the playing of a Script. This can also act as a Pause button, as the playback of the Script can be resumed.

Take Picture TestDrive-Gold contains comprehensive logic to

decide when a screen picture should be taken during recording. However, if the user has made significant changes on a screen and would like to record this intermediate stage for comparison during playback then clicking on this icon causes an additional picture to be taken.

Filter Two configuration settings relating to the

Contents panel are controlled by this toolbar option.

If the ‘Show Content Structure’ option is checked, the elements in the Contents panel are shown in a multi-level tree structure where the parent of each control is clearly visible. If this option is left unchecked the elements are presented in a simple list form.

If the ‘Show Blank Elements’ option is left unchecked, only elements with a non-blank value for their core properties will be included in the Contents list. The core properties are those which appear in bold within the Element Properties panel and are used for comparison at playback time. If this option is checked then all elements will be listed.

Options Display the Options for TestDrive-Gold which

contain the configuration settings for recording and playing back scripts – see later section for full details.

Help Access the online TestDrive-Gold help

information. The TestBench Help application needs to be installed separately.

Menu Options Note: This section only lists the options which have not already been


TestDrive-Gold

explained above. File Close Closes the existing script but leaves the

TestDrive-Gold application open. If changes have been made to the Script since it was last saved, you are prompted to save the changes before it is closed.


the Script to be saved with an alternative name or to a different Project and Test Case. As such it can be used to create a copy of an existing Script.


support integration with Mercury Quality Center and enable you to launch a particular Script without going through TestBench-PC. To use the file in Quality Center simply add it as an attachment as you would any other PC file. To launch outside of Quality Center simply right click the file and select ‘Launch’. By specifying additional options in the wizard that is displayed launch files can also be used for unassisted playback via a scheduler. See the section in the TestBench-PC chapter for more information.

Exit Close TestDrive-Gold. This option is not

available when recording, inserting screens, playing back a Script or viewing Results. If a Script is open and changes have been made to it since it was last saved, you are prompted to save the changes before it is closed.

Script Show Tracked Field History This provides a history of all of the tracked field

activity during the current execution of the Script. The option is only enabled during


TestDrive-Gold

Playback. Properties Open the Script Properties panel, see later

section for more information. Tools Preferences Edit the User Preferences, see the following

section for more information. Options Display the Options for TestDrive-Gold which

contain the configuration settings for recording and playing back scripts – see later section for full details.

Diagnostics To be used only in conjunction with your

support contact for troubleshooting purposes. Help Check On-Line Connects to the support area of the Original

Software web site, from where for example support questions can be submitted or latest product versions downloaded.





Edit User Preferences

This panel is displayed after selecting ‘Preferences’ from the ‘Tools’ menu option.


TestDrive-Gold

During recording, switch application to Defines the format that TestDrive-Gold will take

while in record mode. Choose between ‘Nothing’, in which case TestDrive-Gold remains in full screen mode but can be minimised if necessary, or ‘Compact’ mode whereby only the screens panel is shown and the list of screens is build up as the script is recorded. There is an Expand/Collapse button which enables the view to be changed during recording.

During playback, switch application to Defines the format that TestDrive-Gold will take

while in playback mode. Choose between ‘Nothing’, in which case TestDrive-Gold remains in full screen mode but can be minimised if necessary, or ‘Compact’ mode whereby only the screens panel is shown and the list of screens is build up as the script is re-played. There is an Expand/Collapse button which enables the view to be changed during playback.


TestDrive-Gold

Stop the playback process with CTRL + x Although there is a Stop button present on the

TestDrive-Gold panel during playback, because the mouse is being moved by the toll it can sometimes be difficult to click on. Therefore an alternative is to use the Ctrl key in combination with the keystroke specified here.

Edit test items Check this option to be prompted to select test

items at the beginning of a test run and to record the status of the items at the end of the run. See later section for more information.

Activate Integrated Starts (Test_IT) Determines the default ‘Activate Test_IT’ Script

level option for all newly created Scripts.


TestDrive-Gold

Options The Options control the settings that affect the recording and playing back of scripts using TestDrive-Gold. Access this panel from the Tools menu, by clicking the Options button on the toolbar or by right clicking the name of the currently opened script.

General

The options held within the General tab are the default options that will be applied to all new scripts and are stored with the script when it is saved for the first time. Once the script has been created they can be viewed by right clicking the script name and selecting the Edit option. They are separated into three tabs. The first three sections, Analysis, Take picture on and Wakeup on, can be viewed but cannot thereafter be changed for that script. The latter three sections, Busy sense, Alerts and Miscellaneous can be changed to alter the settings that will be applied when the script is played back. It is very likely that different settings will be required by different types of application, and that personal preference will require variations for different users. Therefore it is possible to save specific options settings to the database under a unique name, to do this key a meaningful name into the box at the top of the form and click Save. They can be re-selected later using the drop down box prior to recording a new script. The form will be updated with the option values selected and when the Accept button is clicked, the local options set is replaced with the selected choices. These will be in force until further changes are made or an alternative set is selected. Use the Delete button to remove the selected set of options from the database. There are several pre-shipped option sets which begin with the characters ‘ORIGSOFT’ which can be used for recording and playing back but cannot be changed.


TestDrive-Gold

General Tab

Playback

During playback, set activity timeout to x seconds The maximum number of seconds that

TestDrive-Gold will wait between each screen for a response from the application before the script is paused. At this point the user can choose to enter the timeout loop again and wait for the specified number of seconds for activity to finish, or stop the playback. The default value is 15 seconds, the maximum is 86400 seconds (one day).

During playback, set an error limit of x errors Allow the selective termination of the script if

the error threshold is reached. This enables the prevention of unnecessary replay when sufficient errors have already been identified so as to necessitate action. The user can choose to continue with script playback at which point the error count is re-set, or stop the playback. This value is zero by default, which means that there is no error limit on playback.


TestDrive-Gold

Web and GUI Tab

All options with no symbol to their left are applicable to both Web and GUI applications. Those options with a world symbol apply only to Web applications, those with a document symbol are relevant to GUI applications only.

Analysis This first set of options controls the level and nature of the information that is recorded.

For each element, do not capture more than x items This option applies to Combo boxes, List boxes,

List views, Tree views, in fact any control that can contain more than one item. It determines


TestDrive-Gold

the maximum number of items that will be recorded and hence compared during playback. 100 items is the default value.

Generate real pictures using a quality level of x % Adjust the quality of the pictures that are taken

of each screen in the script, which will affect the image size. The default value is 75%.

Wait for replacement screen similarity to be x % One of the properties that TestDrive-Gold stores

against every screen in a script is the Replacement Count, which can be viewed by clicking on the Screen Properties tab. For most screens this will be zero, which means that no intermediate screens were displayed before the final picture appeared. However some web applications contain screens with a replacement count of greater than zero, for example when a page takes some time to build so an intermediate display shows a progress bar until the final page is ready. Sometimes differences in web application performance between recording and playing back mean that although a screen was recorded with a replacement count of 2, the actual screen on playback only has a count of 1 because it appeared more quickly.

If the replacement count of the actual screen is

lower than the expected, TestDrive-Gold will wait for the amount of time specified by the activity timeout in the Alerts section of the Options (see below) in case another screen does appear. If no new screen is displayed within the allotted time, TestDrive-Gold refers to the percentage value specified against this option to determine whether or not this is in fact the expected screen. If the actual screen is considered to be, in the example above, 85% the same as the expected screen, a picture will be taken and the script will move on. If however the screens are different or if no percentage value has been specified (this is the default


TestDrive-Gold

value), playback will pause and the following prompt is displayed.

Click Wait to enter the timeout loop again and

allow more time for the correct screen to appear, or click on Use Current if the Actual screen is in fact the correct expected screen, at which point a picture will be taken and the script will move on. Stop will halt the playback of the script.

If the expected replacement count is lower than

the actual, if there is no percentage value specified here the screens could be matched too early because TestDrive-Gold will try to match them when the actual count reaches the expected count. Specifying a percentage as above will only cause the screens to be matched if they are 85% the same. Otherwise TestDrive-Gold will attempt to wait for a new screen in which case the timeout logic is applied.

Delay analysis for For the majority of applications this value

should be left as zero. However, if for example a java script launches once a web page is complete and new controls are then added to that page, adding a delay of a few milliseconds will ensure that these controls are included in the analysis of the page.

Ignore elements when analysing screen Some applications create blank labels which

then appear in the list of screen contents that have been analysed. Select the option ‘Empty text’ to remove these from the contents list.


TestDrive-Gold

Discard elements hidden by others This option controls whether or not forms that

are fully or partially hidden by other forms within the application are analysed. Ignoring such windows means that if one of these windows contains a difference, this difference will not appear on every screen node within the script when it is played back. It will only be listed once when that screen is in focus.

Discard elements that are located outside the client area This option determines whether elements within

the application which are outside of the boundaries of the visible screen area will be analysed by TestDrive-Gold and included in the Contents list. These elements are discarded if this option is checked, which is the default value.

Discard invisible elements that are inside the client area This option enables items such as invisible

menus to be excluded from the analysis. During analysis, mark all elements as ‘ignored’ All elements on every page in the script will not

be checked for differences on playback. This action can be reversed at the script, page or individual element level. This option is unchecked by default.

Use Advanced Screen Capture This should be on by default and represents the

most advanced technique for capturing screen images. However in some specific cases ActiveX controls are used to re-size forms, an alternative technique must be used and this option should be left unchecked.

For web pages, exclude parameters in comparisons Do not check any parameters in all elements,

commonly found on the page URL or Links within the web page. If parameters are used


TestDrive-Gold

which are likely to vary, for example date and time stamps or policy numbers, this option can be checked to avoid recording screen differences during playback. This option is checked by default.

Start Java Bridge In order to be able to analyse the contents of

simple Java Swing applications, TestDrive-Gold uses the Java Accessibility Bridge. Checking this option will automatically start the Java Bridge in the application under test to enable this content analysis to take place. By default this option is not checked.

Generate Mouse Move inputs for elements with events With this option enabled, a mouse move event is

recorded if the underlying HTML object has either an OnMouseMove or OnMouseOver event handler. This is usually javascript code that might change the web page. It ensures that the same actions are repeated when the script is played back as when it was recorded so that the same results can be achieved. The Mouse Move options are left unchecked by default as they cause additional input to be recorded that in most cases is not required.

Generate Mouse Move inputs for content changes This option waits for the mouse move to be

processed by the web page. If the contents of the entire web page have changed then a mouse move is recorded, ensuring that the same actions are repeated when the script is played back as when it was recorded so that the same results can be achieved. The Mouse Move options are left unchecked by default as they cause additional input to be recorded that in most cases is not required.

Capture Entire Webpage Picture This option should be on by default and ensures

that the entire webpage including the area that may not be visible on most web sites is captured


TestDrive-Gold

and analysed. However, in a small number of situations this may trigger an unwanted action on the web page, in which case the option should be unchecked.

Include additional elements for block matching This option is switched on by default because it

is required if block matching will be used for a script. It causes additional elements to be included in the analysis of each web page, although these items are hidden from view and made available to TestDrive-Gold only when blocks have been created. See later section for more information.

Take picture on These options determine at which points during the test a new picture is recorded of the target application. TestDrive-Gold monitors for activity within the target application and takes a picture when this activity has finished and the application goes “quiet”. These options control which types of activity are included in this process.


TestDrive-Gold

Show window A new picture is taken after a new window has

appeared as a result of activity in the application. For example, clicking on the Help menu and selecting the About option might display a new form.

Hide window Similar to the above option but a new picture is

taken when the window is closed. Show child element A new picture is taken when elements within a

window become visible, for example when a click on a radio button causes further previously invisible options to be displayed.

Hide child element Similar to the above option but a new picture is

taken when the elements are hidden. TCPIP receive During peak times in application activity, if the


TestDrive-Gold

application has been receiving information from TCPIP APIs and this option is checked, once the activity has finished a picture will be taken of the screen. For example, a refresh button might cause an API call to the database to retrieve a list of customer names and addresses, which does not change any elements on the form but does cause new data to be added to a grid.

TCPIP send Similar to the above TCPIP receive option but

relates to information being sent to the server. ODBC activity Similar to the above TCPIP options but

TestDrive-Gold will monitor for the use of ODBC APIs. In this case we monitor for calls to these APIs rather than more specifically any send or receive operations.

API locks Monitor for applications which are not

responding, perhaps for example due to a slow call for information to the network.

JWalk screens Monitor for the activity indicators which are

present on JWalk screens. Active window changes If the active window (the window that currently

has the focus) has changed a new picture is taken. For example, the main application window and the About window are open and you click between the windows without closing either one.

Resize child element Similar to the above option but a new picture is

taken when the elements are resized. Move child element Similar to the above option but a new picture is

taken when the elements are moved. Take picture on AJAX dialogs AJAX and similar techniques enable interactive

web applications to be created, whereby the web page interacts with the server behind the scenes to display new information. As with the above


TestDrive-Gold

option, the entire web page does not have to be reloaded each time the user makes a change. Checking this option causes TestDrive-Gold to take a new picture following http communication with the server.

Ignore child navigations Some web pages perform navigations to

generate, for example, child menus. These navigations are within a child object so the user does not see them, but without checking this option they will be recorded. Check this option to ignore these navigations and reduce the number of pictures taken by TestDrive-Gold.

Content change On some web sites some of the content of the

visible page may change without a navigation having occurred, for example on sites where DHTML is used and a partial refresh occurs. Using these options will ensure that in these situations a new picture is taken.

Item types Select ‘For Input Items’ to cause a

new picture to be taken, as long as the new information contains a field which is capable of taking input. ‘For All Items’ will ensure a picture is taken regardless of the new content type.

Include layering Check this option if you wish

content that is made visible or invisible, for example by the use of tabs, to trigger a new picture.

Wakeup on Normally TestDrive-Gold monitors for activity within the target application and takes a picture when this activity has finished and the application goes “quiet”. It begins to monitor for this activity following some kind of input into the application such as a mouse click or keyboard action. However, sometimes activity is triggered by other events or occurs after a time delay. By default these are not monitored for and


TestDrive-Gold

hence no new picture will be taken if they result in any screen changes occurring. Therefore the wakeup options can be used to monitor for these types of activity and take a picture when the application becomes quiet again. For performance reasons the last three options are left unchecked by default.

User interface activity A picture is taken following any activity within

the user interface. TCPIP receive A new picture is taken after the application has

received information from TCPIP APIs if this option is checked.




Busy sense Busy sense is the technology used by TestDrive-Gold to monitor the activity in the application under test and therefore control when a new


TestDrive-Gold

screen picture needs to be taken.

During activity, use a loop interval of x milliseconds The interval in milliseconds that TestDrive-Gold

will wait before checking if the activity in the application has finished. At this point a new screen picture can be taken. This value might need to be raised if TestDrive-Gold takes multiple pictures for a single screen due to more than one peak in activity from the application under test. In most cases however this can be left as the default value of 32.

For inputs, wait for activity to finish Sometimes an input action might fail to play

correctly because an event generated by a previous input action has not yet completed. Most commonly this will occur where the target element is dynamic and therefore ‘Only for dynamic inputs’ is the default option. However, for applications where this is more widespread the ‘Always Wait’ option can be used. ‘Never Wait’ means that input actions will be played without waiting for any activity to finish.


TestDrive-Gold

For keystrokes, wait for activity to finish Sometimes keystrokes might fail to play

correctly because an event generated by a previous keystroke has not yet completed. This is rare and in most cases this option should be set to ‘Never Wait’. However, for applications where this does occur the ‘Only if System Busy’ or ‘Always Wait’ options can be used, the latter however while more robust will create a slight playback delay between individual keystrokes.

For web pages, wait for activity to finish The default value of ‘Always Wait’ will only

allow a picture to be taken once all residual activity has finished after it has been told that the page is ready, to allow for circumstances where this activity causes a change in the page structure. ‘Never Wait’ means that TestDrive-Gold will take a picture of the web page as soon as it is told the page is ready.


TestDrive-Gold

Alerts These options determine under which circumstances script playback will pause and ask for a decision from the user about how to continue.

Pause when input cannot be played Provide the user with the option to end playback

if any of the recorded input fails to play back, for example because its target element is no longer on the screen. Clicking the Stop button will end the playback whereas Continue will resume playback with the next input in the list. This option is checked by default.

For web pages, pause when page URLs are different Provide the user with the option to exit the

playback if the actual URL is different to the expected, which could mean that the navigation on the web site has changed and the script must be updated. The two options are Stop and Continue. This option is unchecked by default.


TestDrive-Gold

Miscellaneous

Playback in real time This option is unchecked by default, which

means that all scripts will be replayed as quickly as the response times of the application under test allows. However if using the script for example for training purposes, checking this option enables the script to be played back with the same time delays with which it was recorded. This option may also be needed for more complex drag and drop operations.

Playback dynamic input using recorded offset Input is classed as “dynamic” if the target

element for the input was not present on the screen when it was analysed. For example, if a click on a radio button causes a new set of options to be displayed but due to the ‘Take picture on’ options this did not cause a new picture to be taken. If we then click on one of these new options this input would be classed as dynamic. For some types of dynamic input it may be necessary to play back using coordinates


TestDrive-Gold

rather than by checking for the properties of the target element, specifically in situations where lots of similar elements exist. This can be achieved by checking this option.

Check for changes in element location/size When scripts are played back, only the core

properties of each element are compared between the actual and expected screens and potentially highlighted as being different. These core properties do not by default include the size and location of the element. For example, a text box might have increased in size but if its content is the same it will not be marked as being different. Checking this option will cause this to be identified as a difference on playback.

Reposition all forms before the playback starts When checked all windows will be placed in

exactly the same position during playback as they were when the Script was recorded. This may not accurately replicate the application under test and may therefore be undesirable. It does however prevent the situation where a panel was dragged to a new position as part of the test and as a result of a new window start position on playback the panel is dragged out of the PC screen causing any input to fail. This option is checked by default.

Clear browser cache at playback start This option causes any temporary internet files

to be deleted prior to the playing back of a script. This might be necessary to ensure consistent playback when the browser is not closed down in between. There are several options which enable files to be cleared at different points during playback.

First Run Start If the number of runs for this script is greater than one, the files will be cleared prior to the first execution only.

Every Run Start If the number of runs for this script is greater than one, the files will be


TestDrive-Gold

cleared prior to every execution. First Transaction Start Use this option for

variable data scripts to clear the files prior to the playback of every variable data transaction.

Never Do not clear the files. Clear browser cookies at playback start This option causes any temporary internet

cookies to be deleted prior to the playing back of a script. This might be necessary to ensure consistent playback when the browser is not closed down in between, for example when a site requires a User ID and password on first entry only. There are several options which enable cookies to be cleared at different points during playback.

First Run Start If the number of runs for this script is greater than one, the cookies will be cleared prior to the first execution only.

Every Run Start If the number of runs for this script is greater than one, the cookies will be cleared prior to every execution.

First Transaction Start Use this option for variable data scripts to clear the cookies prior to the playback of every variable data transaction.

Never Do not clear the cookies. Screen property to use for caption

We have traditionally used the window caption to provide our screens with meaningful captions. This has the problem that when using a limited-width assist/gold window then all the screens appear to have the same caption, e.g. ‘http://www.origsoft.co…’. A new option has been added which allow the information used in displaying the caption to be customized. Window Caption This is the default and displays what IE displays in its title bar. URL Displays the full URL of the page Page Name Displays the page name or the right-most piece of information if no page is


TestDrive-Gold

available, i.e. the deepest-level folder or the domain if no folder. Page Title Displays the text of the first element within the page which should correspond to the <TITLE> tag of the html. In a multi-framed site the title of the first frame will be displayed.


TestDrive-Gold

5250 Tab

These options are used by TestDrive-Assist when it is monitoring 5250 applications.

Title Position/Line The position on the screen where the screen title

can typically be found. Screens in the Script will automatically be saved with this name.

Include Colours in Analysis If this box is checked, the Check Colours option

for all scripts will be enabled. For PCs running version 3.1.3 of Client Access colour information cannot be retrieved, and some earlier service packs may cause TestDrive-Green to become unstable if colour checking is enabled.


TestDrive-Gold

Screen Analysis

TestDrive-Gold has many options which enable it to record and playback scripts and analyse the content of screens for applications written in a wide range of languages. It uses Microsoft Active Accessibility (MSAA) and Class Rules to define how to interact with the elements on screen and the Messages help to control when screen pictures will be taken. If you are using TestDrive-Gold for the first time over a new application you are likely to achieve a good result because by default it uses Microsoft Active Accessibility to analyse screen contents. This means that TestDrive-Gold will enumerate the contents of every screen using Microsoft Active Accessibility and every control which implements this standard will be analysed without the need for any additional setup. If there are then any specific window components which do not support this standard, Class Rules can be created to retrieve the data by sending and receiving Microsoft Standard and Common Control messages (MSCC). Any controls which do not support either of these techniques will be recorded as a panel and their contents will not be retrieved. In summary: 1 Enumerate and analyse items using MSAA 2 Use Class Rules messages for anything which does not support

MSAA When using Class Rules, TestDrive-Gold will enumerate all of the window controls on every screen and then use the Class Rule definitions to retrieve their content. This does mean that controls without a window handle will not be included in the contents list. See specific sections below for more information.


TestDrive-Gold

Class Rules

When TestDrive-Gold is recording and playing back scripts and the MSAA standard cannot be used, it looks at the names of the windows components on each screen and must convert these to an internal type so that it knows how to interact with the component and obtain the information that is listed on the Content screen. It does this by obeying the Class Rules listed below. For example, a class name of “Thunder*Option Button” will be treated as a Radio Button.

Filter It is possible to filter via the drop down lists as displayed in the screen below, for example by Description or Type. Once a filter has been chosen, click on ‘Apply’ to save the filter. Click on the ‘Hide’ button to return to the full Class Rules display.


TestDrive-Gold

Options The following options are displayed by right clicking anywhere in the Class Rules table. Add Create a new Class Rule - the following screen

is displayed. Edit Change an existing Class Rule - the following

screen is displayed. Delete Remove the Class Rule, a confirmation screen is

displayed before the deletion takes place. Import Retrieve Class Rules from a file and add to or

update the existing definitions. See below for further explanation of this function.

Export Add existing Class Rules to a file. See below


TestDrive-Gold

for further explanation of this function.

Class Rule The name of the windows class that appears in

the application. See the following section which describes the use of special characters in the class rule.

Description User defined description of the class. Internal Type Select the corresponding TestDrive-Gold class

type from the drop down list. This type is used for both analysis and representation purposes. There is one special internal type called Ignore. This should be selected for classes which are either unimportant or whose names are determined dynamically. TestDrive-Gold uses the class names when matching classes on playback so names which constantly change may cause screens to be reported in error when they actually are not.

The new rule will be appended to the end of the list of Class Rules by clicking on the Accept button. The sequence of the Class Rules can be altered using the up and down arrow buttons.


TestDrive-Gold

Pattern Matching The following characters are allowed for Class Rules that use pattern matching: Character Matches ? Any single character * Zero or more characters # Any single digit (0-9) [Charlist] Any single character in Charlist [!Charlist] Any single character not in Charlist If the class name that you want to match includes any of the special characters above, you must include it into brackets. i.e.: Dialogs have class #32770. The class rule for dialogs would be [#]32770. Priority of Class Rules Each Class Rule has a sequence number. Every time TestDrive-Gold tries to find the internal type of a child window it will iterate through the Class Rules starting from the one with the lowest sequence. Low sequence means high priority. The order of the Class Rules is very important and the more specific rules must be higher up in the list. Example: Class Rule “Thunder*RadioButton” must go before “Thunder*Button”. Importing and Exporting Class Rules These functions enable new or missing Class Rules to be added to an existing list on mass, avoiding the need to key each one individually. When rules are exported they are added to a file with the extension .rul, the location of this file can be selected by the user at the time of export. All Class Rules will be added to the file but if only some rules are required the file can be opened using an editor such as Notepad and modified.


TestDrive-Gold

When the Import option is selected you are prompted to locate the file containing the Class Rules. If the format of any of the rules being imported is invalid an error message will be displayed, the rule must then be corrected prior to trying the request again. Once all errors have been fixed a message box containing the number of new rules that will be added and the number of existing rules that will be updated is displayed, the Class Name is used to identify a matching rule. At this point click on Cancel to stop the import or Proceed to continue. The changes to the Class Rules will not however be stored in the database until the Accept button is clicked on the Class Rules screen.


TestDrive-Gold

Messages

TestDrive-Gold knows when to take a new screen picture by listening to the application under test and monitoring for when it becomes “quiet”, i.e. there is no message or CPU activity. Some applications send certain messages constantly and therefore these need to be ignored. These messages are defined in the following table which should only be modified with assistance from your support contact.


TestDrive-Gold

Validation Rules

By default when a script is re-played in TestDrive-Gold, every screen which actually appears is compared against the expected screen stored in the script and any differences are highlighted. Validation Rules provide an alternative to this method in situations where either there is no single correct answer, or the correct answer might be different dependant on other variables. They also enable more complex checks to be performed on the information that is displayed on screen. Using the following display, a library of Validation Rules can be created at the Project level. These rules can then be used by individual scripts, see later section for more information on creating and using Validation Rules.

The following options are available from the right click menu. Add Create a new Validation Rule which can then be

used by all scripts within the Project.


TestDrive-Gold

Edit Change an existing Validation Rule. Delete Remove the Validation Rule, subsequent to a

confirmation screen.

Validation Functions

Validation Functions are used to perform more complex processing that cannot be easily achieved by the Validation Rule wizard. They enable small programs to be created, the results of which can be used by a Validation Rule to compare against a screen field in order to validate it. For example, a Function could be created to calculate today’s date or to retrieve the correct salesperson code for a specific order number. There are two types of Validation Function. A Custom Function must be entirely created by the user and keyed into TestDrive-Gold via a VB script. Alternatively an SQL Function can be created using a wizard which guides the user through checking values in a database file. All of these Functions are created at the Project level and displayed on the screen below. They can then be used by any scripts within that Project. See the later section for more information on using Validation Functions within Validation Rules.


TestDrive-Gold

The following options are available from the right click menu. New Create either a new Custom or SQL Function

which can then be used by all scripts within the Project.

Edit Change an existing Function. Delete Remove the Function, subsequent to a

confirmation screen. Export to Custom Function Converts an existing SQL Function into a

Custom Function so that the underlying VB script can be modified.


TestDrive-Gold

Custom Functions

Custom Functions enable the user to write a VB script to perform more complex processing that is not possible with a simple Validation Rule. When a Custom Function is created or edited the following screen is displayed.

Function Name The name of the Function up to a maximum of

30 characters. The name cannot contain any blanks or special characters and must be unique.

Parameters The names of any parameters required by the

Function. Implementation The VB script which performs the programming

required by the function and calculates the result that can then be used within a Validation Rule. Tracked fields are also available within the function, these can be updated here and then used within the main script.


TestDrive-Gold

SQL Functions

SQL Functions enlist a wizard to assist the user in performing a check against a database table. When an SQL Function is created or edited the following is the first screen to be displayed.

Name The name of the Function up to a maximum of

30 characters. The name cannot contain any blanks or special characters and must be unique.

Click Next to display the following screen which enables a connection to be made to the database which contains the file to be checked. These details will be defaulted to those that are being used for the current TestBench-PC connection and in most cases only the Library name will need to be changed.


TestDrive-Gold

Provider The Microsoft ADO driver name that will be

used to connect to the database. In most cases this value is defaulted and should not need to be changed.

Data Source The server to which the connection will be

made. This is defaulted to the server on which the TestBench database resides.

Library the name of the library on the server in which

the file to be interrogated resides. User name The User ID to be used when making the

connection to the server. Password The Password to be used when making the

connection to the server. Click Next to define the table from which you would like to retrieve a value, the table to be interrogated. Click on a file as shown on the screen below in order to select it or key in the name of the file at the top of the screen.


TestDrive-Gold

Click Next to define how the data should be retrieved from the file by specifying the parameters that should be used for the selection.

There are three possible values for the Include option for each field in the file.


TestDrive-Gold

Blank This field will not be used for the data selection.

Runtime This parameter will be populated at execution time with the contents of a tracked field.

Value A specific value will always be used as the

parameter for selecting this field. This value must be keyed into the final Value column on this screen.

Click Next to define which information will be retrieved from the file being validated. Click on the field whose contents will be returned as the result of the SQL Function and which can then be used within a Validation Rule.

There are five possible values for the option which determines how the return value should be treated. Just return the value The contents of the selected record and field will

be returned. In the above example this would be the First Name of the salesperson being retrieved. If there is more than one record which matched the selection, the contents of the first one is returned.


TestDrive-Gold

Return the number of records A numeric value containing the total number of

records which match the selection criteria is returned.

Return the average of this field A numeric value containing the average of all of

the field values on records that match the selection criteria is returned.

Return the minimum value of this field A numeric value containing the lowest value of

all of the field values on records that match the selection criteria is returned.

Return the maximum value of this field A numeric value containing the highest value of

all of the field values on records that match the selection criteria is returned.

The Function definition has now been completed but can be modified at any time using the Back and Next buttons. Clicking Next on the above screen will display the final screen shown below, from where it is possible to run a test on the SQL Function to ensure that it is working as expected prior to plugging it into a Validation Rule. All of the parameters which have been defined as ‘Runtime’ are listed and for each one a test value must be keyed. At this point click the ‘Test’ button. The file will be interrogated and the results returned. If there is a problem returning the desired results a red cross and an error code and reason is displayed.


TestDrive-Gold

Click Finish to store the Function in the database at the Project level.


TestDrive-Gold

Recording

Instructions

1. Ensure that TestDrive-Gold does not currently have a script open and then click the Record button on the toolbar. The Record Wizard is then displayed.

2. There are two ways to select the application to be tested. All applications which are currently running on the PC are listed and one of these can be selected by clicking the ‘Attach to running application’ radio button and then highlighting the correct application in the list. Alternatively click the ‘Open new application’ option which will cause the specified application to be launched prior to recording. You must specify the location of the application to be launched or the initial URL for browser applications. You can select from a list of all previously launched applications or browse for new ones. Your previous selection is remembered to make repeated testing over the same application easier.


TestDrive-Gold

3. Click the Start button to begin recording, at which point either focus will be placed on the selected application or the specified application will be launched and all activity recorded. Alternatively click Cancel to end the recording process.

4. During the recording process, depending on your product Options

TestDrive-Gold will either remain in full screen mode or reduce to a compact view as shown below. The expand/collapse icon in the top right corner of the form can be used to toggle between these two views. As each new screen appears a picture is taken and every input action is recorded. The ‘Take Picture’ button can be clicked on if significant changes have been made on a screen and you would like to record this intermediate stage for comparison during playback.

5. When you have finished recording, press the Stop button. Click ‘No’ to continue recording further actions in the application or ‘Yes’ to end the recording process and return to the main TestDrive-Gold display.


TestDrive-Gold

6. At this point the script has not yet been saved. It can be modified and re-played, however any features such as variable data and tracked fields which require Project specific data to be retrieved cannot be utilized until the save has taken place. Also the results generated by the execution of the script cannot be stored.

Notes • Browser windows are displayed without the menu options and

toolbars. However, the Back option can be selected from the menu that appears after right clicking within the browser window.

• During the recording process, five icons in the status panel of TestDrive-Gold indicate the type of activity which is being monitored for. Typically it is when all activity stops and the application goes quiet that a new picture is taken. Therefore, if pictures are not being taken at the correct times, noting down which icons are active and conveying this information back to your support contact will help to set the Options correctly. In order from left to right, these icons represent:

- CPU Activity - Messages


TestDrive-Gold

- Windows APIs - Ajax - Web Navigation

• If a control has a scroll bar, the action of clicking and holding the up or down arrows to scroll the contents list will be re-played in real time as the time delay between the down and up click is recorded. However this may not cause exactly the same result on playback due to differences in application response times. Therefore whenever possible it is preferable to use an alternative method to scroll the list, for example drag the rocker button, use single clicks on the up and down arrows or click within the scroll bar to move one page at a time.

• If Alt/Tab is used while recording to access another application, only the Alt is recorded because after this point focus is no longer on the application being recorded. This will not replay correctly and therefore this action should be avoided while in record mode.

• If a browser window is maximized or minimized while in record mode, this action is not repeated on playback and therefore if a specific browser size is required it should be set prior to initiating the record process.

• When an adobe document is launched from a browser, there is a setting inside Adobe which determines whether the document is hosted inside a browser, or simply hosted inside Adobe Reader. Only PDF documents hosted inside a browser can be recorded and analysed correctly. Also, only Version 7 or later of Adobe Reader is supported.

• Please note that when recording on Windows Vista, there is a specific animation function which must be switched off to enable TestDrive-Gold to work correctly. If this option is switched on, a message is displayed. The following steps can be followed to disable the option.

i. Open the Control Panel.

ii. Select ‘Performance Information and Tools’. iii. Click ‘Adjust Visual Effects’ iv. Uncheck ‘Animate controls and elements inside windows’. v. Click ‘OK’.

• No additional load is placed on the server while a Script is being recorded.


TestDrive-Gold

Drag and Drop

TestDrive-Gold supports dragging a file from another application that is not part of the script into the application that is being recorded. It intercepts the drop operation and records this as a specific input type. There is no link or connection to the source of the drag operation as this may not be available at playback time, however the input is recorded with the full path of the file being dropped. At playback time the drag is simulated and the drop over the target application occurs. The input can be edited in order to drop a different file. There are two types of drag and drop, the Win32 implementation and the OLE method. The first is fully supported but there is currently no support for the latter.


TestDrive-Gold

Script Structure While a Script is open it will be shown in the format illustrated below.

Layout Options

The panes on the display can be moved to different positions and also overlain. To move a pane, click on its title and drag it to the new location. To overlay a pane, click on its title and position it over another pane, a tab for each one will appear at the bottom of the pane. The panes can be hidden by clicking on the Pin icon, when this is done a tab for the pane will appear on the left hand side of the screen. To restore the pane to the main view, click on the tab and then on the Pin icon. TestDrive-Gold can store two possible formats for this window, which can be selected by right-clicking on any of the orange window labels.

• Standard – All of the panes with the exception of Expected Contents and Expected Input Properties are a permanent part of the display.


TestDrive-Gold

• Preferred – This is only available if the ‘Set Preferred’ option has previously been selected. It enables an alternative to the above format to be created and stored, this will be specific to the PC being used. Simply adapt the display to suit your requirements and then select ‘Set Preferred’ to create or overwrite the preferred layout.



While the Standard layout can be manipulated, it will continually return to the default setting so the Preferred layout should be used to store any permanent changes to the view. The window can be best explained by considering each of the distinct panes individually.

Script

All screens in the script are listed, the + button to the left of each screen can be used to expand the view to also show the input for the screen. Right click any screen or input in the list or the script name to obtain the following options. The options displayed depend upon the type of element selected. Edit Access the Script Properties, Screen Properties

or Edit Input panel, see later sections for more information.

Delete Delete the screen or the input from the script. A

confirmation screen is displayed before the deletion takes place.

Checking Use these options to specify whether or not this

script, screen or the elements within it will be checked for differences on playback. There are two options, ‘Ignore Script/Screen’ and ‘Set For All Elements’. If the ‘Ignore Script/Screen’ option is selected a flag is set at this level and a yellow cross next to the script or the screen in


TestDrive-Gold

the list indicates that it is not being checked. If the ‘Set For All Elements’ option is chosen the following window is displayed and the include or ignore flag can be set at the individual element level for all elements within the script or screen.

This makes it easier to check only a small

number of elements on a screen. Checking can be switched off for everything and then switched back on for the desired elements by right clicking in the Expected Contents list. Every element which is not being checked will have a yellow cross next to it in this list.

Loop Point Select this screen as the start or end loop point

for variable data transactions, which causes a red down or up arrow to be added to the screen icon. See later Variable Data section for more information.

Verify Script level option to begin the verification

process, see later section for more information. Verification Use the option ‘Always Stop Here’ as a

checkpoint to force the Notification window to be displayed at the selected screen. See later section on Verification for more details.

Click on a screen in the list to show information for that screen in all of the other panels. Click on any input to display an orange box around the


TestDrive-Gold

target element for that input on the screen picture.

Picture

An image of the recorded screen is displayed. If an input action or element in the Contents list is highlighted, the target element is surrounded by an orange rectangle on the display. Conversely, clicking an item on the picture will also highlight that element in the Contents list. There are 3 buttons at the top left of the panel that determine how the picture is displayed.

• 100% - Displays the picture at full size • Page Width - Displays the picture at the width of the panel • Best Fit - Resizes the picture so that the whole screen is visible

within the panel

Right clicking an item on the Expected Picture displays a floating menu with three options. Edit Display the Edit Element screen, see later

section for more information.


TestDrive-Gold

Checking Enables the element to either be checked or not checked for differences on playback.

Create Validation Rule Automatically store one of the core properties of

a screen field within a tracked field and then define a Validation Rule which uses this or any other tracked fields or functions. The following screen is displayed.

Property Use the drop down list to select the core

property of the element that will be stored within the specified tracked field and can then be utilized in the subsequent Validation Rule.

Tracked Field Either select an existing tracked field from the

list or key in the name of a new one that will be used to store the value of the element property.

Element Checking Define whether or not the element on the actual

screen will be still be validated against the expected value on playback. It is quite likely that this kind of checking will no longer be required if a Validation Rule is being created to check the contents of this element.


TestDrive-Gold

When the OK button is clicked, the Validation Rule definition screen is displayed. Please see the later section for more information. Two additional icons above the screen image control the mode that the panel operates in.

• Mouse icon – Default view whereby clicking on an element in the screen image will display relevant information about that element in all other panels.

• Outline icon – Markup mode which enables sections of the screen to be annotated.

Markups

You may wish to annotate specific areas of any of the recorded screens, for example to highlight information which is incorrect and needs to be changed, or for training or documentation purposes. To do this, click on the outline icon above the screen picture. Then use the mouse to drag a box around the area of the screen that you wish to add a comment about. When the mouse is released, a comments box is displayed as shown below.

Description Add some text to describe the issue or

instruction. High Importance If this option is checked, the screen will be

marked with a red exclamation mark.


TestDrive-Gold

Click Accept to add this markup to the screen. The markup is shown below the screen and clicking on it will highlight the selected area of the screen and fade out the rest. Click anywhere else on the screen to return to the full view. The following options are available from the right click menu for a markup. Edit Change the description or importance flag for

the markup. Delete Remove the markup. Any screen which contains a markup will have its screen icon overlain with a dotted box. If any of the markups have been flagged as being of high importance, the box will contain a red exclamation mark.

Contents

The elements included on the highlighted screen are presented in list form. Click on an element to highlight it on the screen picture with an orange rectangle and to populate the Expected Element Properties panel. The Filter button on the main toolbar can be used to modify the appearance and contents of the element list. See the Main Panel section near the beginning of this document for more information.


TestDrive-Gold

Right clicking an item in the list displays a floating menu with two options. The ‘Edit’ option displays the Edit Element screen, see later section for more information. ‘Checking’ enables the element to either be checked or not checked for differences on playback. If an element is not being checked it is displayed with a yellow cross icon in this list.


TestDrive-Gold

Expected Element Properties

The properties pane displays the properties for the currently selected object in the Contents pane. An additional section beneath the main properties panel is populated when a specific property is highlighted. This enables the full list of values to be viewed for any properties that are too large to fit on the main display. Such properties are displayed with three dots at the end to indicate that there is more information that cannot be shown. The properties that appear in bold are those that will be checked for differences on playback. These are different for each element type and are considered the core properties for that type. The only non-core properties that can be optionally checked are the size and location, this is controlled via the TestDrive-Gold options.


TestDrive-Gold

Edit Element

Right click an element either on the screen picture or within the Expected Contents list and select the ‘Edit’ option in order to display the following screen.

Property The properties listed here are considered to be

the core properties for the element and are the ones that will be checked and compared when the script is played back. Therefore these properties will vary depending on the type of element that is being edited.

Click on the Property that you want to edit and

then work with the following options.


TestDrive-Gold

Data Source Tab Value The data contents of this control that will be

used for comparison purposes at playback time. This is the expected value for the element and can be changed here.

Variable Data Field Optionally select the name of a variable data

field. The data within this field in the Variable Data Set being used by the Script will be used for comparison purposes on playback instead of the fixed input that was actually recorded. See the later section on variable data for more information.

Tracked Field Optionally select the name of a tracked field.

The data contained within this field at playback time will be used for comparison purposes instead of the fixed input that was actually recorded. See the later section on tracked fields for more information.

Track Value Tab Use this tab to store the contents of this element for use later in this script or in another script in an Action Map. See the section on Tracked Fields for more information.


TestDrive-Gold

Store Start Value The initial contents of this field when the screen

was first displayed will be captured and stored in the specified tracked field.

Store End Value The final contents of this field after all

keystrokes have been replayed will be captured and stored in the specified tracked field.

Track Field The name of the tracked field which has been

defined at the Project level and which will be used to store the contents of this screen element.

Store Whole Field The entire contents of the screen element will be

stored. Store Part Field Only the specified subset of the screen element

value will be stored.


TestDrive-Gold

Expected Input Properties

Highlight an input action on the Script pane to view further details about that input here. The properties displayed vary slightly depending on the type of input selected.

Type There are two types of input event, keyboard

input and mouse input. Alt/Ctrl/Shift Indicates whether these keys were in an active

(True) or inactive (False) state at the time of the input.

Data The value of any keyboard input. Repetitions If a key is held down so that the same input is

repeated many times, the data value is recorded as a single character, for example ‘a’, and the number of repetitions indicates how many characters were actually keyed. In this example 6 repetitions would actually equate to a value of ‘aaaaaa’.


TestDrive-Gold

Timestamp This is used for internal purposes, for example to calculate time delays during drag and drop operations.

Location The position in pixels of the input operation

relative to the top left corner of the target element.

Element Caption The label associated with the target element for

the input. For example, for a button this could be the visible text such as ‘Accept’ or ‘Cancel’, for a text box it might be the label which appears to the left of it.

Element Text The contents of the target element at the time of

the input. Element Name For elements such as combo boxes or menus for

example, this is the item that was actually selected by the input action.


TestDrive-Gold

Edit Input

The following display is accessed by right clicking an input action on the Script panel and selecting the Edit option, then clicking on the Input Properties tab. Please note that existing input can be changed or removed but new input cannot be added.

Input Type This drop down box allows selection of the

action to be performed. Depending on what is a selected, some additional fields will become active in the window. Some example input types are Keyboard, Right Mouse Click and Mouse Move.

Client X/Y These fields are only displayed if the input

operation was a mouse event. The position in pixels of the input operation relative to the top left corner of the target element.

Repetitions The number of times that the keystrokes will be

typed. Keyboard States Defines if the Ctrl, Alt or Shift keys were active


TestDrive-Gold

during the keyboard input. Changing these could cause a change in the value of the actual input that is replayed.

Play system function This option applies only to keyboard events. If

checked this keyboard event was the function key shown in the selection box, for example ‘Back’, ‘Tab’ or ‘Return’.

Play keystrokes This option applies only to keyboard events. If

checked this keyboard event was the text shown in the text box.

Play Dynamic Input This option is only visible for input that is

considered to be dynamic. This is input over elements that were not present on screen when the analysis took place and therefore are not included in the Expected Contents list. For example, combo box items or drop down menu items.

There are two possible values for this option,

‘By Value’ and ‘By Position’. By default all input, including dynamic input is played back by value. This is important because it means that input will be played back correctly even if the elements have moved. For example, assume a combo box contained the following values at the time of recording and the user clicked on ‘Wednesday’.

Monday Tuesday Wednesday Thursday Next assume that by the time the script is played

back, ‘Tuesday’ has been removed from the list so that it now looks like this.

Monday Wednesday Thursday


TestDrive-Gold

If TestDrive-Gold were to play back by position,

it would incorrectly click the third element in the list which is ‘Thursday’. However, playing back by value causes the input to search for the correct element name of ‘Wednesday’, regardless of position.

However, there may be some circumstances

where playing back dynamic input by value does not yield the correct results. This could occur if there were multiple occurrences of the same value in the list. In these situations the ‘By Position’ option can be selected.

Dynamic input is displayed with a darker orange

rectangle on the screen picture. Variable Data Field Optionally select the name of a variable data

field. The data within this field in the Variable Data Set being used by the Script will be used for input on playback instead of the fixed input that was actually recorded. See the later section on variable data for more information.


The data contained within this field at playback time will be used for input instead of the fixed input that was actually recorded. See the later section on tracked fields for more information.

Pause options The default value for this option is ‘Do not

pause before playing’. However two other options enable the playback of this input to be delayed. ‘Pause until user confirms’ will display a dialog box at playback time and the input is not played until the message is cleared. Alternatively the user can ‘Delay playing this item for’ a specified number of seconds.

Move mouse to safe area after playing input Move the mouse to the top left-hand corner of

the screen after playing this input. This option


TestDrive-Gold

is only required for very specific situations and should be left unchecked by default.

The properties of the target item for the selected input can be displayed by clicking on the Target Element tab.

Variable Data Field Optionally select the name of a variable data

field. The data within this field in the Variable Data Set being used by the Script will be used for comparison purposes on playback instead of the fixed input that was actually recorded. See the later section on variable data for more information.


The data contained within this field at playback time will be used for comparison purposes instead of the fixed input that was actually recorded. See the later section on tracked fields for more information.


TestDrive-Gold

Summary

The Script or Screen Summary panel has several sections within it, each one is described in more details below. The title of each section for which information exists is highlighted, headers for other sections where no data exists are not.


TestDrive-Gold

Tracked Fields

All Tracked Fields in use in this script are listed on this screen. Beneath each field are listed the screen elements for where the tracked field is being used. See later Tracked Fields section for more information. Click on any field in the list to highlight the details for that field on the other Content panels. Click on the ‘click here’ link to define new or modify existing tracked fields for the Project. Right click options Edit The Edit Input or Edit Element window is

shown, depending on the type of tracked data selected. Double clicking will also have the same effect.

Delete Remove the input. Checking Specify whether or not this element should be

checked for differences on playback. Create Validation Rule Automatically store one of the core properties of

a screen field within a tracked field and then define a Validation Rule which uses this or any other tracked fields or functions. See the previous ‘Picture’ section for more information.


TestDrive-Gold

Variable Data

All variable data fields in use in this script are listed on this screen. Beneath each field are listed either the input values or the start values of the fields for which the variable data will be used. Click on any field in the list to highlight the details for that field on the other Content panels. Click on the ‘click here’ link to manage the Local and Public variable data sets. Right click options Edit The Edit Input or Edit Element window is

shown, depending on the type of variable data selected. Double clicking will also have the same effect.

Delete Remove the input. Checking Specify whether or not this element should be




TestDrive-Gold

Validation Rules

When the script name is in focus, this panel lists all of the Validation Rules defined for the entire script. There are two levels of Rules:

• Tracked Field. These are effectively defined for the whole script, but will only be applied to screens where at least one of the tracked fields utilised by the rule is populated on that screen. If none of the tracked fields are populated then the Rule is bypassed for the screen. Therefore the Rules at the Tracked Field level are only applied when a relevant tracked field changes.

• Screen Rules. Rules defined at the screen level for individual

screens in the script are always applied, regardless of whether or not any tracked fields are updated on the screen.

The following options are available from the right click menu. Add New Create a new Validation Rule, see the following

section for more information. Edit Modify an existing Validation Rule, see the

following section for more information. Delete Remove a Validation Rule, a confirmation

screen is displayed. Import from library Create a copy of a Project level Validation Rule

which has been defined using the TestDrive-Gold Options at the script or screen level.

Export to library Create a copy of a Validation Rule that has been

created at the script or screen level at the Project level.

When a specific screen is in focus, only the Rules for that screen plus any Tracked Field Rules are listed. Tracked Field Rules that will not be applied to the screen because none of the tracked fields are stored there will have their icon greyed out. When either the Add or Edit options are taken, the following screen is displayed. Please note that each column is only enabled once all previous


TestDrive-Gold

columns in the same row have been populated.

Rule name Key in a description of the Validation Rule up to

a maximum of 30 characters. The Rule name does not have to be unique.

Clause There are two sections to the Validation Rule.

The When clause determines under which conditions the Rule will be applied, if the rest of this line is left blank then the Rule is always applied. The Test clause holds the rule definition. In addition there are three other possible values, ‘And’, ‘Or’ and ‘ ‘ which is used to remove a clause definition.

Value These columns can contain three possible types

of entry. Tracked Field. These can be selected from a

drop down list and are all prefixed with the characters ‘TF_’.

Function. The name of a user created Custom

or SQL Function, the result of which will be


TestDrive-Gold

used as the Value in the rule definition. Choose the ‘<Select a Function>’ option from the drop down list.

Value. A hard-coded value to be used for

comparison purposes. If the ‘<Select a Function>’ option is selected, the following screen is displayed. From here an existing Function can be selected and modified by clicking on the right hand ‘pen’ button at the top of the screen or a new Function can be created using the left hand ‘plus’ icon.


TestDrive-Gold

Blocks

There are occasions when the key goal is to match a ‘block’ of similar data elements within a web page, not necessarily the individual items themselves. For example, when viewing a long list of products where sometimes a new product is added, it is necessary to ensure that on playback all of the details of the same product on the expected and actual pages are matched, even if when the script was recorded the product appeared at the top of the list but on playback it was half way down. To facilitate this matching process, ‘blocks’ of data can be identified on the screen and these are used on playback when matching actual and expected elements. Click on the ‘click here’ link on the Blocks section of the summary panel to launch the Block Wizard. In the following example a radio button which appears in each of the ‘blocks’ within the same webpage has been chosen as the anchor, this is the item or items that will be found in every block and can be used to identify the repeating pattern. To define the anchors, click on one of the repeating items, then hold down the shift key and click on a second item. These two elements will appear in bright red, all other similar items which have been identified as anchors will be given a pale red border.


TestDrive-Gold

When the anchors have been defined, click Continue to view the actual blocks that have been identified as shown below. What this actually means is that during playback, a match of the entire block will be searched for. This means there is no danger that the radio button from one block will be incorrectly matched with that from another block, which could result in a mouse click selecting entirely the wrong company. If the number of blocks that have been identified does not match the number of anchors that were found on the previous screen, a red icon instead of a green one will appear next to the text above the screen picture and the Continue button will be disabled. If this occurs, click the Back button to modify your anchor selection. Only when matching numbers of anchors and blocks are found will the wizard allow you to move to the next stage.


TestDrive-Gold

When the blocks have been correctly identified, click on Continue to select one or more Identity Elements. These are the items that are also found in each block but that will help to identify a block and separate from the others, therefore wherever possible these should be unique. Sometimes one single item is not enough to uniquely identify a block, in this situation a combination of more than one element can be used, for example Product Code and Package Quantity. Click on an item to select it as an identity element, the identity elements found in other blocks will all be highlighted. To select more than one identity element, hold down the shift key. If identity elements were not found in every block, a red icon instead of a green one will appear next to the text above the screen picture and the Continue button will be disabled. If this occurs, click the Back button to modify your selection. Only when matching numbers of blocks and identity elements are found will the wizard allow you to move to the next stage.


TestDrive-Gold

Click Continue to display the final screen in the Block Wizard. This enables error checking to be switched off for all of the elements within the blocks although the rest of the screen will still be checked for differences on playback. This is a sensible option to take if the list of items for which blocks have been defined is likely to change, or if variable data will be used to enable input to be played over alternative blocks.


TestDrive-Gold

Once a Block Set has been defined, it is listed in the Summary panel as shown below. The Block Set header is followed by any input for elements within the block, which is turn followed by the identity elements for the input.

The following right click options are available depending on which item in the block definition was highlighted at the time. To view the blocks that have been defined in the wizard, click on the Block Set header in the Blocks panel. Block Set Edit Display the first screen of the Block Wizard as

described above to modify the block selection. Delete Remove the Block Set. Block Errors Toggle the flag to either include or ignore

differences in block elements during playback.


TestDrive-Gold

This option is also present on the final wizard screen as described above.

Input Edit Open the Edit Input form to modify details

about the input. Delete Remove the input. Identity Element Edit Open the Edit Element form to modify details

about the element. Checking Specify whether or not this element should be



Screen Properties

Information about the current screen which is required by TestDrive-Gold and is placed here for information purposes only.


TestDrive-Gold

Script Options Script Options can be accessed in several ways: 1. Shown when the ‘Playback’ button is pressed for a selected Script. 2. Double clicking the Script Header in a selected script or right

clicking and selecting the ‘Edit’ option. 3. Clicking on the Options button when saving the Script.

Tracked Fields This button will allow any Tracked Fields that

are associated with this Project to be edited. See the separate section on Tracked Fields.

Start Mode Determines whether the specified application


TestDrive-Gold

under test will be launched by TestDrive-Gold at playback time or whether it will be already running and TestDrive-Gold can simply attach to it. If the ‘Launch’ option is selected and the application requires any parameters these can be specified as part of the command.

Application For browser scripts this will be the initial URL

for this script, for all other scripts it is the name and location of the application under test. If the full application path is not known, the browse button to the right of the field allows the application to be located.

Num. Runs The number of times this script should be

executed during the current run. Use Variable Data If the script has been set up to use variable data

this field will be automatically checked. Un-checking this field will cause the script to be replayed with its original fixed values.

Use Tracked Fields If the script has been set up to use tracked fields,

this option will be automatically checked. Un-checking this option will cause the script to be replayed with its original fixed values.

Activate Test_IT Choose whether TestBench facilities are to be

enabled when this Script is executed. Using this option will instruct TestBench to start the Test Case before replaying the script.

If using JWalk, Test_IT gives the capability to

ensure a consistent initial environment, together with database, data area and program parameter verification. In fact all of the TestBench Test Case functionality can be used.

If using another application which makes

database changes on the iSeries or Oracle, you will be prompted for the User ID which will actually be making the changes, or for Oracle the Computer Name can also be used. If the


TestDrive-Gold

Test Case has Environment Protection defined (see the TestBench and TestBench-PC User Guides for details) file effects for this User or Computer for the duration of the test will be captured and stored. Data Rules can also be applied to these files. No other type of Data Protection will have any effect.

See later section entitled TestBench Integration. Variable Data This screen enables any variable data that is

associated with the Script (Local) or data that can also be used by other Scripts (Public) to be edited. See the separate section on Variable Data for more information.

Exceptions

These Script level exclusions are an important addition or alternative to that achieved by excluding individual fields. For example, the time of day may appear on every screen in a Script. One option would be to tune each screen to ignore any differences in the time, but Script level exclusions allow this to be achieved via a single entry. To add an exception right click anywhere in the data entry grid on the exceptions tab and then click the add option. To edit or delete an existing exception right click on the exception and then click ‘Edit’ or ‘Delete’ from the floating menu.

Target Select the type of element that you wish to apply

the exception to from the drop down list.


TestDrive-Gold

Property Select which property of the selected target you wish to exclude from comparison. The properties which are normally checked at playback time are those which appear in bold in the Element Properties panel.

Extent Select ‘All’ if you wish the exception to check

for the value specified in the following ‘Value’ option and ignore errors if a match exists. Select ‘Date/Time’ to ignore elements where the selected property is a date or a time.

Value Specify the value to check for if the Extent is

‘All’.

Options

The values listed here are those values that were set up using the Options toolbar at the time the script was recorded. They are used to determine how the script should be recorded and played back. They are split into six sections, the first three of which are used for recording purposes and therefore cannot be changed here. These are listed for information only. The latter three sections can be changed for this script and these changes will be applied to subsequent executions of the script. See the earlier Options section for a full explanation of all of the values.


TestDrive-Gold

Playback

Instructions

1. Click the Playback button to display the following screen.

2. On the Playback Wizard select the required options. Most of these are

explained in the Script Options section. The Run Description and User Reference are user controlled text fields that are displayed against this run in results. They can be used for any purpose, for example to group multiple runs together via a work request number. The variable data transactions specify which rows in the attached variable data set should be played back for this execution of the script. Click Next to continue with the playback or Cancel to return to the script.

3. The Wizard is displayed from where the application against which the

script should be re-played can be selected. 4. If the ‘Edit test items and scores’ Option is checked the following

screen is displayed. The list of documented items for this run can be tailored either by


TestDrive-Gold

left/right clicking individual items, or by using the two buttons to select or de-select all items. New Test Items can be added or removed for this run only. Any changes to the Test Items are stored back on the server if there is an active connection when the Keep button is clicked at the end of the run to save the results. Once the playback of the script has been completed a similar window is displayed which enables statuses and comments to be entered (see later Scoring Results section).

4. Confirm Playback should start by clicking on the ‘Start’ button. The

screen defaults to playback in either compact or full screen mode depending on your Option setting. If you wish to change this mode during playback, click on the icon at the top right of the display.

5 Depending on your Options, playback may automatically stop when

the first expected screen of the Script is displayed. This screen is compared to the actual screen inn the application and any differences are highlighted. If there are no differences the TestDrive-Gold panel shows a green status bar but if there are it will be red. If this is the correct starting point for the script, click ‘Proceed’ to continue. If this is not the correct starting point, click ‘Cancel’ to stop the run. The details of any errors on this screen can be viewed by clicking on


TestDrive-Gold

the Screen name. It is possible to continue with the playback even if errors have been found on this first screen.

6 The Script will now run. Each screen result collected will be shown in the TestDrive-Gold panel with an indicator light. Similar indicator lights are used at the field level.

• Green – No differences

• Red – Differences

• Orange – Screen not checked

7 The Playback can be interrupted at any time by pressing the ‘Stop’ button. A confirmation message is displayed asking whether or not to stop. This button can therefore act as a pause button by selecting ‘No’ at which point Playback will resume.


TestDrive-Gold

Results Once the execution of a Script is complete or the execution has been interrupted by the user, a panel in the following format is displayed.

Each screen which was presented during the execution of the Script along with its associated input is listed together with a signal light indicating: Green For screens, all items that were actually

presented matched your expectations as defined in the Script or expanded through variable data. For input, the action was successfully played back.

Red At least one item did not match your

expectations or the input was not played back. Orange The screen was not verified as you had

instructed it to be omitted (not checked). The panes on the display can be moved to different positions and also overlain. To move a pane, click on its title and drag it to the new


TestDrive-Gold

location. To overlay a pane, click on its title and position it over another pane, a tab for each one will appear at the bottom of the pane. The panes can be hidden by clicking on the Pin icon, when this is done a tab for the pane will appear on the left hand side of the screen. To restore the pane to the main view, click on the tab and then on the Pin icon. TestDrive-Gold can store two possible formats for this window, which can be selected by right-clicking on any of the orange window labels.

• Standard – The Picture, Properties and Errors panes are a permanent part of the display.

• Preferred – This is only available if the ‘Set Preferred’

option has previously been selected. It enables an alternative to the above format to be created and stored, this will be specific to the PC being used. Simply adapt the display to suit your requirements and then select ‘Set Preferred’ to create or overwrite the preferred layout.



While the Standard layout can be manipulated, it will continually return to the default setting so the Preferred layout should be used to store any permanent changes to the view. The window can be best explained by considering each of the distinct panes individually. Please refer to the Script Structure section for more information about the panels on this display. Errors/Expected Contents/Actual Contents All fields present on the Actual and Expected

screens are listed with a red cross indicating a difference. The Errors view lists the Actual version of only those fields with a red cross. The highlighting of differences is affected by the checking options in place. Click on any field in the list to highlight the details for this field on the screen images.


TestDrive-Gold

Expected and Actual Element Properties The properties which are different in the

Expected and Actual screens are shown with a red cross next to them and the differences are underlined. Click on any property which is too long to fit on the display to show its full contents in the extension area below.

Expected and Actual Picture These panes show the Expected and Actual

screens. The opacity slide when moved to the far left will clear both display panes of everything except errors.

Expected and Actual Input Properties Highlight an input action on the Script pane to

view further details about that input here. Summary Panel – Tracked Fields For each tracked field, two columns list the

before and after values for all tracked fields that were updated on this screen. Right click the tracked field name to copy these values to the clipboard, from where they can be added to a spreadsheet or other storage area.

Summary Panel - Validation Rules All Validation Rules which could have been

applied to this screen are listed, with one of five icons indicating the results.

Greyed out icon. This rule was created at the

Tracked Field (script) level but was not applied to this screen because none of the Tracked Fields referenced within it were updated on this screen.

Amber dash. The When condition on this Rule

was not met and so the Test condition was not executed.

Green tick. The Rule passed.


TestDrive-Gold

Red cross. The Rule failed. Yellow exclamation mark. There was an error

when the Rule was executed, for example a screen level rule used a Tracked Field which has not yet been populated.

Hover over any of the Tracked Fields used by

the Rules to view their contents at the time of execution. Alternatively right click a Rule and select the ‘Show Values’ option to toggle the entire panel to this view.

Markups

You may wish to annotate specific areas of any of the screens in the results, for example to highlight information which is incorrect. To do this, click on the outline icon above the screen picture. Then use the mouse to drag a box around the area of the screen that you wish to add a comment about. When the mouse is released, a comments box is displayed as shown below.

Description Add some text to describe the issue or

instruction. Flag As Error If this option is checked, the screen will be

marked with a red cross and a warning created in results.


TestDrive-Gold

Click Accept to add this markup to the screen. The markup is shown below the screen and clicking on it will highlight the selected area of the screen and fade out the rest. Click anywhere else on the screen to return to the full view. The following options are available from the right click menu for a markup. Edit Change the description or importance flag for

the markup. Delete Remove the markup. Any screen which contains a markup will have its screen icon overlain with a dotted box. If any of the markups have been flagged as being in error, the box will contain a red exclamation mark. All markups are printed on the results report.

Pass/Fail Results

If the option has been selected in the TestDrive-Gold Options window, after clicking on the Keep button to save screen results, a window will be displayed so that statuses can be recorded for each Test Item selected at the start of the run. The list of selected Test Items can also be changed here.


TestDrive-Gold

Amending Scripts In the event that changes occur to the system under test for which Scripts already exist, it is possible to easily change these Scripts. Changes that can occur are: • Extra screens can be recorded and inserted into existing test Scripts

(see below). • Incorrect or surplus screens can be deleted from existing test Scripts

(see below). • Both the screen content and input events can be changed to cater for

changes (see earlier sections relating to Script Structure). • Any variable data that has been set up for a Script can be altered (see

later section). • Validation Rules can be modified. • The Scripts that will be run as part of an Action Map can be

changed. • Scripts which have been ‘healed’ as part of the Verification method

will have been changed (see later chapter for more details).

Deleting a Screen

To delete a screen from an existing Script: 1 Open the Script that requires changing and click on the relevant

Screen name. 2 Right click and select the ‘Delete’ option. You will be asked to

confirm that deletion is required. 3 On confirmation the screen will be deleted. 4 Save the Script. Care must be taken in the event that Start & End Loops have been specified within the Script, especially if the screen being deleted is marked as either one (see Variable Data section).


TestDrive-Gold

Inserting a Screen

To insert a screen into an existing Script: 1 Open the Script that requires changing and optionally click on the

Screen name before the point at which you want to insert a new screen.

2 Ensure that the system application under test is on the correct screen for recording.

3 Press the Record button. The following screen will be displayed.

4 Click the Replace option of you wish to delete the existing script and

create a new one. Click the Insert option if you wish to add some new screens to the current script and specify the desired location of the new screens. Click Next to continue or Cancel to return to the original script.

5 The Record Wizard is displayed from where the application containing the new screens to be recorded can be chosen. At this point TestDrive-Gold will go directly into ‘Record’ mode with the focus placed on the selected application. Commence the required testing and when finished press the ‘Stop’ button.


TestDrive-Gold

6 Play back the script to verify that the screens have been captured correctly and then save the changes.

Script Verification

This function can be used when more significant changes have been made to the application rendering existing scripts out of date. When the script is played back in verify mode, the old screens will be replaced with the new ones and TestDrive-Gold will attempt to transfer all field information from the old to the new elements. In order to do this it attempts to match elements on the old screens to those on the new ones, once a match has been found it attaches existing input, variable data, tracked fields and checking flags to the new element.

Verification Options

A verification run is begun by right clicking the Script name and selecting the ‘Verify’ option. The Verification Options screen is then displayed which enables the options that control the verification run to be modified. Notification These options control the conditions under which playback will halt to request manual intervention when elements cannot be matched. If matching does not successfully occur any input, variable fields, tracked fields or checking flags defined for an existing element will not be retained by the corresponding element on the new screen.


TestDrive-Gold

Any field If any fields cannot be matched the verification

screen will be displayed so that these fields can be matched manually by the User.

Core fields only The verification screen will be displayed for

manual matching only when existing core fields cannot be matched. The second Notification Option as described below determines which elements should be treated as core fields.

Core Fields Use these check boxes to determine which elements should be regarded as core fields, which is important when determining the level of user intervention required in the matching process as described above. The settings on the screen below specify that a core field is an element which has either input, variable data or tracked fields associated with it. If the ‘Core fields’ notification option is selected, the user will be given the option to manually match any such fields where automatic matching fails.


TestDrive-Gold

Click on the Next button to select the application under test from the Verification Wizard. When the verification run has complete, choose whether or not to overwrite the existing script. The changes will not be saved however until the Save option is taken.

Notification

When elements cannot be matched, the following variation of the main TestDrive-Gold panel is displayed to enable manual intervention in the matching process. It is initially displayed in compact mode but can be expanded to full screen mode by clicking on the expand icon at the top right of the display. The notification level (which is explained in more detail above) determines whether this screen is displayed when any unmatched fields are encountered or for core fields only.


TestDrive-Gold

Core Fields Provides a summary of all of the matched and

unmatched core fields. Errors The Errors tab shows any differences between

the expected results and the actual results in terms of the elements on the screen. Elements where an error exists are shown by the use of a red cross and a description of the error to the left of the object. The object will be highlighted on both the Expected and Actual screen displays (if found in both).

The panes can be moved to different positions and also overlain. To move a pane click on the panel and drag it to the new location. To overlay a pane, click on the panel and position it over another panel, a tab for each pane will appear at the bottom on the pane. The panes can be hidden by clicking on the Pin icon in the panel, when this is done a tab for the panel will appear on the left hand side of the screen. To restore the panel, click on the tab and then on the Pin Icon. The areas of this screen that have not been explained in either the Script Content or Results sections of this chapter are described below.


TestDrive-Gold

Core Fields The following display is split into two parts, Missing Elements and Matched Elements. For all elements listed, the four icons in the header bar determine whether the object has any associated input, variable data, tracked fields or if the element is not being checked for differences. These four properties are used to determine whether or not an element is a core field, depending on the options that were selected at the start of the verification run.

Any core fields that were present on the expected screen for which a match cannot be found on the actual screen are listed here. It is possible to proceed with the replacement of the expected screen without matching these elements; however any core information will be lost. If an element is present on the actual screen to which this element should be matched, then the two elements can be matched manually and in doing so all core information will be transferred to the new field.

Manual Matching To match a field manually, left click to highlight the element on the Core Fields display and then drag the element to either the Actual Picture or Actual Contents list until the target element is also highlighted. Then release the mouse button to complete the manual matching process. If you matched a missing element, the element will be removed from this list and added to the list of matched elements. If you selected an element from the list of matched elements because the matching was incorrect and have now matched it to a different element on the actual page, it is


TestDrive-Gold

possible that you will see an element added to the list of missing elements. This will be the field that was previously matched to the actual field you have just selected.

Verifying Screen This panel is used to determine the next action to be taken in the verification run. It can be expanded or minimized using the double arrow icon at the top right of the panel.

Replace and proceed This is the default option. The expected screen will be replaced with the actual screen and any core information transferred to the new elements for all fields which have been successfully matched.

Insert new screen The actual screen is inserted into the script

before the current expected screen. This inserted screen will have no associated input so control is returned to the application under test and the user must manually key in any input and navigate to the next screen. When a new screen is displayed the verification process resumes, this screen is then matched to the same expected screen as before.

Keep expected The expected screen remains in the script and

the verification process continues with the next screen, it is not replaced with the new actual screen.


TestDrive-Gold

Discard expected The expected screen is deleted from the script and the actual screen is then re-matched to the next expected screen in the script.

Let me navigate manually

Use in conjunction with any of the above options to pass control to the application under test and allow the user to manually navigate to the next screen. This input will then be recorded as the input of the new expected screen. Once this happens the verification process resumes. This option is switched on by default when inserting a new screen.

Continue Click this button to resume the verification run

once the correct option has been selected.

Matching Options The options on this panel control the level of accuracy of the matching process.

Normal This is the method by which TestDrive-Gold matches

elements on the expected and actual screens during standard playback mode. It will first attempt to match the core properties of the element, but if no match is found the search is widened to include other similar elements.

Medium Elements will only be considered to match if they

share their core properties. If multiple matches of two or more properties exist, all other properties will also


TestDrive-Gold

be compared and the best match chosen. In most cases this will be the optimum matching level.

High All properties of an element are required to be the

same on the expected and actual screens in order for a match to be found.

This panel enables the matching options to be modified. Change the level of accuracy and click on the Rematch button to match expected and actual fields on the current pages at the new level. Click the ‘Apply to future pages’ option to use the new level of accuracy on all subsequent pages in the script. This panel is minimized by default but can be expanded using the double arrow icon.

Notification Options The notification level that was chosen at the beginning of the verification run can be changed here, click on the Set button to apply this change to all subsequent screens in the script. This panel is minimized by default but can be expanded using the double arrow icon.

Notification Reason Displays a message indicating why the verification run has been paused.

Verification Checkpoints

Right click any screen in the Script panel and select the ‘Verification – Always Stop Here’ option from the floating menu to create a verification checkpoint. This ensures that when the script is verified it will always stop at the selected screen. This is important, for example, when a new mandatory field has been added to the application. The verification window is only displayed when existing core fields cannot be matched but verification does not stop when new fields are found. Therefore there is no opportunity to add input for this new field. Using a verification checkpoint the run can be automatically stopped at this screen and input manually added to the new field.


TestDrive-Gold

Variable Data Variable Data allows you to record shorter, more flexible Scripts and is thus a key feature of TestDrive-Gold. For example, let’s imagine that you want to stress test the ‘Add a Customer’ function. One option would be to record a Script that adds a single customer and then set the Script Option, ‘Number of Runs’ to 100. However, there is a problem with this approach. The Script would successfully add the first customer, but all the following 99 attempts might be rejected with a ‘Customer already on file’ error message as the Script uses a fixed value for the Customer Number. Without Variable Data the only alternative is to record a Script that is one hundred times longer and contains the details of one hundred different customers. This would take much longer to record and be almost impossible to maintain if the screen layouts for the ‘Add a Customer’ function were changed at any time in the future. Variable Data allows you to feed selected Data and Constant fields with external information, rather than using the fixed value that was recorded. You can therefore record a Script that adds a single customer but then select the Customer Number and perhaps the Customer Name to be fed not as the record constant, but by fields. Once this has been done simply define the Customer Numbers and Names that are to be keyed in and they will be automatically merged with the Script when it is run. There are five basic steps involved in creating a Variable Data Script:- 1 Record a simple Script to process a single transaction. 2 Access the Script Properties panel by right clicking the Script name

and selecting the ‘Edit’ option. Either create a Public Variable Data Set or add data to the Local set. For controls such as Radio Buttons and Select Boxes the transaction values must be equal to one of the possible list of values for this field. One transaction is equal to one iteration of the Script. Variable data can also be defined for the full contents list of controls such as list boxes. In these cases the transaction data consists of all possible values for the control separated by the | symbol.


TestDrive-Gold

If you have data in another windows application, such as a spreadsheet, you can use copy and paste to populate the variable data values for a field. Use the Insert Clipboard Rows option to paste into the Edit Variable Data window.

3 Check the Use Variable Data box on the Playback Wizard to ensure that the keyed variable data will be used during playback.

4 Link the fields that you have just created on the previous Edit Variable Data panel to the actual controls on the screens so that TestDrive-Gold knows where to key in the variable data. Access the Input for the screen and specify that the keystrokes should come from a variable field. If the data being displayed on any screen can vary then access the contents and specify that the current value and/or content will come from a variable field. If information keyed into any field is displayed on another screen, the current value on that screen can also be made variable to prevent differences being reported during playback.

5 Specify which screens will be the loop points for this Script by right clicking the screen. The loop points are indicated on the Script using red up or down arrows.

Access Variable Data

There are two types of Variable Data Sets that can be used in TestDrive-Gold. Local Variable Data is stored with the individual Script and can only be used by the one Script. Public Variable Data Sets are stored at the Project level and can be utilised by any Script within the Project. Variable Data Sets for use in TestDrive-Gold can be accessed in two places: 1. Public Variable Data Sets can be accessed at the Project level in

TestBench-PC - see separate TestBench-PC chapter for more information.

2. Both Local and Public Variable Data Sets can be accessed from the

Script Properties panel in TestDrive-Gold - see screen print below.


TestDrive-Gold

Use Variable Data Indicates whether the Local or a Public Variable

Data Set will be utilised by this Script. The default value is Local and this will be displayed even if no variable data has been defined. The Variable Data Set being used can be changed by right clicking the desired Set in the list and clicking on the Select button.

Right click on any of the Variable Data Sets in the list to obtain the following options. Select Use this Variable Data Set during the playback

of the Script (the ‘Use Variable Data’ Script Option must also be checked).

Add Create a new Public Variable Data Set. The


TestDrive-Gold

Edit Variable Data Panel will be displayed - see the following section for more information.

Edit Change the Variable Data Set. The Edit

Variable Data Panel will be displayed - see the following section for more information.

Delete The Variable Data Set will be removed after a

confirmation screen has been displayed.

Edit Variable Data

The following panel is displayed when a Local or Public Variable Data Set is edited.


after the column in which the right click occurred.

Insert Row(s) After Add the specified number of empty rows



TestDrive-Gold

Insert Clipboard Rows If you have data in another windows application,

such as a spreadsheet, you can use copy and paste to populate the variable data field names and values. You will be asked whether or not the data being copied contains a header row (field names) or only the transaction data.

Column Options

When at least one field has been added some additional options are available on right click on the field name column headings. This screen is cursor sensitive, the options listed apply to the field on which the right click occurred. In addition to the right click options, columns can be moved simply by left clicking the column header and dragging to the desired new position. Multiple columns are selected by using left click in combination with Shift/Ctrl.

Edit Column Access the Edit Column Details panel which

enables the properties of the field to be defined. This is explained in more detail below.


TestDrive-Gold

Remove Column(s) Delete the selected fields and associated transaction data. When no transactions have been keyed, multiple column deletion is not possible.

Copy Column Add the contents of the selected column to the

Clipboard. Paste Column Insert the data in the previously copied column


Row Options


Remove Row(s) Remove the selected transaction.


TestDrive-Gold

Copy Row Add the contents of the selected row to the



Data Options






TestDrive-Gold

Edit Column Details








separator characters can be used:


TestDrive-Gold

dd day portion of date ddd day of the week in upper and lower







Auto-increment If the Active box is checked, the value in the

first transaction for the column will be duplicated into all other columns. If the Value field contains an entry other than zero (only valid for numeric or decimal fields) then each transaction will be incremented by this value. If the initial value is blank then the numbering will start from 1. If any values already exist in any other rows then the numbering will re-start in that position. The same occurs when incrementing is already active and a value is changed.




TestDrive-Gold

Variable Block Selection

In addition to using blocks to improve the matching process during script playback, their selection can also be made variable so that the input that was originally recorded against one block can actually be associated with a different block during playback. To achieve this, it is the Identity Element for the block that must be made variable, not the input itself. The input remains the same but it must be keyed against an alternative block.

In the above example you might wish to loop around the script several


TestDrive-Gold

times, each time adding an order for a different product. In this case the variable data set should contain the list of Identity Elements for each block that you wish to be selected.

Right click the Identity Element in the Blocks section of the Summary panel and select ‘Edit’. From here the variable data field ‘Product’ can be selected.


TestDrive-Gold

Playback

When the playback of a Variable Data Script is selected, the Playback Wizard enables the starting and ending Variable Data transaction numbers to be selected. If these are left blank then all transactions will be processed.


TestDrive-Gold

Tracked Fields Tracked Fields enable system generated values to be stored and re-used later in the Script. This has several benefits. Differences during playback as a result of these unpredictable values can be avoided. Also, these values can then be used as input on subsequent screens, whereas without Tracked Fields testing would need to be paused while the correct value was added to the screen in question. They can also be used within Validation Rules, please see earlier section for more information. For example, when a new customer is created the system generates a customer number which is one greater than the last customer used. If data protection is not being used then the customer number will be different every time the Script is re-played. As the customer number appears on all of the customer details screens this would cause differences on playback. One option would be to exclude the customer number from the comparison, but this means that if the customer number were displayed incorrectly this would be missed by TestDrive-Gold. Therefore the customer number can be placed into a Tracked Field and this field can be used for comparison purposes for all occurrences of the customer number on subsequent screens.


TestDrive-Gold

Edit Tracked Fields

This tracked field could also be used as input on the customer enquiry screen so that the customer details could be viewed within this Script.

Add Create a new Tracked Field which can then be used by any Script in the Project.

Delete Remove the field. If the field is currently in use

by any Scripts then the delete is prevented.


TestDrive-Gold

TestBench Integration TestDrive-Gold is integrated with TestBench on the iSeries or Oracle, providing several benefits:- • Central, secure storage for Scripts and results. • Option to protect the initial test database on the server so that testing

can be repeated without the need to re-create the test environment. • Full reporting capabilities for all stored test results. Individual Scripts can optionally be integrated further with TestBench, providing the following additional benefits:- • Tracking of transactions after their arrival on the server, providing

database effects and the ability to define expected results using Data Rules.

• Automatic creation of a consistent testing environment on the server. This full Script integration is requested by checking the ‘Activate Test_IT’ box on the Script Properties panel. The User ID or Computer Name which actually performs the updates should then be specified. Further details on reviewing results from tests can be found in the TestBench-PC section of the user guide.

JWalk

If the JWalk product is being used to create iSeries screens in your application, scripts recorded over these screens can be played back fully integrated with the TestBench product. In this way full advantage can be taken of all other Test Case features on offer. To achieve this, a ‘Start-up’ script is automatically loaded onto the local PC at the time of installation. This script will then be used to navigate from the TestBench Main Menu, through launching the relevant Test Case to the first screen of the application under test. At this point the script created by the user will take over to perform the testing. There may be some occasions, perhaps due to a different version of JWalk being used, that the pre-shipped integration script does not successfully launch the Test Case. In these situations it is possible to


TestDrive-Gold

record an alternative script to be used instead of the one that was installed with the product. Please speak to your support contact for details should you need to do this.


TestDrive-Gold

How to create a new Test Case The following is a summary of the typical steps involved in setting up a Test Case to be used in conjunction with TestDrive-Gold. Please note however that if TestBench is simply being used to store Scripts and screen results on the iSeries then only steps 1 and 2 are necessary. Steps 1 to 5 can be completed in either TestBench-PC or TestBench. The functions described in steps 6 to 8 can only be done in TestBench if using the iSeries, but Data Rules can be set up in TestBench-PC if using Oracle. Refer to the separate documentation for each of these products for more detailed information on any of these functions. 1 If required, set up a new Project. 2 Create the new Test Case with a new Test Case code. 3 Depending on how you want it to work, you may wish to use some

or all of the following steps to set up additional optional features. 4 Choose whether the data used by the program(s) is to be protected

from update by TestBench. *NONE No files are protected. The files to be used and

updated are those found in the library list, or accessed by the server programs.

*ENV Use in conjunction with the ‘Environment’ option to specify a Test Environment to be used when running the Test Case. Refer to the ‘Environments’ chapter of the TestBench documentation for instructions on how to create Test Environments.

5 Enter a maximum acceptable error severity for the Test Case if using the iSeries. Any messages added to the job log by the test run which exceed this severity will cause a warning message to be generated by TestBench.

6 If using the iSeries, press F7 to define the library list that the server programs will require at the start of the job. NOTE If using Environment Protection the Test Case library list will be ignored, the Environment library list will be used.

7 Create user-defined commands to be executed at specified points in the test run.

8 Data rules can be defined for the Test Case (as well as for all tests in


TestDrive-Gold

a Project) to check all the updates to protected files during a test run.

Test Run Results Test results can be viewed in both TestBench-PC and TestBench. The following results may be stored for your Test Run, depending on the functions utilised when setting up the Test Case:- • Warning messages • Screen results (Screen content can be viewed in TestBench-PC ` only) • Performance information • Timeline • Server activity • Database effects • Job Log messages • Data Rules • Pass/Fail information For more information please refer to the TestBench-PC documentation or the ‘Results’ chapter in the TestBench User Guide.

Test Reporting Full reporting capabilities for all stored results are present in TestBench-PC or TestBench on the iSeries - please refer to the relevant sections of these User Guides for more information. Please note, TestDrive-Gold screen results can only be reported from TestBench-PC.


TestDrive-Gold

Script Security If the server that you are connected to is the iSeries and security has been activated then the access for a specific User to Scripts within TestDrive-Gold may be restricted. There are several authority states. No authority The User has no authority to the Project. View The User can view Scripts within this Project

but cannot change them or play them back. Execute The User can view and play Scripts but cannot

change them. Full authority The User has full access to the Scripts within

this Project.


TestDrive-Gold

Troubleshooting If the expected results are not being achieved while either recording or playing back using TestDrive-Gold, this can often be resolved by modifying the Options that are being used. TestDrive-Gold is shipped with some standard Options sets for known application types. The following list describes how to resolve some of the most common scripting issues.

Recording Issues

A picture is not being taken when clicking on a tab control within a web page. Most web tab controls use some form of DHTML to simulate the known Windows tab controls. This can be monitored for using the option ‘Take picture on content changes’. Too many mouse moves are being recorded. Try turning the option ‘Generate Mouse Move inputs for content changes’ off. This option should only be used as a last resort if the option ‘Generate Mouse Move inputs for elements with events’ does not record the required input. Extra pictures are being taken when changing the focus between the target application and TestDrive-Gold or another application. Turn the option ‘Take picture on Active window changes’ off.

Playback Issues

A picture is being taken too early (or additional pictures are being taken) so the playback of input fails. Try setting the ‘Wait for replacement screen similarity to be’ option to 50% (experiment with this value). This will make TestDrive-Gold wait for a replacement screen that is more similar to the expected screen than the current actual screen. If you find you need this option to enable reliable playback, you might want to configure your ‘During playback, set activity timeout to’ setting to something more appropriate. If there are no replacement screens, it might be because Internet Explorer is doing some post-document-complete processing. Try setting the ‘Delay analysis for’ option to something like 50ms so we wait for this post-


TestDrive-Gold

processing to occur. Elements within a web page are not being matched correctly. This results in input not playing back. Some web sites are designed around a single page where the multi-page feel is simulated by URL parameters. As default we ignore these parameters in our matching. This results in a link to index.htm?home being treated the same as index.htm?contactus. To resolve this problem, disable the option ‘For web pages, exclude parameters in comparisons’. Playback of some input fails in Lotus Notes, Microsoft Access or another similar application. These applications do not have a 100% implementation of Microsoft Active Accessibility. Try turning on the option ‘Playback dynamic input using recorded offset’. It is also worth noting that any input that requires this option might not correctly playback if the target element changed location. Playback fails for a script that seems to be OK. Always try using the option ‘Playback in real time’ to diagnose whether this is just a timing issue.

Saving Scripts Locally

If a script has been created which needs to be sent to your support contact for help in diagnosing an issue or for any other purpose, this script can be saved to your local PC from where it can then be attached to an email. When this script is open in TestDrive-Gold, hold down the Ctrl key and Right Click the script name to gain access to an additional menu item called ‘Save Script As File’. If this option is selected, the location and name of the new script must be chosen. Click ‘Save’ and then click ‘OK’ on the subsequent ‘Save script to file’ window (the options on this screen are only required when creating JWalk Integration scripts). To load a script into TestDrive-Gold which has been saved locally, first of all ensure that no script is currently open. Then hold down the Ctrl key and Right Click to obtain a list of local scripts in the default location.


TestDrive-Gold


Action Maps

5 Action Maps

Introduction Action Maps allow a set of components to be run in a conditioned sequence. Components are either TestDrive-Green Scripts, TestDrive-Gold Scripts or TestBench functions such as Warp Cases, Plan Cases or Environment Checkpoint manipulation actions. Action Maps allow scripts from different Test Cases and other components within the same Project to be grouped and run together. Action Maps also allow the creation of branches where results in one script can be used to decide which subsequent components will be run. This means that the run sequence is driven by conditions pre-determined by the user – e.g. different script scenarios may be followed depending on whether an invoice is raised containing a positive, negative or zero balance. The logic that enables this conditional execution is what forms the basis of an Action Map. In addition to the above functionality, variable data can be specified at the Map level to enable the entire Map to be repeated for each variable data transaction. For each individual script, either the Map data or the scripts own variable data can be used. This would enable, for example, the Map data to control the addition of new customers with varying properties, and then many orders could be placed for each customer via a script using its own variable data.

Getting Started

Action Maps are accessed at the Project level in TestBench-PC. See the TestBench-PC chapter for more information.


Action Maps

Click the Action Map name within TestBench-PC to display the following options within the Actions and Commands panels. To create a new Map, take the ‘New Action Map’ option when a Project is highlighted. Edit Launches Action Map and opens the selected Map. Copy Copy the selected Action Map to a new Action Map in

the same or any other existing Project. Notes Edit the notes associated with the selected Action Map -

see the Notes section in the TestBench-PC chapter for more information.

Delete Remove the Action Map from the Project. This will not

delete component objects which exist in their own right. Confirmation will be required.

Results View results for all previous runs of this Action Map.

See the Action Map Results section in the TestBench-PC chapter for more information.


Action Maps

Action Map Panel The following panel is displayed when a new Action Map is launched through the Create option in TestBench-PC or via the ‘New’ option in Action Map itself.

Toolbar Buttons

New Creates a new Action Map. Where an existing Action Map is open and has been changed the application will display a warning and enable the Map to be saved.

Open Open an existing Action Map. By selecting this

option you can browse the database to find the required Action Map.

Save Save the current Action Map. Note no

confirmation message will be displayed even where changes have been made to the Action Map.

Delete Delete the current Action Map from the

database. A warning message is displayed


Action Maps

asking for confirmation of the delete request. Playback Playback of the current Action Map is initiated.

This option is only enabled if an Action Map has been loaded. See later section for full details of the playback process.

Options Access the product options where the default

run mode and Map formatting for component names can be adjusted. See later section for details.

Help Access the on-line product Help which can also

be launched via the F1 function key.

Menu Options

Note that only those menu options which are not available through buttons (see section above) are detailed here. File Close Closes the existing Action Map but leaves the

application open. If changes have been made to the Action Map or any of its components, since it was last saved, you are prompted to save the changes before it is closed.


the Action Map to be saved with an alternative name. As such it can be used to create a copy of an existing Action Map.


support integration with Mercury Quality Center and enable you to launch a particular Map without going through TestBench-PC. To use the file in Quality Center simply add it as an attachment as you would any other PC file. To launch outside of Quality Center simply right click the file and select ‘Launch’. By specifying additional options in the wizard that is displayed


Action Maps

launch files can also be used for unassisted playback via a scheduler. See the section in the TestBench-PC chapter for more information.

Exit Close the Action Map application. This option

is not available when recording, inserting screens into Scripts, playing back an Action Map or viewing Results. If an Action Map is open and changes have been made to it since it was last saved, you are prompted to save the changes before it is closed.

Map Tracked Fields This provides a history of all of the tracked field

activity during the current execution of the Map. The option is only enabled during Playback.

Disconnect Session Disconnects the attached iSeries session being

used by all TestDrive-Green scripts, for example so that another application can attach to it or so that an alternative session can be selected. Button is only enabled if a 5250 session is attached.

Properties Displays the Action Map Control window,

please see later section for more details. Help Check Online Connects to the support area of the Original

Software Group web site, from where for example support questions can be submitted or latest product versions downloaded.






Action Maps

Right-click Options

Once an Action Map has been opened the Action Map main panel will have several right-click options as displayed below.

Add Component Add a TestBench component to the Action Map,

which could be a Plan Case, Data Case, Warp Case, Comp Case, Test Case or Script. The component will be added to the Map after the current cursor position. See the Action Map Maintenance section for more details.

Set Checkpoint / Rollback Enables the Action Map to include the setting of

checkpoints and rollbacks to checkpoints. The action of setting a checkpoint or rolling back will be added to the Map after the current cursor position. See the Action Map Maintenance section for more details.

Add Branch Enables the Action Map playback to follow user


Action Maps

controlled logic statements. The branch will be added to the Map after the current cursor position. See the Action Map Maintenance section for more details.

Remove Remove the item from the Action Map. Only the

reference to the component is removed and the actual component is not affected by this action. A confirmation screen will be displayed. If this option is selected for a branch, the branch and all of its components will be removed.

Cut Copies the component within the Action Map

and will remove it when you select where to paste the component, which must be within the same Action Map. If this option is selected for a branch, the branch and all of its components will be moved.

Loop Point Allows the configuration of the Action Map for

variable data usage. See the Action Map Maintenance section for more details.

. Active Determines whether the component highlighted

is marked as Active for the next run. See the Action Map Maintenance section for more details.

Play Control Play Control values can be set to determine

which components within the Action Map will be executed at the next run and can be used as an alternative to the Active flag. See the Action Map Maintenance section for more details.

Play This Action Execute this component only. If this option is

selected, no Action Map results will be stored, results if applicable will exist for the individual component only.

If any of the Add Component, Set Checkpoint/Rollback or Add Branch options are selected while a branch in the Action Map is highlighted, the following window appears.


Action Maps

Inside the branch The component will only run if the condition in the branch is true.

Below the branch The component will run after the branch and its

components, regardless of whether or not the branch condition is true.


Action Maps

Action Map Maintenance The following sections describe the functions involved in creating and maintaining your Action Maps.

Adding Components

To create an Action Map you will need to select the components which will make up the Map. These components can be held within different Test Cases but must all exist within the same Project as the Action Map itself. The component type must be one of Script, Test Case, Data Case, Warp Case, Plan Case or Compare Case. For more details on these different component types see the relevant section within the TestBench User Guide. Right click on any of the nodes in the Action Map and select the Add Component option to insert a new component after the highlighted item. The following screen is displayed which lists all components within the current Project.


Action Maps

For all components other than Test Cases, double click the component or right click and choose Select to add it to the Action Map. As you double click the components will become displayed on the left side of the panel. Continue to add as many components as required. For Test Cases, right click and choose Select to add them to the Action Map, or double click to reveal the list of Scripts which are stored against the Test Case which can in turn also be selected. Toolbar Options Show Types Filter the list of TestBench components to only

those of a specific type, for example Test Cases. If either TestDrive-Green or TestDrive-Gold scripts are selected while viewing Test Cases and other iSeries components, the list will be filtered to show only Test Cases, with those which do not contain any of the requested script type greyed out.


down into Test Cases to display a list of scripts and also move back up to the top level as shown in the above display. The Back button displays the previous component list and can continue to be pressed until the display following the Add Component option is reached.

Go up one level This button is only enabled when viewing

scripts for a selected Test Case and is used to return to the Project level component list as shown above.





Action Maps

Set Checkpoint / Rollback

As well as executing scripts and other TestBench components, you may also wish to control our test data as part of the Action Map playback. This can be done by using Test Environments, please refer to the TestBench User Guide for detailed information about this function. As part of the Action Map a pre-existing checkpoint can be set and data can also be rolled back to an active checkpoint. Right click on any of the nodes in the Action Map and select the Set Checkpoint / Rollback option to insert one of these actions after the highlighted item. The following screen is displayed which lists all Test Environments within the current Project.

Double click one of the Test Environments to display a list of Checkpoints in that Environment. For each Checkpoint the following right click options are available. Roll Back Remove all database changes that have been

made since the checkpoint was set. Set Checkpoint Mark the current status of the database so that

the data can be rolled back to this point in the future and all subsequent changes to the data can be removed.


Action Maps

Toolbar Options Show Types Filter the list of TestBench components to only

those of a specific type, either Environments or Checkpoints. If Checkpoints are selected while viewing Test Environments the list will be adapted to show those which do not contain any checkpoints greyed out.


down into Test Environments to display a list of checkpoints and also move back up to the top level as shown in the above display. The Back button displays the previous component list and can continue to be pressed until the display following the Set Checkpoint / Rollback option is reached.

Go up one level This button is only enabled when viewing

checkpoints for a selected Test Environment and is used to return to the Project level component list as shown above.





Action Maps

Adding Branches

A powerful feature of the Action Map application is the ability to create branches within the Map. This enables events to be driven by the user’s creation of logical arguments. The following panel is displayed when the Add Branch option is selected.

The window is divided into two panels. The panel on the right shows the complete set of conditions which make up the branch. (A condition is a logical test such an A > 10 or b = “Customer”.) An individual condition can allow a Tracked or Variable Data Field value to be compared with a fixed value, or it can allow the values of two Fields to be compared. A branch may include several conditions, linked together with And/Or statements. Use the left hand area to enter the correct selections for the argument you wish to build. As you move to the next column the left hand panel will automatically present the next set of applicable values from which you can select by clicking. And/Or The default and only possible value for the first

condition of any branch is ‘If’. When additional conditions are added to the branch using the Add button a choice of And/Or is available. If an Or condition is specified, any previous lines form a separate condition


Action Maps

and any subsequent And conditions become part of the Or.

. Field The name of the Tracked or Variable Data Field upon

which the condition will be based. This can be selected by either double clicking the required Field when the list of Fields is displayed in the left hand box or by clicking the down arrow in the Field box that appears when you click within it in the table.

There is a special variable data field called ‘*Trans_No’ which is available for all Maps containing a variable data set. This allows the variable data transaction or row number to be used in the logical expression.

Op The valid values are =, <, >, <=, >=, <>, Like. Like

enables wild card values to be used. For example, Error* would include values of Error and Errors.

Comp The two valid entries are Value and Field. Value

enables any string or numeric value to be entered against which the Tracked or Variable Data Field will be compared. Field requires another Project and Field to be selected against which the contents of the first Field will be compared.

Details If the option ‘Value’ has been selected from the ‘Comp’

field then the value in here can be free-text. If the value chosen for the ‘Comp’ field was ‘Field’ then the value for this selection must come from those available in the drop-down.

Right-Click Options Right click any of the expressions in the branch to obtain the following options. Add Add another line to the Branch table so that another

And/Or condition can be keyed. Remove Delete the selected condition from the branch.


Action Maps

Buttons The following are buttons are available for new branches that have not yet been added into the Action Map. Add Add a newly created branch to the Action Map. Cancel Do not add the newly created branch into the Action

Map. The following are buttons are available for branches that already exist in the Action Map. Apply Once the condition is complete and Add has been

selected, the Add button changes to ‘Apply’. Press ‘Apply’ to commit the action to the database.

Undo Reverts back to the previous state before the last

commit/keystroke.

Evaluating Branches

If an Action Map includes branches, the values of the Tracked or Variable Data Fields at the point where the branch occurs will be used to determine which of the later components should be run. If a branch is Not True then the components which depend on the branch will not be executed and they will not appear in the results. The following rules apply when the application evaluates a branch. If the Field value has not been set when the condition is evaluated (this applies to Tracked Fields only), the default Field value is used, blank for alphanumeric fields and zero for numeric fields. If the condition is defined against a number but the Field does not contain a number then the condition is Not True. If the condition is defined against a string but the Field does not contain a string then the condition is Not True. If the condition compares two Fields and one Field contains a number and the other one does not, the condition is Not True.


Action Maps

Action Properties

Click on a component in the list and select the Action Properties tab to view and change the options which control the execution of the component within the Action Map.

Project Read-only description of the Project name in

which the component is stored. Code Read-only description of the Test Case name in

which the component is stored. Script Read-only description of the Script name if this

component is a TestDrive-Green or TestDrive-Gold script.

Active? Indicates whether the component is Active for


Action Maps

use in the next execution of the Action Map. Inactive components appear greyed out in the Action Map list. By default this value will be checked, i.e. Active.

Loop Point If the Action Map has a variable data set

attached, the component can be configured to be a start or end loop point for a variable data set. If a loop point is configured, the component icon in the Action Map list will include a red up or down arrow to indicate this. The default value for this will be ‘None’. See Variable Data section for more information.

Play Control This option enables Action Map playback to be

controlled so that only specific sections of the Map are re-played. For example, the first five components of the Action Map may have already been tested so there is no need to continually repeat these tests. Alternatively, some areas of the application under test may have issues which need fixing meaning that certain scripts cannot currently be replayed. Play Control values of ‘Start’ and ‘End’ enable components at the beginning or end of the Map to be bypassed at execution time. When one of these options has been selected it is indicated by a horizontal green arrow on the icon in the Action Map list. The default value is ‘None’ which means that all components are active.

Variable Data Source This option is valid only for Script components

and it determines which variable data set will be used during Action Map playback. As well as a script containing its own variable data, it is also possible to attach a variable data set to the Map itself. However, only one variable data set can be used by each script. Therefore set a value of ‘Script’ if the scripts own variable data set should be used, in which case when the script is executed it will loop around all transactions prior to the running the next component. Alternatively select ‘Map’ if the variable data


Action Maps

set attached to the Map should be used. In this case the entire Map is looped, each time the script is executed it will use the next transaction in the table. A value of ‘None’ will cause the script to be re-played with fixed values only.

Play Final Screen? This option is valid only for Script components

and it determines whether or not the script will play the keystrokes on the penultimate screen or not. For example, if all scripts have been recorded in an integrated fashion, they may press F3 on the final screen in the script which causes an exit from the application menu and a return to TestBench. However, if several scripts have been combined into an Action Map and Map Integration has been selected, the exit should only be performed by the final script in the Map. The default value is checked, i.e. the last screen of the script will be played. Uncheck the box to instruct the application not to play the last screen of the script in playback, this is indicated by a yellow horizontal arrow on the icon in the Action Map list.

Run in Batch? This option is valid only for non-script

components and controls the run mode of the component on the iSeries. The default value is unchecked, i.e. the component will not run in batch.

Reuse Browsers? This option is valid for TestDrive-Gold scripts

only. If this option is checked, these scripts will not create a new browser into which to play their input but will attach to the browser that was opened by the previous script. This is important if, for example, the web site requires a login but you do not want to have to record this for every script that is created. Therefore the login script could be executed at the start of the Action Map and all subsequent scripts could then begin from the URL following login. This option is ignored for the first TestDrive-Gold script in an Action Map. It is not valid if the


Action Maps

previous script has left more than one browser open, in which case an error message is displayed at run time.

Attachment This and the following two options are only

enabled if the ‘Show target application prompt’ option at the Map level is disabled. This means that for all TestDrive-Gold scripts, instead of selecting a single application at the start of the run, the application can be controlled at the individual script level.

Script Action means that if the script is set to

launch, the application defined in the Command Line of the script will be launched. If it is set to attach, Action Map will attempt to find a running application which matches the application that was running when the script was recorded. Matching is performed by comparing the caption of the first screen in the script with the application that is running, the text must be exactly, although the matching is not case sensitive and ignores leading or trailing blanks. Playback is halted if no match is found.

Attach means searching for an application that

matches the criteria specified by the Target Application and Target Caption properties below. At least one of these properties must be entered, but if both are keyed then both must match. When searching for a match for a running application, there must be only one match, if there is more than one or none that match then a warning is issued and playback will halt.

Launch means that the application specified in

the Target Application field below will be launched. Specify the full path, the executable name if it is found in the System path, or the name of a URL in which case a browser is opened and a navigation to the URL performed.


Action Maps

Target Application If either Attach or Launch is specified in the Attachment option above, this is the application over which the script will be played. It can be the full path, the executable name or the name of a URL.

Target Caption If either Attach or Launch is specified in the

Attachment option above, this is the caption of the application over which the script should be played. Wildcards can be used and if an executable is being specified, include just the name and not the full patch.

Options Click the Options button on the toolbar to control some of the system level Action Map options.

Default Run Mode There are three valid run mode options, ‘Map

Integration’, ‘Script Integration’ and ‘Map No Integration’. For full details on the definitions of these terms see the following Action Map Control section. This screen controls the default value that will be applied to all new Maps but it can be subsequently changed by right clicking the Map name and selecting the Edit option.


Action Maps

Action Descriptions If short names are selected, the component code

and Test Case (for scripts only) is displayed in the component list. The full names option also displays the component type description (for example Data Case) and the Project name.

Show Test Items Determines whether or not the Test Items

defined against the Test Case which has been specified on the Action Map Control screen will be available for selection and scoring at execution time.

Combine results from different scripts If this option is checked, during playback you

will be able to view results for all scripts in one list. If this option is left unchecked, only results for the script which is currently playing back will be visible. Please note however that combinations of TestDrive-Green and TestDrive-Gold scripts cannot be viewed at the same time, only results for the same script type are listed together.

Emulator Session Displays the 5250 session to which the Action

Map product is currently connected and into which any TestDrive-Green scripts will be re-played. If a valid session is selected here you will not be prompted to select one the first time a TestDrive-Green script is played back.


Action Maps

Action Map Control Once the required components have been selected then further settings which customise the Action Map can be modified via the Action Map Control options. These can be accessed by right-clicking the Action Map and selecting the Edit option, they are also displayed when playing back an Action Map and are available from the Save As panel.

General

Run Mode There are three options to select from, ‘Use

Script Setting’, ‘Map Integration’ and ‘Map No Integration’.

Map Integration For TestDrive-Green

scripts, the Test Case which is specified on this panel will be executed on the iSeries when the


Action Maps

Map is launched, therefore the application under test will be ready when the first script is executed. Any additional scripts will be run without launching their own Test Case, hence it is important that only the final script exits from the application under test and causes the close down process to execute. The Play Final Screen option can be used to control this. All results for all scripts will be stored against a single Test Run, but each will have their own separate submit ID.

Map No Integration All scripts will be

executed in a non-integrated fashion, meaning that no Test Case will be launched on the iSeries for TestDrive-Green scripts. However, a Test Case must still be specified on this panel as this is where all results will be stored. All results for all scripts will be stored against a single Test Run, but each will have their own separate submit ID.

Use Script Setting Action Map will look at the

individual script to determine the settings to be used in playback. For TestDrive-Green scripts, if the Script is integrated its associated Test Case will be launched on the iSeries, similarly scripts which do not activate Test_IT will play back non-integrated. However, the default value for ‘Play-Final Screen’ is checked for all scripts and so this may need to be altered. All script results will be stored individually against their own Test Run.

Test Case A valid Test Case within the current Project

must be entered here if using either Map or Map No Integration. For Map Integration it is the Test Case that will be executed when the first TestDrive-Green script is encountered, for Map No Integration it is the Test Case against which all script results will be stored. Click on the Browse button to select from a list of all Test Cases in the Project.


Action Maps

Use Variable Data This option is only relevant if the Map has

variable data attached to it, see the Variable Data section below. If this option is checked, the Map will loop for the number of transactions within the variable data set and any scripts which are set to use Map variable data will use the data within the current transaction or row number.

Show target application prompt If this option is checked, at the start of the

execution the user can select or specify an application that the first script will either launch or attach to depending on the script settings. The behaviour of all subsequent scripts in the map will be determined by their Launch or Attachment setting. If the script is marked to Attach then it will attempt to attach to the last running application used by the Map. If it is marked as Launch, the application in the script properties will be launched and used.

If this option is not checked, additional

parameters on the Action Properties panel at the script level (for TestDrive-Gold scripts only) control the application at the individual script level.

Description Relates to this particular Run only and is

displayed in Action Map Results. User Reference It can be used for any purpose, for example to

group multiple runs together via a work request number and is displayed in Action Map Results.

First Transaction For Maps which have a variable data set

attached, this is the first transaction or row number which should be used. Note this field will be disabled unless the Variable Data field has been checked.

Last Transaction For Maps which have a variable data set


Action Maps

attached, this is the last transaction which should be used. Note this field will be disabled unless the Variable Data field has been checked.

Server User ID This option is only required for Maps which

contain integrated TestDrive-Gold scripts where other results such as database effects are being tracked and stored. Specify the User ID of the job on the server which is making the database updates so that the file changes made by this test only can be extracted and stored in results. If the server is Oracle then the Computer Name can also be used.


Action Maps

Advanced

Number of Runs The number of times the map will be executed.

This must be a numeric value between 1 and 999.

Pause on Initial Screen Determines under which conditions the

playback of the first script will pause on the initial screen of the application, at which time the user must choose whether or not to allow playback to commence. The three possible options are ‘Always’, ‘Never’ or ‘Only on error’ (i.e. if any initial screen differences occur).

If error count exceeds Select a value between 0 and 999. Use this to

force an action to be taken should the number of fields in error exceed the number specified here. The script can either be continued to be played,


Action Maps

paused, at which point the option to continue is available, or aborted.

Tracked Fields This displays the Tracked Field window, which

lists all existing Tracked Fields within this Project. From here changes to existing Tracked Fields can be made and new Fields can be added. For more details see the relevant sections in the TestDrive-Green or TestDrive-Gold chapters.

Variable Data

Variable Data allows you to record shorter, more flexible Scripts and is thus a key feature of the Original Software suite of products. For example, let’s imagine that you want to stress test the ‘Add a Customer’ function. One option would be to record a Script that adds a single customer and then set the Script Option, ‘Number of Runs’ to 100. However, there is a problem with this approach. The Script would successfully add the first customer, but all the following 99 attempts might be rejected with a ‘Customer already on file’ error message as the Script uses a fixed value for the Customer Number. Without Variable Data the only alternative is to record a Script that is one hundred times longer and contains the details of one hundred different customers. This would take much longer to record and be almost impossible to maintain if the screen layouts for the ‘Add a Customer’ function were changed at any time in the future. Variable Data allows you to feed selected Data and Constant fields with external information, rather than using the fixed value that was recorded. You can therefore record a Script that adds a single customer but then select the Customer Number and perhaps the Customer Name to be fed not as the record constant, but by fields. This is taken one step further by Action Maps, which enable many scripts using variable data to be linked together. Let us assume that you have two variable data scripts, one which adds multiple customers and another which adds orders. When these are combined into an Action Map, by default each script will complete all of its own transactions before the next one is executed. Therefore we would have many customers added


Action Maps

by the first script, and then multiple orders added to a single customer by the second. However, it may be desirable to run the first script using one transaction to add a single customer and follow this with the second script to add an order for that customer (customer number could be monitored for using tracked fields). Then once this is complete the first script can run again and add the second customer followed by the second order, and so on until all transactions are complete. In effect we wish to loop around the entire Map, thus enabling us to add one order for each new customer. This can be accomplished using the variable data attached at the Map level. The following steps outline how to achieve this. 1. Record the required scripts and add variable data in the normal way. 2. Add these scripts in the correct sequence to an Action Map. 3. Create a new public variable data set which contains all of the fields

and data transactions required by all of the component scripts. This can be the same data set attached to the individual scripts.

4. Attach this data set to the Map using the Action Map Control form as shown below. Right click the required data set and choose the ‘Select’ option. Please refer to the TestBench-PC chapter for general information on creating variable data sets.


Action Maps

5. Access the Action Properties tab for each script that should use the

Map level variable data and change the ‘Variable Data Source’ value to ‘Map’.

6. If required, set loop points on your Action Map Components using the Action Properties tab to define which elements of the Map should be repeated for each transaction. If no loop points are defined the entire Map will be looped.

Note: It is possible to use a combination of scripts which do not use variable data, which use Map variable data and which use data defined against the Script. All scripts inside the loop points, regardless of which data they use (if any) will be run for each transaction within the Map variable data. However, those using Map data or no variable data will loop through only once, whereas those using Script variable data will loop through all of their transactions each time. Therefore it is possible to add a single customer and then create multiple orders for this customer, then repeat the process for a different customer and so on.


Action Maps

Properties

Project The name of the project where the Map is

stored. Map Name The name of the Action Map. Description This is a free text field and allows a brief

description to be given to the Action Map. This will be stored against the Action Map


Action Maps

Action Map Playback When Playback is selected via the button on the toolbar the Action Map Control screen is displayed to enable the Map options to be customized prior to execution. This is followed by the Test Items screen if the Show Test Items option is checked at the Action Map level. If the Map contains any TestDrive-Green scripts and no session has already been selected, the screen below will be displayed to indicate which of the available sessions you wish to connect to during playback. To select a session, click on it and then click ‘OK’.

If the Map contains any TestDrive-Gold scripts and the ‘Show target application prompt’ option is checked, the screen below will be displayed to indicate which of the available applications you wish to connect to during playback. Alternatively specify an application or web site to launch when playback begins. For each TestDrive-Gold script with a ‘Start Mode’ of ‘Attach’, the script will play back over the application that was last used, ie. the one that was used by the previous script in the Map. If the first TestDrive-Gold script is set to ‘Attach’, this will be the application selected below. All scripts with a ‘Start Mode’ of ‘Launch’ will continue to launch the application over which they will play back.


Action Maps

Playback will then begin. Note that for playback of non-Script components progress will be displayed by a horizontal blue progress-bar. If you proceed with the Playback then the each active script will playback in the Action Map Control window, as shown below. N.B. If the Action Map contains TestDrive-Green and TestDrive-Gold scripts and Web or GUI application is launched from a 5250 screen, an additional TestDrive-Green option will need to be used. The screen in the script which launches the Web or GUI application must have the ‘Restore emulator focus option’ checked and the number of seconds required to give the Web or GUI application time to launch must also be specified. This will ensure that once the application has been launched, focus will be placed back onto the iSeries session so that another TestDrive-Green script can be replayed after the TestDrive-Gold one if required.


Action Maps

Playback can be halted at any time by clicking the Stop button within Action Map. When playback has finished, a message is displayed asking whether or not you wish to keep the script results. Yes Store the screen images and differences. No Do not store any screen results. Prior to saving or discarding the results, it is possible to view the screen differences from the Action Map Control panel by clicking on a script and then a screen in the list as shown below.


Action Maps

Tracked Fields

It is possible to view the history of any tracked field activity for the current Action Map run. To do this, choose the Tracked Fields option from the ’Map’ menu option.


Action Maps

Results The results for the Action Map can also be accessed through TestBench-PC. From the TestBench-PC main window, click the Action Map and then select the View Results option from the Commands panel.

This will display a list of all Action Map Runs as shown on the following screen. The results are stored in the TestBench database by reference to the Action Map and a unique run number.


Action Maps

User A drop down list is available to refine your view

by the User Profile which ran the test. The following options are available from the right click menu for an Action Map Run. Map Entries Show the details of the Action Map Run in another tab

as described below. Delete Remove the Action Map Run and all of the Action Map

Entries.


Action Maps

Map Entries

Right click any of the Action Map Runs and select ‘Map Entries’ to display the following screen showing results for each individual Action Map component.

Sequence The order in which the individual Action Entries

were executed. When the sequence numbers are the same it indicates that the entries were part of the same Test Run, for example two scripts running one after the other over the same test process. The number in brackets then further describes the execution order of these entries.


Action Maps

Result Options

The following options are accessed by right clicking the required entry in the list. However some options are not applicable to every type of entry and may therefore not always be available. Details This includes several options which display the

following detailed results for a Test Run:- - Summary - Warnings - Screens - Timeline - Database - Data Rules - Server Activity - Log - Pass/Fail Report Produce a test report for the Test Run. Further details regarding some of these options can be found in the TestBench-PC chapter.


Manual Testing

6 Manual Testing

Introduction The previous chapters in this User Guide have largely dealt with automated testing. These are scenarios where consistent, repeatable tests can be run over a stable initial environment. However this may not always be possible for a number of reasons. For example, when new functionality has been introduced it is inevitable that manual testing will be required during the early stages of the test cycle. Only when stability is confirmed and any interface changes applied might the user wish to record automated tests to use during the later stages of the test cycle and for future releases. Also when an automated test tool is first employed, it is likely that the core areas of the application will be included first, meaning that the peripheral testing tasks still need to be completed manually. The Manual Testing capabilities within the Original Software products are designed to assist with the testing that is not yet or cannot be automated. It provides documentation and auditing of the tests performed, spell and link checking, the management and storage of results in the TestBench database, integration with test planning so that test tasks can be updated and defects raised, and the option to turn manual test results into automated scripts for future use. The level of manual testing that is provided depends on which Original Software products are in use. In its strongest configuration it covers the entire process from the execution of a test task, storage of screen and database results, to the passing or failing of the results and associated defect management.


Manual Testing

Getting Started Manual Testing is managed from TestDrive-Assist. This can be launched from the shortcut on the TestBench-PC menu within the Original Software program collection. Alternatively it will launch automatically when a task containing steps is executed within TestPlan. This will be covered in more detail in a later section. When TestDrive-Assist is opened for the first time it will have the following appearance. It occupies the right hand side of the screen and all other active applications are automatically re-sized to fill the remainder of the screen size. The width of TestDrive-Assist can be changed by clicking and dragging the left hand border.

TestDrive-Assist needs to use an ODBC connection to connect to the TestBench database into which results will be saved. This can be changed at any time, but the first time that TestDrive-Assist is launched this is the only action that can be performed. Click on the database icon at the top left of the panel to specify the database connection.


Manual Testing

If a TestDrive-Assist license exists, this will be used when it is launched. If there are no free TestDrive-Assist licenses and a GUI or Web application is being tested, any spare TestDrive-Gold licenses will be used instead. The same is not true however for iSeries applications and TestDrive-Green, to monitor a 5250 session a valid TestDrive-Assist license must exist. TestDrive-Assist cannot operate while TestDrive-Gold is either recording or playing back. Therefore if it is open and TestDrive-Gold is used to record or playback a script, TestDrive-Assist will become automatically suspended. Once TestDrive-Gold has finished then it becomes active again.

Connection Parameters

The following window enables the database containing the TestBench application to be specified.


Manual Testing

Connection Parameters Data Source Lists the name of each server for which there is

an ODBC connection available. Only ODBC Data Sources which include the word ‘TestBench’ will be displayed.

Library If using the iSeries as the server this is the


User Name The User ID that will be used to log onto the

selected server. Password The relevant password for the above User

Name. Test Click this button to perform a connection to the

server using the parameters defined above. A message box will indicate whether or not the connection was made successfully. If the connection parameters have changed, click this button to make the new connection and retrieve the available license information. If you change the connection parameters and do not click this button, the old connection will be retained until the Accept button is clicked.

Register Click on this button to access the screen into

which the product validation code can be keyed. This code should be obtained from your supplier. Click on the ‘Details’ button on the registration panel to list out the information that will be required by your supplier before a code can be provided.

Other Automatically launch Determines whether or not TestDrive-Assist will

be launched automatically when the PC is started up.


Manual Testing

Minimize by default If this option is checked, TestDrive-Assist will

be minimized to an icon in the System tray. Right clicking the icon and selecting the ‘Open’ option will maximize it again.

Do not keep more than x results in history When TestDrive-Assist is active it monitors and

records screens for the applications requested. Results are moved to history by clearing them manually or automatically when another application in the list is given focus. This value determines how many sets of results will be stored before the oldest result is discarded. If it is set to 0, old results will automatically be deleted.

Once the connection parameters have been defined, clicking on the Accept button will make the connection to the server. At this point two additional icons are displayed next to the Database icon in the top left of the panel.


Manual Testing

If you intend to use TestDrive-Assist to monitor an application, the application parameters must be defined. Click on the Applications icon (the folder symbol containing a yellow star) or on the link in the summary section above to manage the list of monitored applications.


Manual Testing

Applications

The following window lists all of the Applications that have been defined by all users on this connection. Those applications that will actually be monitored by this PC must be selected by checking the box to the left of the row.

The following options are available from the right click menu. Add Define a new application that could be

monitored for manual testing. See the following section for more details about the application parameters.

Edit Change the parameters for an existing

application definition. Remove Remove an application from the list. If either the Add or Edit options are selected, the following window is displayed.


Manual Testing

Application Tab

Name A user defined description of the application to

be monitored. This cannot be changed when in Edit mode.

Command Applications launched by this command will be

monitored for and tracked by TestDrive-Assist. There are several syntax options for defining the command. 1. Executable name, eg. OE_Demo.exe 2. Executable full path, as shown above. 3. URL path, eg. http://www.origsoft.com 4. Any of the three previous variations also

supports pattern matching: • Con*.exe – Any program that starts

with ‘Con’ and ends with ‘.exe’ • C:\Program Files\Conman\* - Any

program launched from this folder • http://www.origsoft* - Any web page

that starts with www.origsoft Caption As an alternative to the Command definition, the



http://www.origsoft*/

http://www.origsoft/

Manual Testing

caption of the main application window can be used to define when monitoring of the application should begin. The following options exist when defining the Caption. 1. Full window caption, eg. UK Contact

Management 2. Pattern matching, eg. *Contact* If both a Command and Caption are entered, both must match in order for results to be captured for an application. At least one of these values must be entered.

Options When an application is monitored within manual testing, screens will be recorded using the TestDrive-Gold technology. Therefore it is possible to specify here a set of TestDrive-Gold options to use when recording screens. Amongst other things these options determine when a picture of a new screen should be taken. If no set of options is selected, the local set at the time of recording is used.

Edit Options Click on the pencil icon to the right of the

Options field to maintain the TestDrive-Gold options that are selected above. See the following section for those which are relevant for manual testing.

I want my computer to monitor this application Check this box if you would like to begin

recording this application when it is launched or becomes in focus. This has the same effect as checking the box to the left of the row on the previous Applications list.

Finder Tool If the application you wish to monitor is already

open, click and drag the finder tool icon over the main window title bar of the application. This will populate the Command and Caption parameters automatically.


Manual Testing

Quality Checks Tab

I want my computer to spell check this application Check this box if you would like to spell check

this application against the language defined. Please note that spell checking will only be activated if an application is also being monitored.

Language If spell checking will be switched on for this

application, specify the language against which it will be checked. The choices are English (United Kingdom), English (United States), Spanish or Dutch.

I want my computer to link check this application Check this box if you would like to check the

validity of all links within this application. Please note that link checking will only be activated if an application is also being monitored.

Timeout The number of seconds that TestDrive-Assist


Manual Testing

will wait for a response from a link before raising it as being in error.

Check external links If this option is checked, links within other

domains will be checked as well as those within the domain of the application being monitored.

Once your application parameters have been defined and you have selected the application for manual testing, as soon as the application gains focus, TestDrive-Assist will begin recording its screens and input.

Options

The Options control the settings that affect the recording of screens. They can be accessed from the Application panel. Only those which are most relevant to manual testing within TestDive-Assist will be explained here, for further information relating to all of the Options please refer to the TestDrive-Gold chapter. It is very likely that different settings will be required by different types of application, and that personal preference will require variations for different users. Therefore it is possible to save specific options settings to the database under a unique name, to do this key a meaningful name into the box at the top of the form and click Save. They can be re-selected later using the drop down box prior to recording a new script. The form will be updated with the option values selected and when the Accept button is clicked, the local options set is replaced with the selected choices. These will be in force until further changes are made or an alternative set is selected. Use the Delete button to remove the selected set of options from the database. There are several pre-shipped option sets which begin with the characters ‘ORIGSOFT’ which can be used for recording but cannot be changed.

Web and GUI Tab

All options with no symbol to their left are applicable to both Web and GUI applications. Those options with a world symbol apply only to Web applications, those with a document symbol are relevant to GUI applications only.


Manual Testing

Analysis This first set of options controls the level and nature of the information that is recorded.

For each element, do not capture more than x items This option applies to Combo boxes, List boxes,

List views, Tree views, in fact any control that can contain more than one item. It determines the maximum number of items that will be recorded. 100 items is the default value.

Generate real pictures using a quality level of x % Adjust the quality of the pictures that are taken

of each screen in the script, which will affect the image size. The default value is 75%.


Manual Testing

Wait for replacement screen similarity to be x % This option may only need to be modified if the

results will be converted to a TestDrive-Gold script, see that chapter for more information.

Delay analysis for For the majority of applications this value

should be left as zero. However, if for example a java script launches once a web page is complete and new controls are then added to that page, adding a delay of a few milliseconds will ensure that these controls are included in the analysis of the page.

Ignore elements when analysing screen Some applications create blank labels which

then appear in the list of screen contents that have been analysed. Select the option ‘Empty text’ to remove these from the contents list.

Discard elements hidden by others This option controls whether or not forms that

are fully or partially hidden by other forms within the application are analysed. Ignoring such windows means that if one of these windows contains a difference, this difference will not appear on every screen node within the script when it is played back. It will only be listed once when that screen is in focus.

Discard elements that are located outside the client area This option determines whether elements within

the application which are outside of the boundaries of the visible screen area will be analysed and included in the Contents list. These elements are discarded if this option is checked, which is the default value.

Discard invisible elements that are inside the client area This option enables items such as invisible

menus to be excluded from the analysis.


Manual Testing

During analysis, mark all elements as ‘ignored’ This option may only need to be modified if the


Use Advanced Screen Capture This should be on by default and represents the

most advanced technique for capturing screen images. However in some specific cases ActiveX controls are used to re-size forms, an alternative technique must be used and this option should be left unchecked.

For web pages, exclude parameters in comparisons This option may only need to be modified if the


Start Java Bridge In order to be able to analyse the contents of

simple Java Swing applications, TestDrive-Gold uses the Java Accessibility Bridge. Checking this option will automatically start the Java Bridge in the application under test to enable this content analysis to take place. By default this option is not checked.

Generate Mouse Move inputs for elements with events This option may only need to be modified if the


Generate Mouse Move inputs for content changes This option may only need to be modified if the


Capture Entire Webpage Picture This option should be on by default and ensures

that the entire webpage including the area that may not be visible on most web sites is captured and analysed. However, in a small number of situations this may trigger an unwanted action on the web page, in which case the option


Manual Testing

should be unchecked. Include additional elements for block matching This option may only need to be modified if the


Take picture on These options determine at which points during the test a new picture is recorded of the target application. TestDrive-Assist monitors for activity within the target application and takes a picture when this activity has finished and the application goes “quiet”. These options control which types of activity are included in this process.

Show window A new picture is taken after a new window has

appeared as a result of activity in the application. For example, clicking on the Help


Manual Testing

menu and selecting the About option might display a new form.

Hide window Similar to the above option but a new picture is

taken when the window is closed. Show child element A new picture is taken when elements within a

window become visible, for example when a click on a radio button causes further previously invisible options to be displayed.

Hide child element Similar to the above option but a new picture is

taken when the elements are hidden. TCPIP receive During peak times in application activity, if the

application has been receiving information from TCPIP APIs and this option is checked, once the activity has finished a picture will be taken of the screen. For example, a refresh button might cause an API call to the database to retrieve a list of customer names and addresses, which does not change any elements on the form but does cause new data to be added to a grid.




API locks Monitor for applications which are not

responding, perhaps for example due to a slow call for information to the network.

JWalk screens Monitor for the activity indicators which are

present on JWalk screens. Active window changes If the active window (the window that currently

has the focus) has changed a new picture is taken. For example, the main application


Manual Testing

window and the About window are open and you click between the windows without closing either one.

Resize child element Similar to the above option but a new picture is

taken when the elements are resized. Move child element Similar to the above option but a new picture is

taken when the elements are moved. Take picture on AJAX dialogs AJAX and similar techniques enable interactive

web applications to be created, whereby the web page interacts with the server behind the scenes to display new information. As with the above option, the entire web page does not have to be reloaded each time the user makes a change. Checking this option causes a new picture to be taken following http communication with the server.

Ignore child navigations Some web pages perform navigations to

generate, for example, child menus. These navigations are within a child object so the user does not see them, but without checking this option they will be recorded. Check this option to ignore these navigations and reduce the number of pictures taken.

Content change On some web sites some of the content of the

visible page may change without a navigation having occurred, for example on sites where DHTML is used and a partial refresh occurs. Using these options will ensure that in these situations a new picture is taken.

Item types Select ‘For Input Items’ to cause a

new picture to be taken, as long as the new information contains a field which is capable of taking input. ‘For All Items’ will ensure a picture is taken regardless of the new content type.


Manual Testing

Include layering Check this option if you wish content that is made visible or invisible, for example by the use of tabs, to trigger a new picture.

Wakeup on Normally TestDrive-Assist monitors for activity within the target application and takes a picture when this activity has finished and the application goes “quiet”. It begins to monitor for this activity following some kind of input into the application such as a mouse click or keyboard action. However, sometimes activity is triggered by other events or occurs after a time delay. By default these are not monitored for and hence no new picture will be taken if they result in any screen changes occurring. Therefore the wakeup options can be used to monitor for these types of activity and take a picture when the application becomes quiet again. For performance reasons the last three options are left unchecked by default.

User interface activity A picture is taken following any activity within

the user interface. TCPIP receive A new picture is taken after the application has

received information from TCPIP APIs if this option is checked.



Manual Testing



Busy sense Busy sense is the technology used to monitor the activity in the application under test and therefore control when a new screen picture needs to be taken.

During activity, use a loop interval of x milliseconds The interval in milliseconds that TestDrive-

Assist will wait before checking if the activity in the application has finished. At this point a new screen picture can be taken. This value might need to be raised if multiple pictures are taken for a single screen due to more than one peak in activity from the application under test. In most cases however this can be left as the default value of 32.


Manual Testing

For web pages, wait for activity to finish The default value of ‘Always Wait’ will only

allow a picture to be taken once all residual activity has finished after it has been told that the page is ready, to allow for circumstances where this activity causes a change in the page structure. ‘Never Wait’ means that TestDrive-Gold will take a picture of the web page as soon as it is told the page is ready.

Miscellaneous Screen property to use for caption

We have traditionally used the window caption to provide our screens with meaningful captions. This has the problem that when using a limited-width assist/gold window then all the screens appear to have the same caption, e.g. ‘http://www.origsoft.co…’. A new option has been added which allow the information used in displaying the caption to be customized. Window Caption This is the default and displays what IE displays in its title bar. URL Displays the full URL of the page Page Name Displays the page name or the right-most piece of information if no page is available, i.e. the deepest-level folder or the domain if no folder. Page Title Displays the text of the first element within the page which should correspond to the <TITLE> tag of the html. In a multi-framed site the title of the first frame will be displayed.


Manual Testing

5250 Tab

These options are used by TestDrive-Assist when it is monitoring 5250 applications.

Title Position/Line The position on the screen where the screen title

can typically be found. Screens in the Script will automatically be saved with this name.

Include Colours in Analysis If this box is checked, the Check Colours option

for all scripts will be enabled. For PCs running version 3.1.3 of Client Access colour information cannot be retrieved, and some earlier service packs may cause instability if colour checking is enabled.


Manual Testing

Dictionary

Click on the rosette icon on the toolbar to add exceptions for spell and link checking. Four base dictionaries are included for use with spell checking, English (United Kingdom), English (United States), Spanish and Dutch. It is possible to add words to these dictionaries which do not exist in the pre-shipped list, for example names and places.

Language Select the dictionary that you wish to maintain

from the list of four possible languages. Right click to obtain the following options. Add Type a new word that will be added to the

dictionary. Remove Delete the selected word from the dictionary. Find Locate a word in the dictionary.


Manual Testing

Link Exceptions

When a link is checked for validity, one of a large number of return codes is received. All codes which are considered successful must be added to the following panel, these will not be reported as an error by TestDrive-Assist.

It is also possible to exclude specific links from being checked by changing the Exception Type from Return Codes to URLs. Wildcards can be used here.


Manual Testing

Add Type a new Return Code or URL that will be

added to the exceptions list. Delete Delete the selected Return Code or URL from

the exceptions list.

Toolbar

There are three additional icons on the toolbar that have not already been described. Help Launch the on-line manual testing help text. Minimize This removes TestDrive-Assist from view and

places it on the System Tray. It can be identified by the yellow circle icon that also represents TestDrive-Gold. In this mode it is still active and applications are still monitored.

Exit Close TestDrive-Assist.


Manual Testing

System Tray

When TestDrive-Assist is minimized it is placed in the System Tray and can be identified by the yellow circle icon that also represents TestDrive-Gold. The right click menu for the icon contains the following options. Hide TestDrive-Assist This option will minimize TestDrive-Assist

when it is maximized. Open TestDrive-Assist This option will maximize TestDrive-Assist

when it is minimized. Exit Close TestDrive-Assist.


Manual Testing

Performing a Manual Test When all of the connection parameters and applications have been defined, as soon as an application in the list gains focus, the recording process will begin. Each screen is recorded and listed in the Current tab together with any input which can be viewed by expanding the + icon to the left of the screen caption. As each new screen is recorded, an image of that screen appears in the bottom of the panel.


Manual Testing

• During the recording process, five icons on the right side of the status panel of TestDrive-Assist indicate the type of activity which is being monitored for. Typically it is when all activity stops and the application goes quiet that a new picture is taken. Therefore, if pictures are not being taken at the correct times, noting down which icons are active and conveying this information back to your support contact will help to set the Options correctly. In order from left to right, these icons represent:

- CPU Activity - Messages - Windows APIs - Ajax - Web Navigation

If link checking is enabled, the links on each web page are checked by another thread in the background. This means that although you may have navigated away from the page, its links are still being checked. If link checking is in progress, the left-hand icon in the status bar beneath the list of screens is enabled. The application should not be closed until this icon is disabled to ensure that all links have been checked. Red Cross There is at least one error on the screen. Double

click the screen name to view the detailed failures.

Screen Icon This screen does not contain any items that have

failed the spell or link checking and no markups have been flagged as errors.

If at any point during the test a screen has been updated with some information that you wish to record but a picture of that screen has not been captured, click on the Add button on the toolbar to add a picture of the screen to the screen list. Click on any screen in the list to change the screen image at the bottom of the panel. Please note that this screen appears on top of any other application on the PC and therefore it must be closed before accessing any other application. Click on any input to highlight that input in orange on the screen image. To view a larger image and further information about any of the screens, double click the screen name in the list.


Manual Testing

An image of the recorded screen is displayed. If an input action or element in the Contents or Errors list is highlighted, the target element is surrounded by an orange rectangle on the display. Conversely, clicking an item on the picture will also highlight that element in the Contents list. There are 3 buttons at the top left of the panel that determine how the picture is displayed.

• 100% - Displays the picture at full size • Page Width - Displays the picture at the width of the panel • Best Fit - Resizes the picture so that the whole screen is visible

within the panel The two buttons to the right of these control which mode the screen contents view operates in.

• Mouse icon – Default view whereby clicking on an element in the screen image will display relevant information about that element in all other panels.

• Outline icon – Markup mode which enables sections of the screen to be annotated and optionally flagged as being in error. See the later section for more information.


Manual Testing

The elements included on the highlighted screen are presented in list form in the Contents section. Click on an element to highlight it on the screen picture with an orange rectangle and to populate the Element Properties panel. The Element Properties pane displays the properties for the currently selected object in the Contents pane. An additional section beneath the properties panel is populated when a specific property is highlighted. This enables the full list of values to be viewed for any properties that are too large to fit on the main display. Such properties are displayed with three dots at the end to indicate that there is more information that cannot be shown. The properties that appear in bold are those that will be checked for differences on playback, should this manual set of results ever be turned into an automated script (see later section for more information). These are different for each element type and are considered the core properties for that type. Highlight an input action from the screen list to view further details about that input in the Input Properties section. The properties displayed vary depending on the type of input selected. These properties will become very important if this set of results is ever converted to an automated script. Type There are two types of input event, keyboard

input and mouse input. GUI and Web applications only, for 5250 applications the input is always via the keyboard.

Alt/Ctrl/Shift Indicates whether these keys were in an active

(True) or inactive (False) state at the time of the input. GUI and Web applications only.

Data The value of any keyboard input. Repetitions If a key is held down so that the same input is

repeated many times, the data value is recorded as a single character, for example ‘a’, and the number of repetitions indicates how many characters were actually keyed. In this example 6 repetitions would actually equate to a value of ‘aaaaaa’. GUI and Web applications only.


Manual Testing

Row The line number on the 5250 session into which the input was keyed.

Column The horizontal position on the 5250 session into

which the input was keyed. Timestamp This is used for internal purposes, for example

to calculate time delays during drag and drop operations.

Location The position in pixels of the input operation

relative to the top left corner of the target element. GUI and Web applications only.

Element Caption The label associated with the target element for

the input. For example, for a button this could be the visible text such as ‘Accept’ or ‘Cancel’, for a text box it might be the label which appears to the left of it. GUI and Web applications only.

Element Text The contents of the target element at the time of

the input. GUI and Web applications only. Element Name For elements such as combo boxes or menus for

example, this is the item that was actually selected by the input action. GUI and Web applications only.


Manual Testing

Spell Check Errors

The Errors panel lists all of the words on the screen which have failed the spell check. Click the plus icon to expand the list to show all of the instances of this word. Click on the instance to highlight its location on the screen image. Right click the word to provide the following options. Ignore Remove this word from the Errors list for all

screens within this test, but do not add it to the Dictionary. Therefore it will still be reported as an error for all subsequent tests.

Add to Dictionary Add this word to the Dictionary which is being

used by this application. All results for this test will be re-calculated and this word will no longer be reported as an error for all applications using this Dictionary.

Please note that when results are saved for Web and GUI applications, the results of the spell checking are also saved. However, this is not true of 5250 or iSeries applications and therefore spelling errors for these tests must be reviewed from within TestDrive-Assist.

Link Errors

The Errors panel lists all of the links on the screen which have failed the check. Click the plus icon to expand the list to show all of the instances of this link. Click on the instance to highlight its location on the screen image and populate the Element Properties panel with the Link Status (the reason for the failure) and the Response Time. Please note that each link is only checked once. If the same link appears on more than one screen, each will have the same status.


Manual Testing

Markups

You may wish to annotate specific areas of any of the recorded screens, for example to highlight information which is incorrect. This can either be done from the main Screen Contents panel above or by using the full screen display mode. To access the full screen mode, click on the expand symbol to the bottom right of the screen picture on the main TestDrive-Assist panel. Please be aware that this panel will always sit on top of any other applications on the PC, so to access any other application it must first be closed. Use the mouse to drag a box around the area of the screen that you wish to add a comment about and optionally flag as an error. When the mouse is released, a comments box is displayed as shown below.

Description Add some text to describe the issue. Flag As Error If this option is checked, the screen will be

marked with a red cross and a warning created in results.

Click Accept to add this markup to the screen. The markup is shown to the left of the screen and clicking on it will highlight the selected area of the screen as shown below.


Manual Testing

The following options are available from the right click menu for a markup. Edit Change the description or error flag for the

markup. Delete Remove the markup. When you close the above window and return to the main tree view, any screen which contains a markup will have its screen icon overlain with a dotted box. If any of the markups have been fagged as being in error, the box will contain a red exclamation mark. All markups are printed on the results report. Please note that this functionality is not available for 5250 results.


Manual Testing

Windows Vista

Please note that when monitoring Web or GUI applications on Windows Vista, there is a specific animation function which must be switched off to enable TestDrive-Assist to work correctly. If this option is switched on, a message is displayed as soon as the application receives the focus. The following steps can be followed to disable the option.

1. Open the Control Panel. 2. Select ‘Performance Information and Tools’. 3. Click ‘Adjust Visual Effects’ 4. Uncheck ‘Animate controls and elements inside windows’. 5. Click ‘OK’.

Toolbar Options

Once recording has begun for an application and its screens have been added to the Current tab, three toolbar buttons become available.

Save Save the results for this manual test to the

TestBench database. See later section for more information.

Clear Move these results from the Current tab to the

history tab, after a confirmation window is displayed. This occurs automatically if you switch focus from one application to another and both are in your list of applications to be monitored.

Add Immediately take a picture of the application

being monitored and add it to the results screen list. This is useful if you have updated a screen with lots of information that you wish to document.


Manual Testing

History Tab

Results can reach the History tab in one of two ways.

1. Click on the Clear toolbar option from the Current tab to move the most recent set of results to history.

2. Switch focus from the application currently being monitored to

another one which is also in your list of applications to be monitored. The set of results in the Current tab will then automatically be moved to history.

The maximum number of results that can be stored in history is determined by the setting on the Connection parameters window, the default is 10. Each set of results is stored separately and is identified by the name of the application as it was defined in the Applications list. Click on a result set to display the full set of screens with their input and screen images in the panels below. All of the functionality regarding viewing the details about each screen that was available on the Current tab is also available here. For example, double click a screen to display another window giving further details about the screen contents. Clear The Clear option on the History tab will remove

the set of results from history. These results can then no longer be recovered unless they have previously been saved. The Clear option is also available by right clicking a result header.


Manual Testing


Manual Testing

Saving Results

The results for any manual test can be saved, whether on the Current tab or moved to History. If on the History tab, the results set that you wish to save must be in focus prior to clicking on the Save button. When the Save option is selected, the following window is displayed.

Description This text is saved with the results and can be

used to describe the nature of the test or the contents of the result set.

Reference Also saved with the results, this text can be used

to hold the version number or change control reference for example.

Pass / Fail Use this option to Pass or Fail the test or section

of the results you intend to save (see following screen for more information). A blank in this field means that the test results are stored with no status.

Comments Use in conjunction with the status field above to

document the reason for passing or failing the


Manual Testing

test. Next Move to the next screen of the Save wizard as

shown below.

Use the top section of the screen to specify against which Project and Test Case the results should be saved. The properties for a Folder in TestPlan, which are obtained from the Folder right click menu, hold the default location for saving results for Tasks within it. Any Test Case specified is automatically selected but can be changed here. New Projects and Test Cases can be added here and existing ones changed or deleted by using the right click menus. See the following section for more information. Enable Database Effects For Oracle and iSeries servers where a Test

Environment has been created over the application database, it is possible to retrieve and store database effects by ticking this option. The following fields must then be populated.

Environment The name of the Test Environment which is

built over the application database. Any database updates performed here by the chosen User ID for the duration of the test will be stored


Manual Testing

with the rest of the manual test results. Data Rules Data Rules are used to define how records or

rows on a file or table should look once some activity has been performed on them during a test. Specify here which existing Data Rules should be applied to the database updates derived from this manual test. The options are All, Project only, Test Case only or None. If running Data Rules, the ODBC connection being used by TestDrive-Assist must specify the name of the TestBench library in the ‘SQL default library’ option on the ‘Server’ tab.

User ID/Computer Name When database effects are being retrieved for a

manual test, only the activity within the time frame of the test is included. In addition this option is used to ensure that only the activity performed by this test is saved, and any other activity within the application at that time is ignored. To achieve this on the iSeries the ID of the User performing the manual test must be entered, on Oracle either the User ID or the Computer Name can be used.

Click the Next button to specify which screens to save with the test results. Using these options you may wish to save a result set multiple times for different reasons or errors, perhaps selecting a different subset of screens each time.


Manual Testing

All Save all of the screen images to the results

database. Last Save only the number specified here, starting

from the final screen and moving backwards through the screen list. With this option selected you can click on a screen in the list in the Current/History tabs to automatically populate it with the relevant screen value. If database effects are also being saved, only those created within the same time span of the screens actually being saved will be included.

From Specify the range of screens that you wish to be

saved. With this option selected you can click on the screens in the list in the Current/History tabs to automatically populate the field in focus with the relevant screen number. When this option is selected, if database effects are also being saved, only those created within the same time span of the screens actually being saved will be included.

When you have finished click on the Finish button to store the results. At


Manual Testing

any time the Back button can be used to modify data on a previous screen.

Maintaining Projects and Test Cases

New Projects and Test Cases can be added and existing ones maintained or deleted using the right click menu on the second screen of the save results wizard. Right click the database name to obtain the following option. New Project Add a new Project, you will be required to enter

the Project name and description. Right click any Project to obtain the following options. New Test Case Add a new Test Case to contain manual test

results. The following screen is displayed.

Add a code and title to describe the type of results that the Test Case will contain. All other fields are only required if utilising other features that can only be set up using TestBench-PC. Please refer to this chapter in the User Guide for more information.


Manual Testing

Edit Change the description of the Project. Delete Remove the Project. Right click any Test Case to obtain the following options. Edit Change the description of the Test Case. Delete Remove the Test Case.


Manual Testing

Viewing Results The results saved from a manual test are stored in the TestBench database and can be viewed from TestDrive-Assist and from TestBench-PC. To view them from within TestDrive-Assist, click on the Results tab on the toolbar. All manual results for this User are listed, grouped by application name.

Toolbar Options Open Display the detailed results which include

Screens, Warnings, Response Times and Pass/Fail information. Please see the following section for more information.

Recent Toggle between all results for the current user

and results for this session of TestDrive-Assist only.

Refresh Update the results list following changes on


Manual Testing

another session for example. Right Click Options Right click any set of results to obtain the following options. Open Display the detailed results which include

Screens, Warnings, Response Times and Pass/Fail information. Please see the following section for more information.

Clear This option will delete some of the information

associated with the results, leaving a reduced record that the test took place. This option will permanently remove for example all screen results and response times. A confirmation screen is displayed before the clear takes place.

Delete This option will delete permanently all

references to the test. A confirmation screen is displayed before the deletion takes place.

If the Open option is selected to view detailed results, the following screens are displayed. This chapter describes only those results that might be generated when using TestDrive-Assist in standalone mode. This means that no other products such as TestBench-PC are being used to set up Environment Protection or Data Rules for example. For more information about these kinds of results, please refer to the TestBench-PC chapter.


Manual Testing

Summary

This screen contains high level information about the test and a picture of the first screen that was saved for reference purposes.

Warnings

A warning is created if any of the screens are in error. An error can be


Manual Testing

either a spelling mistake, link check failure or a markup that has been flagged as an error.

Screens

Display the detailed screen results which can also be viewed directly from the Current or History tabs in TestDrive-Assist. See the above sections for more information.


Manual Testing

Response

The performance statistics are a combination of both server and browser activity. When viewing results for browser tests the bar can be spilt into two separate sections to show transmit and build times. Response Complete time taken in seconds for the screen or URL

to appear on screen after the last navigation. This is equal to the sum of the transmit and build values.

Transmit Seconds taken since the last navigation for a response to

be received from the server. Build The time difference in seconds between a response

being received from the server and a screen or URL being completely built.


Manual Testing

Pass/Fail

Current Run Status Display either Pass, Fail or N/A (not yet

defined) to represent the relative success of the test.

Change Run Status Change the current status of the test to either

Pass, Fail or N/A. Once the status has been altered, the comments box is enabled and a comment must be entered before the status change can be updated.

Update Status Click this button once the new status and

comment have been entered in order to update the current status of the test.

Pass/Fail History Displays the details of all previous status

changes. Test Items Change the status and optionally add comments

for each Test Item defined to this test. Test Items will only be present if a TestPlan Task has been executed to begin the manual test, see later section for more information. There is no history display for Test Item status changes. There is also no requirement for the Test Items


Manual Testing

to be updated prior to updating the status of the Test Run as a whole.

Report

Title An optional user defined field which appears on

the Cover Page and at the top of each page of the report.

Company The name of the Company by whom the report

has been produced, which appears on the Cover Page and at the top of each page of the report. This is an optional field.

Printed By The name of the person who has generated the

report which appears on the Cover Page and at the top of each page of the report. This is an optional field.

Include cover page If this option is selected, a single page

containing the above three fields and the date will be printed at the beginning of the report.


Manual Testing

Click Next to display the second screen of the wizard.

Screens All Generate all information including all

screen details and response times. Screens in Error Generate all information

including screen details and response times, however only include those screens for which differences exist.

Summary Generate only the Run Summary and Run Details sections of the report.

Picture Size Choose between Small and Large pictures.

Small pictures will typically display the Actual and Expected side by side if both exist, whereas large pictures will be displayed one after the other. However this is a guideline only, the report structure is optimized according to the shape of the screen being reported upon. This may mean that although large pictures have been selected, very long and thin web pages might still be displayed side by side.


Manual Testing

Show This option determines whether the additional expected and actual screen pictures showing only the differences are included. The choices are ‘Screens only’ ‘Errors only’ or ‘Screens and Errors’. This option is not available for 5250 results.

Keystrokes For 5250 results, choose whether or not to

include the additional screen picture containing the input.

File Effects If database effects have been stored for this run,

choose which level of information to include on the report.

Data Rules If Data Rule results have been stored for this

run, choose which level of information to include on the report.

Click the Next button to complete the wizard selections and then the Finish button to begin the report generation. Please note that only the options available on your server are enabled. Once the report has been generated the following screen is displayed. Use the arrows at the bottom of the report to navigate through the report and the magnifying glass to alter the zoom level.


Manual Testing

Viewing Results from TestBench-PC

Manual results created by TestDrive-Assist appear in the results list with the prefix ‘Application:’ in the Name column, which is shown to the right of screen below. Please refer to the TestBench-PC chapter for detailed information on the results screens.

If a valid TestDrive-Gold or TestDrive-Green license exists (depending on the type of results), right clicking any manual test result will provide the option to ‘Create script from results’. This will convert the screen results into a script which can then be saved and used in the future for automated testing. Please refer to the TestDrive-Gold and TestDrive-Green chapters for more information.


Manual Testing

Test Execution from a Testing Task The previous section deals with manual tests which are launched from TestDrive-Assist. However, in its most comprehensive form a manual test can be executed from a Task in TestPlan, thus combining the script and database tracking functionality already described with test planning and defect management. The Execute option is available either from the right click menu for a Task or from the Steps tab for a Task as shown below (please refer to the TestPlan chapter for detailed information regarding the Steps panel). When the execute option is selected, the Steps for the selected Task are copied to the TestDrive-Assist panel ready to become part of the next manual test. If TestDrive-Assist is not currently active then it will be automatically launched. Please note however that the Execute option is only valid for Tasks which contain Steps. Also if another Task is executed prior to the current test being moved from the Current to the History tab, a message asks if the current results should be cleared.


Manual Testing

As well as the Test Item type and description, two additional columns are present on the above display. The Pass column provides the ability to pass or fail an individual Test Item. Therefore as the testing begins, once each test item is completed its status can be changed accordingly. The right hand column can be used at this time to add any notes which may provide further information about the testing of the individual item. Simply click in the notes field to activate an additional box into which comments can be keyed. If the Steps defined to TestPlan have more than one column, double click the column title on the above display (in this case ‘Step Description’) to display another fully expanded window containing all step columns. Close this additional window to revert to the above view. If the manual test being performed is over an application which is being monitored by TestDrive-Assist, once the Task has been executed and the Test Items have been added to the panel, focus can be placed on the application. When this occurs the display will change to include the Screens and Input as well as the Test Items as shown below. As the test progresses, the Test Items can be updated to indicate the success of the test.


Manual Testing

Once the test has been completed, the results can be saved as described in the previous section. This time the Test Items and their results will also be saved and can be viewed from the Pass/Fail tab in results. The results are also automatically stored against the Task which was executed in TestPlan and they can also be viewed from the Results tab there. If multiple sets of results are saved for this manual test then they will all be stored against the Task, providing a complete audit trail of testing


Manual Testing

activity. Clearing results which contain Test Items moves both Screen and Test Item results to History. Both can be viewed at any time for each result set by clicking on the relevant tab. If Test Items exist without any screen results, no history entry is created.

Adding Defects

Once a Task has been executed, a new toolbar button is created for raising a defect. Clicking on this button at any point during or after a test displays the following panel, which contains a subset of the functionality provided for raising a defect in TestPlan. Please refer to the TestPlan chapter of this User Guide for full details about the defect maintenance screens.

Once the defect description details have been entered, you can optionally click on the Results tab and right click to attach your manual test results. All results which have been generated for this manual test are listed.


Manual Testing

Once all defect details have been entered, click Accept to create the defect. It will automatically be added to the Task which was executed from TestPlan. However, an alternative Task, Folder or in fact Plan can be selected by clicking the Back button on the Defect wizard once, twice or three times respectively.


Manual Testing


Index 5250 Tab .................................................. 4-28, 6-21 Action Map Options...........................................5-22 Action Map Panel ................................................5-3 Action Map Playback.........................................5-31

Action Map Run Mode ................................5-20 Evaluating Branches ....................................5-15

Action Maps............................................... 2-18, 5-1 Copy .................................................... 2-18, 5-2 Delete................................................... 2-18, 5-2 Edit ..............................................................2-18 Edit/Launch ...................................................5-2 Getting Started ...............................................5-1 Launch ...........................................................5-1 New..............................................................2-13 Results ............................... 2-19, 2-63, 5-2, 5-35

Activate Test_IT .....................................4-82, 4-117 Active.................................................................5-16 Add Child Table.................................................2-80 Add Top Level Table .........................................2-80 Add/Edit Defect .................................................1-61

Allocated To ................................................1-62 Defect Description .......................................1-61 E-mail Notification ......................................1-62 E-mail Reference .........................................1-62 Priority .........................................................1-61 Reported By.................................................1-62 Status ...........................................................1-61

Add/Edit Task ....................................................1-42 Allocated To ................................................1-43 Comments....................................................1-44 Description...................................................1-42 Duration.......................................................1-43 Reference .....................................................1-44 Set as Milestone...........................................1-44 Start/End Date..............................................1-43 Status ...........................................................1-43

Admin Options............................................. 1-6, 1-8 Defect Priority ...............................................1-8 Defect status ..................................................1-8 Plans ..............................................................1-8 Resources.......................................................1-8 Task status .....................................................1-9

Advanced Tab....................................................5-26 After...................................................................1-28 AJAX ....................................................... 4-18, 6-17 Alerts .................................................................4-23 Analysis ................................................... 4-11, 6-12 Anchors..............................................................4-75 Applications.........................................................6-7 Attach.................................................................1-50 Auto Analyse .....................................................2-79 Automatically expand folders ............................1-77 Before ................................................................1-28 Block Matching........................................ 4-16, 6-15

Anchors........................................................4-75 Identity Elements .........................................4-77

Block Wizard .....................................................4-75 Blocks ............................................. 4-16, 4-75, 6-15

Errors ...........................................................4-78 Variable Data .............................................4-112

Browser Requirements.........................................4-2 Busy sense ...................................... 4-20, 6-19, 6-20 Caption.................................................................6-8

Checking.......................3-20, 3-30, 3-35, 3-43, 4-52 Checkpoint.........................................................5-11 Checkpoints .......................................................2-39

Activate........................................................2-40 Delete...........................................................2-40 Edit ..............................................................2-40 Rollback.......................................................2-40

Class Rules.........................................................4-30 Importing and Exporting..............................4-33

Clear Run Results.........................................2-50, 2-51

Clear browser cache...........................................4-25 Clear browser cookies........................................4-26 Clone Schema ...........................................2-72, 2-76 Code...................................................................5-16 Colour ................................................................3-44 Column Input .....................................................3-38 Command.............................................................6-8 Commands

Play_IT ..........................................................3-2 Component Options ...........................................5-31 Copy..........................................................1-52, 1-59 Copy Plan...........................................................1-14 Create Launch File................................ 3-6, 4-5, 5-4 Create New Plan ................................................1-31 Current State ......................................................1-25 Custom Function.......................................4-38, 4-39 Custom Queries..................................................2-85 Cut .....................................................................1-52 Data Case

Description...................................................2-73 Execute ........................................................2-73 Execution.....................................................2-88 Name............................................................2-73 Relationships ...............................................2-79 Remove Table..............................................2-82 Results .........................................................2-89 Run Description ...........................................2-88 Save .............................................................2-72

Data Cases .........................................................2-70 New .............................................................2-13

Data Protection ..................................................2-56 Scope ...........................................................2-16

Data Rules.............................. 2-17, 2-29, 2-57, 6-39 Adding .........................................................2-30 New ....................................................2-13, 2-15

Data Selections ..................................................2-84 All Possible..................................................2-83 Custom.........................................................2-83 Only Required..............................................2-83

Data Source..............1-9, 1-13, 1-21, 1-58, 4-61, 6-4 Change.........................................................2-72

Database....................................................2-11, 2-36 Database Effects ................................................6-38 DataBase effects .......................................2-16, 2-56 Date Formats

Variable data................................................2-27 DBCS...................................................................3-9 Defect

Create...........................................................6-56 Defect Chart.......................................................1-69

Chart Rotation..............................................1-70 Statistics.......................................................1-70

TestBench PC Products i The Original Software Group

Defect Pane........................................................1-59 Cut ...............................................................1-60 Delete Defect ...............................................1-59 Edit Defect...................................................1-59 New Defect ..................................................1-59 Paste.............................................................1-60

Defect Priority....................................................1-18 Delete...........................................................1-18 Edit ..............................................................1-18

Defect Status......................................................1-19 Delete...........................................................1-19 Edit ..............................................................1-19

Delete.....................1-21, 1-29, 1-52, 3-20, 4-52, 5-3 Run Results..................................................2-51

Description.........................................................5-24 DHTML ................................................... 4-19, 6-17 Diagnostics ..........................................................4-6 Dictionary ..........................................................6-22

Add To.........................................................6-31 Drag and Drop ...................................................4-50 Dynamic Input ......................................... 4-24, 4-66 Edit.....................................................................1-21 Edit Parent Table Relationship...........................2-82 Edit Parent Task.................................................1-29 Edit/View...........................................................3-19 Exceptions....................................... 3-44, 3-46, 4-83 External Links....................................................6-11 Field ...................................................................1-27 Field Properties ..................................................3-29

At Start - Field .............................................3-29 At Start - Fixed ............................................3-29 Keystrokes - Fixed.......................................3-30

File Effects.........................................................6-38 Filter........................................................... 1-23, 4-4 Filters .................................................................1-73 Find

Edit ..............................................................1-29 For ...............................................................1-24 ID ...............................................................1-24 Text..............................................................1-25

First Transaction ................................................5-24 Folder Count ......................................................1-77 Folder Pane ........................................................1-35

Chart ............................................................1-38 Copy ............................................................1-36 Cut 1-36 Defect Count................................................1-35 Delete...........................................................1-37 Drag and Drop .............................................1-38 Move Down .................................................1-38 Move Up......................................................1-37 New Folder ..................................................1-36 Paste.............................................................1-37 Properties .....................................................1-37 Rename ........................................................1-37 Report ..........................................................1-38 Task Count...................................................1-35

From...................................................................1-27 General Tab .......................................................5-22 Halt on Unmatched Input...................................3-12 Help .....................................................................5-4 Help Text .............................................................2-6 History .............................................. 1-45, 6-5, 6-35

By ..................................................... 1-46, 1-64 Date.................................................... 1-46, 1-64 Log..................................................... 1-46, 1-64 Status ................................................. 1-46, 1-64

Time....................................................1-46, 1-64 How to create a new Test Case ........................4-119 Identity Elements ...............................................4-77 If error count exceeds.........................................5-27 Ignore.................................................................6-31 Include History ..................................................1-25 Include transition search ....................................1-27 Input..........................................................4-63, 4-65 Java ...........................................................4-15, 6-14 Joblog

Results .........................................................2-59 JWalk ................................... 4-18, 4-82, 4-117, 6-16 Language............................................................6-10 Last Transaction.................................................5-24 Launch Files.. 2-12, 2-15, 2-19, 2-21, 2-42, 3-6, 4-5,

5-4 Layout Options ............................... 3-16, 4-51, 4-89 Library

Connection........................................... 2-2, 2-47 Link Check................................................6-10, 6-31

Exceptions ...................................................6-23 Locate in Explorer ...............................................2-8 Location .............................................................3-32 Loop Point ................................................4-53, 5-17 Manual Mapping................................................3-53 Manual Matching...............................................4-99 Manual testing .....................................................2-3

Results .........................................................1-37 Task execution....................................1-39, 1-48

Manual Testing .......................................... 6-1, 6-26 Getting Started...............................................6-2 Results .........................................................6-37 Task Execution ............................................6-53 TestPlan .......................................................6-53

Map Integration..................................................5-22 Map No Integration............................................5-23 Markup............................................ 4-56, 6-28, 6-32 Markups ....................................................4-56, 4-91 Match Rules ..............................................3-12, 3-57 Menu Options ......................................................1-6 Mercury Quality Center2-12, 2-15, 2-19, 2-21, 2-42,

3-6, 4-5, 5-4 Messages............................................................4-35 Microsoft Active Accessibility (MSAA) ...........4-29 Milestones..........................................................1-71

Add New......................................................1-71 Amend Milestone.........................................1-72 Delete...........................................................1-71 Edit ..............................................................1-71 Edit Task......................................................1-71

Mouse Moves............................................4-15, 6-14 Native R&P..........................................................3-3 New............................................................ 1-21, 5-3 Notes..................................................................2-93

Action Map.......................................... 2-18, 5-2 Creating .......................................................2-94 Formatting ...................................................2-95 Project..........................................................2-12 Script............................................................2-21 Test Case .....................................................2-14

Number of Runs.................................................5-26 ODBC .............................4-18, 4-20, 6-2, 6-16, 6-19 ODBC connection........................ 1-2, 2-2, 2-46, 6-4 Open.....................................................................5-3 Open Plan...........................................................1-30

Delete...........................................................1-31 Favourites ....................................................1-31

TestBench PC Products ii The Original Software Group

Open last plan ..............................................1-30 Open other plan............................................1-30 Rename ........................................................1-31

Options......................................................... 5-4, 6-9 Oracle Log .........................................................2-59 Pass/Fail................................. 2-50, 2-61, 4-92, 6-37 Paste...................................................................1-52 PC File View......................................................1-78 PC Files..............................................................1-53

Attach File ...................................................1-54 Attach URL..................................................1-54 Attached by User .........................................1-54 Computer Name...........................................1-54 File Name ....................................................1-54 Full Path.......................................................1-54 Launch File ..................................................1-54 Modified Date..............................................1-54 Remove File.................................................1-55

PDF....................................................................4-49 Plan ....................................................................1-24 Plan Authority....................................................1-13

Add to Plan ..................................................1-13 with authority...............................................1-13

Platforms..............................................................4-2 Play Control .......................................................5-17 Play Final Screen ...............................................5-18 Play_IT ................................................................3-2 Playback...............................................................5-4 Playback Script

Pause............................................. 3-5, 4-4, 4-87 Prerequisites.................................................3-61 Stop.................................................... 3-62, 4-87

Playback Wizard ................................................4-85 PowerPLAY.................................... 3-12, 3-57, 3-63 Project ................................................................5-16 Projects .................................................... 2-10, 2-12

Delete...........................................................2-12 Edit ..............................................................2-12 Maintain.......................................................6-41

Properties ...........................................................5-30 Quality Checks...................................................6-10 Record Delay .....................................................3-10 Record Wizard ...................................................4-46 Recording Script

Prerequisites.................................................3-14 Record................................................ 3-14, 4-46 Save

Performance...........................................3-14 Stop.................................................... 3-14, 4-47

Repetitions .........................................................4-65 Report ...................................................... 1-29, 6-49 Reporting ...................................... 1-65, 2-66, 4-120 Reporting Options..............................................1-65

Folder...........................................................1-65 Options ........................................................1-67 Print .............................................................1-67 Refresh.........................................................1-67 Save .............................................................1-67 View ............................................................1-66

Resource Authority......................................................1-11 Comments....................................................1-12 Edit ..............................................................1-10 E-mail Address ............................................1-12 Job Description ............................................1-11 Name............................................................1-11 Password......................................................1-12

Plans ............................................................1-12 Re-Enter Password.......................................1-12 User ID ........................................................1-11

Restore Default Layout ......................................1-34 Restore emulator focus .............................3-35, 5-32 Results 2-15, 2-49, 2-63, 3-65, 4-88, 4-120, 5-35, 6-

43 by script .......................................................2-21 Clear ...................................................2-50, 2-51 Delete...........................................................2-51 Joblog Messages ..........................................2-59 Response......................................................2-60 Screens.........................................................2-55 Server...........................................................2-58 Warnings......................................................2-52

Rollback....................................................2-40, 5-11 Run Mode ..........................................................5-22 Save .....................................................................5-3 Save Preferred Layout........................................1-34 Saving Scripts Locally .....................................4-123 Scan/Replace

Scripts ..........................................................3-49 Scheduler ............................2-19, 2-21, 3-6, 4-5, 5-5 Schema

Source ....................................... 2-73, 2-74, 2-77 Target..................................................2-73, 2-88

Screen Content Fields ...........................................................3-21 Original Layout............................................3-16 Preferred Layout ....................... 3-17, 4-52, 4-89 Screen ..........................................................3-19 Standard Layout..................................4-51, 4-89 Tracked Fields ....................................3-25, 4-70 Variable Data...............................................3-24

Screen Options Action On ....................................................3-51 Errors ...........................................................3-36 Final Cursor Position ...................................3-35 Loop Point ...................................................3-36 Play / Pause..................................................3-36 Screen Is Ended By......................................3-34 Title .............................................................3-34 Wait .............................................................3-35

Screens Delete..................................................3-50, 4-93 Insert ...................................................3-50, 4-94 Results .........................................................6-40

Script..................................................................5-16 Amending

Delete a Screen .............................3-50, 4-93 Insert a Screen ..............................3-50, 4-94 Scan/Replace .........................................3-49 Screen Replacement ..............................3-51 Script Verification .................................3-54

Constant fields .............................................3-49 Data fields....................................................3-49 Field Properties

Keystrokes - Field..................................3-31 Pause............................................. 3-5, 4-4, 4-87 Results

Signal Lights.................................3-65, 4-88 Script Delays in TestDrive-Green......................3-11 Script Options ...........................................3-41, 4-81

Activate Test_IT ..........................................3-41 Colours ........................................................3-44 Errors ...........................................................3-42 Exceptions ...................................................3-44

TestBench PC Products iii The Original Software Group

Number of Runs...........................................3-43 Use tracked Fields........................................3-43 Use Variable Data........................................3-42 Variable Data ...............................................3-45

Script Structure Properties .....................................................4-59

Script Verification.................................... 3-54, 3-57 Checkpoints ...............................................4-102 Core Fields......................................... 4-96, 4-99 Manual Mapping..........................................3-53 Manual Matching.........................................4-99 Notification........................................ 4-95, 4-97 Replace Content...........................................3-20 Screen Replacement.....................................3-51 Verify From Here ........................................3-20

Scripts ................................................................2-20 Copy ............................................................2-21 Delete...........................................................2-21 Edit/Launch .................................................2-21 Results .........................................................2-21

Search ................................................. 1-24, 2-7, 2-8 Security

Script Security ..................................3-83, 4-121 TestBench ....................................................2-10

Server User ID ...................................................5-25 Set CheckPoint/Rollback ...................................5-11 Set Preferred ................................... 3-17, 4-52, 4-89 Show all items in sub-folders.............................1-77 Show Tasks as a Timeline..................................1-76 Sidebar .................................................................2-3 Spell Check.............................................. 6-10, 6-31 SQL Builder.......................................................4-41 SQL Function........................................... 4-38, 4-40 Steps......................................................... 1-47, 6-53 System Requirements

TestBench-PC................................................2-1 TestDrive-Gold ..............................................4-2 TestDrive-Green ............................................3-2

Take Picture .........................................................4-4 Take picture on ........................................ 4-16, 6-15 Task Pane...........................................................1-39

Copy ............................................................1-40 Cut 1-40 Delete...........................................................1-39 Edit Task......................................................1-39 Execute .............................................. 1-39, 1-48 New Task.....................................................1-39 Paste.............................................................1-40

Task Status.........................................................1-20 Delete...........................................................1-20 Edit ..............................................................1-20

TCPIP .................................... 4-17, 4-20, 6-16, 6-18 TesDrive-Gold Options

Messages......................................................4-35 Test Case............................................................5-23 Test Cases ..........................................................2-14

Add ..............................................................2-13 Copy ............................................................2-14 Delete...........................................................2-14 Edit ..............................................................2-14 Maintain............................................. 2-16, 6-41

Test Environments ................. 2-17, 2-35, 2-37, 6-38 Add .................................................... 2-36, 2-38 Checkpoints .................................................2-39 Delete...........................................................2-37 Edit ..............................................................2-37 New Checkpoint ..........................................2-37

Test Items...............3-12, 3-64, 3-70, 4-8, 4-86, 6-54 Test Results........................................................1-50 Test_IT................................................ 3-8, 3-41, 4-8 TestBench Components ............................. 1-55, 5-1

Attach Component .......................................1-56 Case ID ........................................................1-56 Case Type ....................................................1-56 Launch Component......................................1-57 Name............................................................1-56 Project..........................................................1-56 Remove Component ....................................1-57

TestBench for Oracle ............... 2-3, 2-29, 2-35, 2-70 TestBench Integration......................................4-117 TestBench-PC

Menu..............................................................2-6 TestDrive-Assist ........................ 4-28, 6-1, 6-2, 6-21

Hide .............................................................6-25 Open ............................................................6-25

TestDrive-Assist Toolbar Add ..............................................................6-34 Clear ...................................................6-34, 6-35 Save .............................................................6-34

TestDrive-Gold ....................................................5-1 from TestBench-PC .......................................4-2 Introduction ...................................................4-1 New Script ...................................................2-15 Options ......................................... 4-4, 4-84, 6-9 Preferences.....................................................4-6

TestDrive-Green ..................................................5-1 from TestBench-PC .......................................3-3 Maximum errors ..........................................3-42 New Script ...................................................2-15 Options

Integrated Start ......................................3-11 Max wait................................................3-11 Test Items ..............................................3-12

Script Security .............................................3-83 TestPlan

Getting Started...............................................1-2 Connection...............................................1-2 Library Name...........................................1-2 Password..................................................1-2 User ID ....................................................1-2

Main Panel...................................................1-33 Menu Options

Chart ........................................................1-6 Exit ..........................................................1-7 File...........................................................1-6 Help .........................................................1-7 Milestones ...............................................1-7 New .........................................................1-6 Open ........................................................1-6 Properties.................................................1-6 Report ......................................................1-6

Steps ............................................................6-53 TestPlan Administrator ........................................1-4 TestPlan User.......................................................1-4 TestPlan Versions ................................................1-4 Thumbnails ........................................................3-26 Timeline....................................................2-17, 2-54 TNS Name

Source ....................................... 2-73, 2-74, 2-76 Target........................................ 2-73, 2-77, 2-88

To .....................................................................1-27 Toolbar Options ...................................................1-7 Track..................................................................3-31 Tracked Field ......................... 4-61, 4-62, 4-67, 4-68

TestBench PC Products iv The Original Software Group

tracked fields.......................... 4-55, 4-70, 4-71, 4-80 Tracked Fields.. 3-25, 3-29, 3-31, 3-43, 3-81, 4-5, 4-

70, 4-115, 5-27, 5-34 Transition State ..................................................1-26 Troubleshooting ...............................................4-122 Use Script Setting ..............................................5-23 Use Tracked Fields ............................................4-82 Use Variable Data .................................... 4-82, 5-24 User Fields ..... 1-6, 1-9, 1-22, 1-25, 1-44, 1-63, 1-73 User Reference...................................................5-24 User Tasks .........................................................1-79 Username ........................................ 2-74, 2-76, 2-77 Validation Functions..........................................4-37 Validation Rules ..4-36, 4-55, 4-70, 4-71, 4-72, 4-80

Export ..........................................................4-72 Import ..........................................................4-72 Results .........................................................4-90 Tracked Field...............................................4-72

Variable Data . 2-19, 3-20, 3-24, 3-42, 3-45, 3-49, 3-71, 4-61, 4-67, 4-68, 4-71, 4-93, 4-103, 5-27 Auto Increment ............................................2-27 Blocks ........................................................4-112 Column details .............................................2-26 Copy ............................................................2-20

Data options.................................................2-25 Data sets.......................................................2-22 Delete...........................................................2-20 Edit ..............................................................2-20 Insert rows/cols............................................2-22 Local .................................................3-71, 4-104 New .............................................................2-13 Public................................................3-71, 4-104 Row options.................................................2-23

Variable Data Source .........................................5-17 Variable Data Tab..............................................5-28 Variable Field ...........................................3-29, 3-31 Verification ........................................................4-53 Verification Checkpoints .................................4-102 Verification Options...........................................4-95 Verifying Screen ..............................................4-100 View Details ......................................................1-51 View Options .....................................................1-75 Vista..........................................................4-49, 6-34 Wakeup on ................................................4-19, 6-18 Warnings

Results .........................................................2-52 Wrap history text ...............................................1-77

TestBench PC Products v The Original Software Group

TestBench PC Products vi The Original Software Group