tmx user guide - Critical Logic

TMX U S E R G U ID E
REVISED 1/15/2015
CRITICAL LOGIC TRAINING & COMMUNICATIONS
TMX User Guide
Uncomplicated Automation
 2015 by Critical Logic, Inc.
505 Sansome St. Suite 1925
San Francisco, CA 94111
www.critical-logic.com
support@critical-logic.com
Table of Contents
1. Getting Started with TMX
3
5.
This Guide
System Requirements
Installing & Registering TMX
TMX Updates
Learning TMX
4
4
5
8
9
Sets List
Sets Editor
Sets Executable
2. TMX Tutorial
10
Guided Tour
Setting-Up the Tutorial
Logging In
TMX Work Area
The First Test
10
10
10
11
12
3. TMX Basics
26
Architecture
TMX Work Area
Adding & Managing Tests
Using Sets
Adding & Using Objects
Managing Actions
Administration
Help
26
27
28
29
30
31
31
32
4. Test Functions
33
Tests List - Adding & Editing Test Cases
Tests Editor
Right Mouse Button
Tests Narratives
Executable
33
57
71
81
83
6.
Set Functions
85
86
92
101
Objects
102
Objects Tree
Objects Usage
Objects Values
104
113
115
7.
Actions Functions
118
Actions – Tree
Actions – Usage
Actions Value
Keyword Action Components
119
129
132
135
8.
Admin Functions
Admin - Tools / Users
Admin - Properties
9.
Putting It Together
Anatomy of an Executable Script
10. Help & Troubleshooting
136
137
145
150
150
162
Help
162
Troubleshooting in TMX
164
Appendix B: Special Note on Windows Appearance
Settings
168
1
Chapter
1. Getting Started with TMX
TMX provides the most effective way to get your automated testing program
up to speed quickly, effectively and efficiently.
T
MX,
from Critical Logic, Inc. incorporates dynamic testing features that
automate changes as the software application is written and modified.
Whether you’re looking for increased efficiency and control over test
case authoring or complete automation and scripting, TMX provides
unique, proven, practical, and effective techniques for improving the software
test and evaluation process.
TMX is fully configurable, allowing business analysts and test engineers to:














Create better tests sooner using a true keyword interface;
Build test scripts from requirements in parallel with software
development;
Generate fully annotated executable scripts;
Generate UI Object Definitions directly from requirements;
Create custom business processes based objects and actions;
Enhance test maintenance through:
o Single point for maintenance of objects;
o Automatic global script updates;
o Multi-user support;
Automate script execution with batch-style process for running the tests;
Simplify risk analysis - pinpointing test library impact at the script level;
Support consistent methodology for application testing and ongoing
performance management;
Create all of your automated test scripts before application code is
complete;
Create more cost-effective and maintainable test repositories;
Eliminate the need to write customized programs for each individual test
case;
Build and integrate automated testing in the environment of “internet
speed” development required by e-commerce.
Create automated tests with non-programming resources;
No other tool creates and maintain serious automated test libraries faster and
for less.
This Guide
The TMX User Guide is offered as the primary documentation for new users as
well as experienced users of the software. It is designed to provide a quick
orientation to the initial installation and use of TMX as well as a more detailed
examination of the many features and functions of the software.
TMX is compatible with all the major automation testing tools. While TMX
contains unique features and functions for specific automation tools, the basic
interface and overall functionality remains the same regardless of the
automation testing tool used. This makes TMX extremely flexible as testing
plans or projects change for the user. This guide uses TMX configured for the
open-source automation testing tool AutoIT.
This publication offers the following elements in an effort to expand your
knowledge of TMX and provide increased functionality in your automated
testing projects:




Tips: Alternative ways to perform tasks and suggestions to increase the
flexibility and functionality of automated testing while using TMX.
Notes: Additional background information as well as descriptions of
advanced features found within TMX.
Italics: These denote specific actions and functions within TMX, such
as pushbuttons that can be selected, tabs and folders.
Blue Highlighted Text: Denotes hyperlinks to other sections within the
TMX User Guide.
System Requirements
TMX is designed to operate on any Windows-based PC, laptop or server
running Windows 2K or newer version. It will run best with at least 32 MB of
RAM and will need approximately 110 MB of disk space.
1/19/2015
Page 4
Installing & Registering TMX
The following instructions refer to the installation and registration of TMX from
the secure Critical Logic download website. Your Critical Logic representative
will have provided you with a secure URL from which to download the
installation files.
Installing from Critical Logic
To download the TMX setup package from the internet you will need an active
internet browser and access to the internet. The setup package will include
TMX, sample database (OS extension), and a sample html test application.
Save the setup package file to your computer and then run it.
You will be presented with the logon window:
Press Save to open the Windows Save window to select a temporary folder in
which to place the setup file, or select Run to start the download and
installation of TMX. After the download is complete, press Open to access the
setup.exe folder and follow the instructions as provided.
Registering TMX
After installation is complete, the first time that you log into TMX, the
Registration Logon Window will appear.
The TMX Registration process begins with the first attempt to log into TMX following
installation. If you have not used the Evaluation period, the “Start Evaluation” button will be
available. Press either the Start Evaluation or Register button to begin the process.
When the Register button is pressed, the TMX Online Registration window is
opened. You will have the option of Activating Evaluation or Registering your
production version of TMX.
1/19/2015
Page 5
The TMX Online Registration window will step you through the registration process. Note
the URL will appear after pressing the Verify Registration Code button.
To Activate Evaluation click on the Activate Evaluation button. This will provide
you with the 15 day evaluation copy of TMX. If you have already used the
evaluation period on your machine, it will not operate again and you will need
to contact Critical Logic.
To Register your copy of TMX, you will need an active internet connection and
your Account ID that was provided to you by your Critical Logic representative
to complete the registration process.
Step 1: Complete the Account ID field with the number you were
provided; complete your name, and your valid e-mail address.
Step 2: Press the Retrieve Code button. This will start your internet
browser and provide the appropriate registration code based upon your
Company ID, your copy of TMX and your workstation.
Step 3: Copy the registration code displayed on the browser into the
appropriate space in Step 3.
1/19/2015
Page 6
Step 4: Press Verify Registration Code to complete the process. If
successful, you will be returned to the TMX logon window. If not
successful, the web page displayed in Step 3 will provide information to
contact your Critical Logic representative.
Please note that the Registration Code generated in this process is unique to
your workstation – it is not transferable. You will need to perform the
registration process for each of your workstations.
Logging On
You’re now ready to log into TMX.
If you do not have an existing TMX database file to open, locate the sample
database file that is part of the TMX install. The sample database called
‘CEM_AutoIT_Sample.cem’ is located in the ‘Critical Logic’ folder under the
User\Public folder in the local directory of your workstation:
(ex. C:\Users\Public\Critical Logic).
The TMX sample database is preloaded with two User IDs by default. The first
provides the features and functions typically used by an automation tester. This
User ID does not have access to the administrative functions.
User ID: User
Password: user
The second ID is for administrator access to all functions in TMX:
User ID: Admin
Password: admin
1/19/2015
Page 7
TMX Updates
Periodically updates will be made available for the TMX products. Registered
users with current maintenance agreements will be notified of these updates
and how to obtain the current copies.
Reasons for updates may include product enhancements, new features, bug
fixes, new/revised functionality, or revisions necessary to interface with the
underlying automation tool.
To check for TMX updates, open the TMX Logon screen and click the ‘Check
for Updates’ button. A message will display stating if an update exists (or not)
and how to download. Additionally, you can always contact your Critical Logic
representative for information on the latest TMX updates.
The TMX Logon window provides a ‘Check for Updates’ button.
If a TMX update is available, it will be downloadable as a zip file. The zip file
contains the latest TMX executable file. This can be un-zipped and copied
directly into the ‘Critical Logic’ folder under your Program Files on your local
drive (or into the location in which you installed TMX originally). It’s always a
good idea to first locate the existing ‘TMX.exe’ file and rename it (to prevent
overwriting) prior to copying the new version file in case you desire to revert
back to that version. Whichever version TMX executable file is named
‘TMX.exe’ in the ‘Critical Logic’ folder is the one used when TMX is launched.
1/19/2015
Page 8
Learning TMX
A variety of resources are available to help you learn the features and functions
of TMX. Online help, this user guide, a tutorial and sample database have been
designed to help you become proficient and effective with the program as
quickly as possible. Additional resources can be found at
www.Critical-Logic.com.
Where to Start
Following installation, the quickest way to become familiar with TMX is to
review the Tutorial in Chapter 2. There you will be introduced to the tools and
functions of the application, create your first automated tests based on the
sample database, and sample some of the unique capabilities contained in
TMX.
Tutorial
The TMX Tutorial (see Chapter 2) has been designed to get you hands-on
experience with automated testing as quickly as possible. Using the sample
database included in the installation package, you will be guided through
setting up your first test cases within minutes. Using TMX next generation
features, you will experience the generation of AutoIT executable scripts
through the click of a button. No other automated test application provides such
features.
The Tutorial will also provide you with reviews of the powerful features and
functions of TMX that will allow you and your team to become more efficient
and effective.
TMX User Guide
The TMX User Guide is the printed alternative to online Help. It contains
information on key functions and features of the application as well as the
written tutorial, using the sample database, setup and installation.
For the most current information on any topic, be sure to visit
www.Critical Logic.com, the online help, or the TMX Video web page.
TMX Help
Extensive Help is available for all TMX features. Available on-line, the Help
features have been designed to provide the most current and understandable
information as quickly as possible.
TMX Support Center
Critical Logic offers on-line assistance via it’s website at
www.Critical Logic.com. These resources include the most recent version of
this guide (updated with each release of TMX), in addition to an expanding
collection of video tours that cover many of the features found in TMX.
Also included in the TMX Support Center are various white papers on various
testing subjects as well as how TMX can best be used to support your
automation requirements.
1/19/2015
Page 9
2
Chapter
2. TMX Tutorial
Guided Tour
Before starting the TMX Tutorial, take a quick Guided Tour of TMX to
familiarize yourself with the logging in, the application features, and
terminology. Follow-up with a more detailed review of the TMX work area in the
following section.
Setting-Up the Tutorial
When
installed,
TMX
creates
a
sample
database
called
‘CEM_AutoIT_Sample.cem’ located in the ‘Critical Logic’ folder under the User
folder in the local directory of your workstation (ex. C:\Users\Public\Critical
Logic). Also included is a sample web page application named testpage.htm.
The Testpage application contains several common object classes and
functions that you would typically see in a web based application.
The sample database comes preloaded with the objects contained in the
Testpage application along with the common keyword actions needed to start
creating your own tests.
As you start working with your own applications under test, you will find that
you will need to “tweak” or modify the actions contained within the sample
database. This is due to your underlying automation tool and the unique
environment of your applications under test. Your automation engineer will
know what changes are needed in order to correctly interface with your testing
environment.
Logging In
Since the TMX is a multi-user application, each user must log into the system
prior to start up. This process assures that the user is authorized for the
specific functions they are attempting, provides audit trails, and establishes
system locks necessary to prevent record conflicts.
TMX is preloaded with two User ID and Passwords that simulate both a typical
user (aka automation tester) and a TMX administrator. Those IDs are:
General User - User ID: User
Administrator - User ID: Admin
Password:
Password:
user
admin
The Admin User ID provides access to additional functionality, including user
administrative functions, test property management tools, and access to test
script executables and generation tools.
To login to TMX, click on the TMX desktop icon or select TMX from your
Windows Startup.
The TMX Logon Window will appear as follows:
Enter User ID
& Password
Current
Selected
Database
TMX Login Window



Enter in the desired User ID and Password where indicated.
Make sure that the ‘TMX_Sample.mdb’ or desired database is displayed
in the Database list. Click ‘Browse’ to locate desired database file.
Click Logon.
For advanced logon features, including database selection and registration
refer to Chapter 8.
TMX Work Area
The TMX work area has been designed to be intuitive as well as functional. If
you haven’t already launched TMX, log in now. Follow the steps outlined in the
preceding section: Logging In.
The TMX work area is divided into the following main areas:
1/19/2015

Tabs: Contain the primary function sets of TMX; these include
Tests, Sets, Objects, Actions, Admin, Help.

Folders: Under each Tab, there are folders that contain subfunctions pertaining to each tab.
Page 11

Functions: On the left side of the TMX work area are a list of
functions that relate to the Tab and Folder in which you are working.
These buttons invoke the specific action and, depending on the
function, may produce pop-up windows or messages.

Work Area: The central part of the TMX window is the work area
that displays list, scripts, or functionality depending on which Tab or
Folder you are working in.
Tabs
Folders
Function
Buttons
TMX Work Area
Current Database
(right click your
mouse on the
database name will
display the entire
path)
TMX Workspace
The First Test
Now, you’re ready to begin creating a test case in TMX. This will be a test of a
sample web page that includes entry of data into text fields, setting of a
checkbox, and validation of the Reset button functionality.
We will be using TMX, the sample database, and the sample html test page
that was included in the setup package.
1/19/2015
Page 12
1. Start your web browser and navigate to the following page:
“http://www.critical-logic.com/documents/testpage.htm”. This webpage will
be the target of our sample test. If no internet is available, open the
included ‘testpage.htm’ located in the same folder as the sample database.
Critical Logic Sample Testpage
Our test will enter data in to the Name, enter data into the Email field, turn
the New Customer checkbox on, then use the Reset Form button on the
webpage and then validate that the data entered in the two fields has been
cleared and the checkbox is no longer checked.
2. The following steps are performed in TMX. Begin by logging into TMX using
the User ID: “Admin” and Password “admin”. Make sure that the Show Test
Filter First checkbox is unchecked. Using the Database dropdown list,
select ‘TMX_Sample.mdb’ from the TMX folder (or Browse to find it).
1/19/2015
Page 13
3. Select the Tests tab from TMX; then the List folder.
Test tab - List folder view showing the current tests available. Note that this view has the filter By Folder
Test Type applied – your view may be slightly different depending on the filter used.
This view shows the current list of folders by Test Type. Your view may
vary slightly depending on the settings that were selected during the prior
session.
4. Highlight ‘By Folder Test Type’ and click the Add Test button from the
functions on the left side of the screen to begin adding a new test. This will
open the New Test window. Enter “Test 01” for your new test name and
press OK. This will save the new test case and return you to the Tests List
folder.
1/19/2015
Page 14
New Test pop-up window
Notice that your new test case has been added to the Tests List as ‘Test
01’ in the Default folder. The icon to the left of the test title shows an empty
green glass. This indicates that the test is currently empty and that there
are no steps or actions associated with that test. The other icons are
described under the Help tab.
The created test case is added to Tests List under the Default folder.
5. Next, you’ll want to create steps associated with the test case – that is,
create the actual actions that you wish the test to execute and validate.
Just to review, our test will enter data into the Name field, enter data into
the Email field, turn the New Customer checkbox on, then use the Reset
Form button on the web page and then validate that the data entered in the
2 fields has been cleared and the checkbox is no longer checked.
1/19/2015
Page 15
6. With ‘Test 01’ highlighted, click the Edit Test button on the left side of the
screen, or click on the Edit Folder. This changes your view to the Editor
folder and displays the ‘Test 01’ details.
Editing Test 01 - Notice the buttons at the left of the screen have changed to reflect the options
available for the Editor folder. Refer to Chapter 3 for a complete description of these features and
functions.
Also, note that some of the same functions found on the left hand buttons
can be accessed using the right mouse button. Often, the right mouse
button contains specialized functions that are not available in the buttons.
7. Select Add Step from the buttons. This will produce the Object Tree list for
selection. The Object Tree is a list of screens and fields that are set up
within the TMX database (Objects tab) which reflect the objects found in the
application under test.
Object Tree List available for use with Test 01. In this view, you can see three windows listed including
Testpage. This list overlays the TMX work area and greys out the underlying window.
1/19/2015
Page 16
From the Object Tree, we will be using those objects associated with the
Testpage in the Sample database. Select and expand the Testpage by
either double clicking on Testpage or pressing the “+” to the left of the
Testpage icon. Select and expand Testpage to display those objects
contained in this window.
Testpage window objects list is a reflection of the Objects tab.
8. Select the editbox Name from the displayed list by either double-clicking or
highlighting and pushing the Select Object button.
9. This will open the Step Editor window.
Test Step Editor Window. Notice the system has provided pre-defined defaults for this object.
1/19/2015
Page 17
The Step Editor provides the name of the object selected, the object type
(or class), and a list of keyword actions that can be selected from a dropdown list.
For this example, use the ‘Input’ action and put the value to be entered into
the Input Text field. For this test, enter “Bob”.
In the Note field for each step, you can add any narrative information that
will prove useful in documenting this step of your test case. The note fields
allow up to 250 characters of descriptive text or numbers.
In this example, enter in “Initial entry of data”.
Accept the default settings for all other fields for now.
The completed Step Editor for the first step should look like this.
10. Push Save to complete this step.
Notice that the Tests Editor view has been updated to show the first step in
the test case along with the narrative note.
TMX provides the option of including the narrative notes in the English
version of the test case. It’s also available within the Executable Scripts that
is generated when the test case is saved.
The first test step has been saved into ‘Test 01’.
1/19/2015
Page 18
11. Step 2 - Select Add Step to enter the next step of the test. As in the step
above, the object tree for Testpage is displayed.
This time, select the editbox Email from the Testpage objects.
One thing to keep in mind when pressing Add Step is that TMX will add the
step immediately below the currently highlighted step.
Adding a new step can also be done by clicking the right mouse button and
selecting Add Step from the menu or by using “ctrl + a”.
TMX provides three ways to add a new step to a test case. Use the Add Step menu button, select Add
Step from the right mouse button menu or use ctrl + a.
12. When the Test Step Editor window appears, enter “bobsmith@criticallogic.com” into the Input Text field. Then in the Step Notes field, double
click in the field. Notice that TMX pre-fills the notes field with the expected
value. Now push the Save button.
Step Editor for step 2.
13. Step 3 - Click Add Step to enter the next part of the test. Select the
checkbox “New Customer” from the Testpage objects available. When the
Step Editor window appears, notice that the Action has defaulted to Check
1/19/2015
Page 19
On/Off with a Status of On. By using the drop down list, you can over-ride
this option and select any of the other actions available.
TMX anticipates and suggests Actions based on the object being selected.
Since this is the desired action, we’ll leave it at the default and select Save
to add this step to the test.
14. Your test should look something like the following, with three test steps
created for inputting a value into the Name field, inputting an Email address
and setting the New Customer checkbox to “On”.
If your view doesn’t look similar to this, review the preceding steps to find
out where you may have done something different than what was
described.
You can make corrections to the test steps by double-clicking on the step or
highlighting and clicking the Edit Step button to open the Step Editor
window. If necessary, you can delete the step then insert a new step by
highlighting the step immediately above and pressing Add Step.
Test 01 with three scripted steps complete.
1/19/2015
Page 20
15. Step 4 - Now that we’ve entered some data onto the screen, we want to
test the functionality of the Reset Form button. To do that, add a new step
to Test 01. Click the Add Step button to bring up the Select Object list:
Double click on Reset Form button from the Object List (or highlight the
Object and press the Select Object button) to bring up the Test Step Editor
window.
As before, TMX will fill in an action based on the preset defaults – in this
instance the action preset is “Click”.
Object type Button defaults to the Click action.
Accept the step by clicking on the Save button.
16. Step 5 - The final phase of our test case is to verify that the use of the
Reset Form button has cleared the data entered. To do this we’ll add a
series of steps that looks at each of the field where we entered data to
verify that they are clear of data or have been re-set to their default
condition.
Add a new step to the test case and, as we did in the very first step of this
test case, select Name from the Object List to open the Step Editor.
From the Action drop down, change the action from the default “Input” to
“Verify” in order to verify that field contains the value expected (blank in this
case).
1/19/2015
Page 21
The Step Editor Action drop-down list contains several available actions for each object.
17. Once Verify has been selected, TMX adds a field in the Test Step Editor
window for entry of the Expected Value. Leaving the Expected Value blank,
will test that the field has been successfully re-set and remains without any
data.
The Step Editor Verify action for the Editbox Type.
As a reminder in the test case, add a note that clarifies what is being done
in this particular step - for example add a note “Expected Value is blank”.
Click Save to complete adding the step.
18. Step 6 - Repeat this process for the Email field. Remember to change the
action to Verify and add the Step Note.
19. Step 7 - The final step of the test case will be to verify that the New
Customer checkbox has been properly reset (i.e. off). As in the prior steps,
select the Add Step button and select New Customer from the Object List.
Instead of accepting the suggested Action, select Verify On/Off from the
Action drop down list:
1/19/2015
Page 22
Use the Action drop-down list to select from the available actions.
And choose Off for the expected status. Click the Save button to confirm
this step and complete the test case.
Your completed ‘Test 01’ should look something like this with seven test
steps. If not, review the previous section to make sure you set up each test
step correctly and make the necessary corrections by double clicking on the
step to bring up the Step Editor window.
The completed test as viewed in the Tests Editor
This simple test demonstrates several powerful features contained in TMX.
From this view, you can review the steps you created to test the sample html
web page. Notice the icons to the left of each step that indicate the type of
action being conducted in each step as well as the type of object being tested.
1/19/2015
Page 23
Steps 001 and 002 indicate a data entry action, Steps 003 and 004 are mouse
actions, and Steps 005, 006, and 007 indicate a check or verification action.
Refer to the Help tab to view other icons and their descriptions.
Clicking on the Narrative folder generates the “English” description of the test
you just created. This version describes each step, the field being acted upon,
the action being taken, and the data used.
The Narrative view displays the test case in Standard English - making it ideal for manual testing or
documentation. The Narrative can be printed or exported for use with other documents.
Clicking on the Executable folder produces the executable script that is
complete and ready to run in your automation tool with all of the appropriate
logging steps and error checking.
1/19/2015
Page 24
Executable folder displays the complete executable script for your test case. Note that yours may look
different from this since TMX generates the test script using the executable code present in the
actions/processes. This sample is using TMX which has code for AutoIT. This is automatically copied into
your Windows clipboard for use in documentation or other test tools.
The scripts are complete and executable automated code, ready to run. They
include many advanced options such as error handling, logging of each test
step, and automatic loading of the object maps.
Each test case is a complete executable script that is easily maintained by
TMX maintenance functions. We’ll explore those functions in the following
chapters.
1/19/2015
Page 25
3
Chapter
3. TMX Basics
Automated software testing can be described as a dynamic interplay of
actions, objects and scripts that have been created using specifications and
test plans.
The following chapter provides a quick overview of the various components of
TMX and how they relate to each other and the functionality of the tool. Each
tab on TMX will be explained in detail in subsequent chapters.
Architecture
The interactions of objects, actions, and scripts with the application produce
the tests that are acted upon, either manually or via your automation tool.
TMX Basic Architecture
It is this premise that forms the basis for the TMX architecture and
functionality. Taking the input from the user interface specifications and test
plans, the defined Objects and Actions determine the scripts. The scripts
combined with specified data and the object map or repository generated by
your automation tools to create the English narratives and executable
automated scripts.
TMX is designed around the three functional areas of Objects, Actions, and
Scripts:



Objects: pertain to all items contained in the application, such as
windows, fields, buttons, etc.
Actions: those things that you can do to objects such as select, input,
click, verify, etc.
Scripts: the result of the actions upon objects while in a test case.
TMX Work Area
The TMX work area has been designed to provide an intuitive framework for
test case creation and maintenance. Using conventional Windows interfaces,
most users will find navigation throughout the application to be easy and
logical.
Tabs
Folders
Function
Buttons
TMX Work Area
Current
Database (right
click mouse to
view entire path)
System
Messages
TMX Build
TMX Work Area
1/19/2015
Page 27
The primary sections of the TMX work area are divided into:





Tabs: These are the primary functions of TMX: Tests, Sets, Objects,
Actions, Admin (for those with Admin access authority), and Help;
Folders: Under each Tab, is a set of folders, defined by the Tab you
have selected, i.e. under the Tests Tab there are folders for List,
Editor, Narrative and Executable;
Functions: On the left side of the window, a series of buttons control
functionality for the current view. The functions controlled by the
buttons will change according to the Tab and Folder selected.
TMX Work Area: Depending on the Tab and Folder selected, the
Work Area provides views, lists, and secondary windows.
Status Bar: At the bottom of the TMX work area is a status bar that
displays system messages, system status, and the path of the current
test database.
The Tabs display the primary work functions of the application. Clicking on
Tests tab will display the tests contained in the current, as well as change the
available buttons to reflect those applicable to test creation and editing.
TMX displays test cases in three different ways: the Test Steps, the
Narrative, and in Executable code. The views are determined by the folder
selected. When creating the test case, select the Editor folder. Each step of
the test case is listed along with any comments.
Adding & Managing Tests
The creation and editing of test cases in TMX is performed under the Tests
tab. Using simple mouse commands and limited editing, a user can create
the test scripts that are automatically generated into executable scripts for
use in the automation tool that TMX has been coded for. In addition, TMX will
generate narrative versions of the test cases for use with manual entry or
wherever documentation is required.
Tests List
The Tests List folder provides the entry point into the test cases. Initially listed
in alphabetical order, the Tests Lists can easily be sorted and filtered to
provide quick and easy identification of target test cases. To view the filtered
test list, click on the List folder located under the Tests tab. To change the
filter view, click on the Sort/Filter button in the functions menu. A complete
description of the Sort/Filter functions is provided in following chapters.
Tests Editor
The Editor folder provides the detail of the selected test. A test is selected by
either double clicking on it from the Tests List (which opens the Editor folder
for that test), or highlighting the test with the cursor and pressing the Editor
folder.
1/19/2015
Page 28
Test Title
Test Properties
folder
Test Steps
Step description comprised
of:
 Action Icon
 Object Class Icon
 Step Number
 Action
 Object Name (in
brackets)
 Data value (in quotes)
Step note
The test Properties are a set of user-defined attributes that allow you to
assign the appropriate level of detail to your test application. This can include
as much, or as little, information to the test cases that can be used for
identification, sorting and filtering, and tracking within your defined testing
process. Only users with Admin authority level can add, delete, or modify
properties. See Chapter 8 – Admin Functions for complete details.
Using Sets
The Sets tab provides the user with the ability to batch related tests in
structured groups for test management and execution. This function also
provides a run history of the tests along with the results of the success of
each test.
Within the Sets tab you can create the groupings of test cases in specific
order for execution. This provides the opportunity to create various
permutations of your test scripts for execution depending on your needs. The
order is easily changed and modified according to your requirements.
Sets can be created that contain only tests, only sets, or a combination of
both.
The executable of a set is made up of the individual component test or set
and is combined to form a unique executable script.
1/19/2015
Page 29
Adding & Using Objects
Objects in the application being tested are maintained under the Objects tab.
Within the Objects tab, you are provided with the functionality to add, modify
and delete objects as they pertain to the application under test. The object
import and export functions allow you to keep your test cases up to date and
in sync with your application under test.
While a tester might refer to these as User Interface (UI) objects, the same is
not true from a developer’s perspective. This point needs to be made clear
when discussing this application with developers.
Objects are arranged in a hierarchical structure. At the top is the Object
Trees collection of an unlimited number of possible object trees. Typically
there would be an object tree for each application under test.
The next level hosts an actual object tree. Generally, object trees are named
after applications. For instance, let’s say that one is testing an online banking
application. Some tests require database queries to validate values added,
deleted, or modified in the database itself, since the presentation layer
doesn’t provide a way to observe these changes.
1/19/2015
Page 30
The tester would create two object trees, one for the Online Banking
application and the other for the database application.
The same test would be able to integrate one or the other object tree in
various steps as required.
There are two types of objects:

Application Objects: Those objects that are used to interact, through
Windows, with the application. They are the objects users see and act
upon when using the application. Typically, these would include the
labels, entry fields, checkboxes, pull-down lists, etc.

Common Objects: These are objects that are shared among several
screens, pages, or windows of the application. A typical example is top
navigation on a website that gets repeated page after page. Instead of
defining and re-defining these objects in each and every screen in which
they occur, they need only be defined under “Common Objects”. Any
Application Object type can be converted to a “Common Object”.
Managing Actions
Actions are those behaviors associated with classes of objects or application
behaviors. Under each Action Type is a collection of behaviors or actions that
can be performed against the object class.
It is also possible to create actions that are not associated with an object
class. These “object not required” actions may act upon multiple object types,
for example logging into an application. We refer to these types of actions as
Processes.
Within each Action there is a segment of executable script. When combined
with specific instances of objects in a test, TMX uses the actions to generate
the structured English Narrative and Executable scripts used by the
automation tool.
Administration
The Admin tab hosts all of the utilities that administer and maintain the TMX
application. This includes establishing login and access for specific users,
initiating new releases and duplication databases, database maintenance, as
well as system and user defined properties.
The Admin tab is divided into two folders:

1/19/2015
Tools/Users: various tools for creating database backups, new
databases, clearing system locks and system utilities (refer to
Admin Functions in Chapter 8). This tab is also used to establish
profile and login requirements for new users, grant or remove
Page 31
access to TMX functions, and delete users who no longer access
the application (refer to Chapter 8).

Properties: used for creating and managing window, test, system
and set properties (refer to Admin - Properties in Chapter 8).
Note: Access to the administration functions is limited to users with Admin
authority. For complete information regarding user access, refer to in Chapter
8.
Help
The Help tab contains access points for the online TMX User Guide, current
database information, TMX version information and user password changing.
1/19/2015
Page 32
4
Chapter
4. Test Functions
All operations related to the creation, editing, maintaining, organizing, printing
and exporting test cases are found under the Test Tab. The following chapter
is organized in a similar fashion to the TMX Tests tab.
Beneath the Tests tab are four main folders:




List: Relates to the organizing and creation of test cases;
Editor: Contains the details of the selected test case;
Narrative: Provides an English version of the test case;
Executable: Displays the executable test script based on
the automation tool code designed for.
When navigating to the Tests List tab, TMX changes the function buttons in
the left hand menu to relate to the function of the tab selected. Some of these
same functions are found using the right mouse button. Often, the right
mouse button contains specialized functions that are not duplicated in the
menu buttons.
Tests List - Adding & Editing Test Cases
When creating tests, by far the most frequently used functions are those of
Add Test, Copy Test and Edit Test. These options provide the opportunity to
create new test cases and maintain them through the edit functions.
Each of the buttons is described in the order they are presented in TMX.
Add Test
Creation of a new test case is a two-step process. The first step creates the
test case and adds it to the database. This is followed by the addition of the
test steps.
1/19/2015
Page 33
New test cases are added from the Tests List folder using the Add Test
button. This function creates the test case, assigns the inputted name and
adds the empty test to the Test List.
This function can be accessed by the Add Test function button, using the
right mouse button then selecting Add Test, or the accelerator keys ctrl + t.
When adding new tests, TMX checks for duplicate names. Should the same
name exist, an informational message will appear requiring you to enter a
unique name.
The newly created test will be added into the folder that was selected when
the Add Test selection was made. If no folder was highlighted, the new test
will be placed in the default folder.
Note: Test Names may not contain any special characters such as ( ‘ / \ : * ? “
< > | ) nor begin with a number.
To Add a Test
1. Go to the Tests tab and select the List folder.
2. If sorted by folders (See Sort/Filter for more information) select the folder
or sub-folder you wish to add the test to.
3. Press the Add Test button.
4. In the New Test window, enter in the name of the new test.
The New Test window allows you to create a unique test name. Note the folder in which the test will
appear is listed under the test name.
5. Press OK.
6. The new test will be added to the current database. Note the icon to the
left of the name (empty green glass) indicating the test is currently empty
of steps. As steps are added, the glass will change to half full or filled:
The new test ‘New Test 001’ added to the Default folder
1/19/2015
Page 34
Edit Test
Once the test has been added to the Tests List, editing can begin to add the
details. Double clicking on the test in the Tests List or highlighting the test
and pressing the Edit Test button opens the test edit functions.
Editing the test allows the user to add test steps, select objects that are to be
tested, review and update test properties.
The Tests Editor view displays the test properties, test steps and notes for the selected test. Double
clicking on a test property or step will open the appropriate editor.
This function can also be accessed by using the right mouse button then
selecting Edit Test, or the accelerator keys ctrl + e or double clicking on the
desired test.
Edit Recent
When working with large test databases, containing hundreds or thousands
of test cases, the Edit Recent button displays the ten most recent test cases
that were opened. This is useful when making changes and verifying the
accuracy of recent work, and eliminates the need to search through long lists
of test cases to identify the tests you were working on.
1/19/2015
Page 35
The Edit Recent button lists the 10 most recently opened tests. Clicking on the test name will
open the selected test case in the Tests Editor.
Import Tests
The Import Test function allows you to select individual or groups of tests to
import from other TMX databases. When pressed, the Import Tests button
opens the Import from Database window. Use either the dropdown list or
Browse to select the target database.
The Import Tests button opens the Import From Database window
Note that while you can select your current database, TMX will not allow you
to open it in this process.
Next, select the Connect button to open the Import Tests window. This allows
you to filter your selection by various criteria and properties. The Property
dropdown will display the folders or properties available in the selected
database. You can narrow your search by filtering by either the Property /
Folder or Test Names.
When you’ve made your selection, press the Show Test List button to display
the matching tests. Once the list has been displayed, you are offered the
opportunity to further narrow the list of tests to be imported by selecting them
using the ctrl or shift buttons.
1/19/2015
Page 36
The Import Tests window provides various methods to narrow down the list of tests to be selected for
import.
To Import Tests
1. The initial step in importing tests into the current database is to identify
the target database. This is done by either entering the complete path
and file name of the database containing the test cases to be imported, or
by using the browse icon to designate the path and file name.
2. Using the Property drop down list, identify the Property to be used as the
primary selection criteria for selecting the tests to be downloaded.
3. Select the Property Value from the dropdown list. Note that the Property
and Property Values listed are from the selected database. If you wish to
view all of the tests within the selected database, leave the Property
Value field blank.
4. The target list can be narrowed by keying in the first few letters of the test
name.
5. Using the Existing Tests radio buttons, indicate if you want TMX to Warn
if there are tests in the current database with the same name, Keep the
existing tests with the same name (ignoring the import), or Replace the
existing tests with the imported tests.
6. Pressing the Show Test List displays all tests within the selected
database that match the selected criteria.
7. The tests to be imported can be selected from the displayed list by
clicking on the desired test name. A range of names can be selected by
clicking on the first test, then holding the shift key, click on the last name
to be selected. Additional tests can be selected by holding down the ctrl
key while clicking on the target test names.
8. Once the tests have been selected press Import Tests to complete the
import.
1/19/2015
Page 37
Rename Test
The Rename Test button is used to assign a different name to a test. When
renamed, the test is placed back in the Tests List in its original position, and
not re-sorted alphabetically – this is to make finding the test easier following
the rename action.
The Rename Test window
This function can be accessed by either the button or using the right mouse
button then selecting Rename Test.
The Rename Test function also updates the test Sets to reflect the new name
of the test.
To
1.
2.
3.
4.
Rename a Test
Select the test that is to be renamed.
Press the Rename Test button.
In the Rename Test window, enter the new name of the test.
Press OK to complete the save.
Delete Test(s)
The Delete Test(s) button is used to delete an existing test case.
To Delete a Test
1. Select the test to be deleted by highlighting it from the Tests List.
2. Press the Delete Test(s) button, the Delete key or using the right mouse
button, select Delete from the displayed list.
3. Since this is a permanent change to the database, TMX prompts you to
confirm the delete action.
4. Press Yes to permanently delete the test case.
Note: There is no “undo” available for delete tests. Once you’ve
confirmed the intent to delete by pressing Yes, you cannot restore the
test case.
1/19/2015
Page 38
If the test case is flagged for test generation, the delete command will produce a confirmation
message that must be cleared prior to deleting the test case.
Generate
Selecting Generate will produce a secondary menu from which you can
select the specific action to be performed.
The sub-menu opened by clicking on the Generate button
Generate Selected Test
Selecting this option will cause TMX to updated the executable script of the
highlighted test case and copy it to the scripts directory. Only the highlighted
test will be generated.
Generate All Tests in Folder
The Generate All Tests in Folder option will update the executable script for
every test case in the currently selected folder and copy the script(s) into the
scripts directory.
1/19/2015
Page 39
Generate All Flagged Tests
The Generate All Flagged Tests option will update the executable script for
each flagged test case and copy the script(s) into the scripts directory.
Flag All
This option sets the flag for all test cases. The test cases can then be
generated using the Generate All Flagged Tests or deleted using the delete
function.
Flag None
The Flag None option turns the flags to “off” for all test cases in the database.
Toggle Flag
The Toggle Flag option sets the flag to the opposite condition of its current
state. If the flag is currently set to “on” the flag will be turned “off”.
Export Test to CSV
TMX provides the option to export the flagged test cases into a CSV format
that can then be used in external documentation or spreadsheets. Selecting
the Export Test to CSV option will create a sub-folder in the current database
and create a comma CSV formatted file containing the contents of the
selected tests.
The exported test case contains three columns: Step, Action, and Expected
Results as shown in the example below.
CEM Sync
This option is available for those installations that are using the Cause Effect
Modeling (CEM) editor application, Direct to Test (DTT). This is determined
by the database that you are using and the options as provided by Critical
Logic.
*** For more information on CE modeling options please contact your Critical
Logic representative.
1/19/2015
Page 40
Selecting the CEM Sync button will open the Synchronize Tests from CauseEffect Models window. All available CE models in the database will be
displayed in the Models tab.
The default option for syncing is to update the nodes in the test cases from
the CE model. This includes the node descriptions (English narrative of the
test step) which can be excluded from update via the displayed checkbox.
Additionally, the test case can have the default ‘Get Test Data’ first step
excluded via the displayed checkbox.
The ‘Descriptive Format’ syncing option will import the entire test from the CE
model in an English readable format that ignores certain properties in the
model that are needed to properly script and prepare for automation in TMX.
The Sync results will display in the Sync Results tab after completion
detailing the model, tests, and nodes synchronized.
The Synchronize Tests from Cause-Effect Models window
Shared Data
The Shared Data function provides a quick method of creating and using
short, stored data sets for use in tests. A complete description of creating,
using and maintaining Shared Data can be found in the next section under
Shared Data.
Sort/Filter
The Sort/Filter action in the Tests List folder allows you to change the view of
the Tests List using test properties and folders by controlling the sort
sequence of test cases and the display of folders and sub-folders.
The sorting and filtering functions can be accessed by the Sort/Filter button or
by clicking the right mouse button to display available functions. It allows you
to control the Tests List display according to the values contained in the test
case properties. Selecting the property in which the test list is to be displayed
is accomplished using the Property drop-down list.
1/19/2015
Page 41
To Sort Tests
1. Select the Sort/Filter button or use the right mouse button to generate the
options list, and then select Sort/Filter to display the Sort/Filter window.
2. The top section of the window controls the sort functions.
3. Using the drop-down list, select the specific property you wish to sort on.
The drop-down is a list of all properties associated with the tests
contained in the current database. This list may appear different than the
default properties or the selection list used when creating tests.
The Test Filter dialogue box provides several options for sorting and filtering. This setting will sort the
tests by Test Type property.
4. Using the checkboxes, indicate if Folders Only or the Sub-Folders should
be displayed.
Note: When the number of test cases in the database increases, sort
times may slow. To improve response times and make sorting more
efficient, check the Show Folders Only option. This will allow the
display of the test folders without the individual tests listed. When you
have located the appropriate folder, you can expand the folder to
display the test names.
In addition to sorting the Tests List, the view can be modified using the Filter
functions available under the Sort/Filter command.
1/19/2015
Page 42
To Filter Tests by Property
1. Select the Sort/Filter button or use the right mouse button to generate the
options list, and then select Sort/Filter.
2. The Sort/Filter window is displayed. The second section of the window
controls the filtering functions.
3. Sorting on a test property can be accomplished by selecting the property
from the drop-down list, then narrowing the view by selecting the specific
value from the Values drop down list.
In this example, the tests have been filtered to display those authored by Admin and with test names
starting with “Test”.
4. Use the second box to enter the criteria for the property you selected in
step 4. You can use the wildcard (*) to greatly expand the filter
capabilities.
5. If a second selection criterion is needed, repeat steps 4 and 5 to complete
the selection.
TMX allows filtering by exclusion of defined properties. Clicking the Excluding
checkbox will exclude those properties and values listed in the dropdown
lists.
To Filter Tests by Name
1. Select the Sort/Filter button or use the right mouse button to generate the
options list and select Sort/Filter.
2. The Sort/Filter window is displayed.
1/19/2015
Page 43
3. In the Test Name edit box, key in the name of the test you wish to filter
on. You can expand the filter by using the “*” as wildcards. For example:
to list all tests in which the name includes “Browser” enter “*browser*”.
Click Apply to filter the list names.
To exclude a name or part of a name in the filter action, click the Excluding
check box and enter the desired text in the text box.
You can combine the property filters with the test name filter to quickly narrow
your search.
Filter by Color Tag
The Sort / Filter also allows you to sort by the color tag associated with the
test cases. This feature allows you to quickly identify all of the tests that you
have flagged in your database. For instance – if you wish to identify all test
cases that are ready for execution, you could “flag” them with the color tag
“green”. Then when ready to execute, do a filter on all “green” tests. The
result is a list of all tests ready for execution.
Exit
The Exit button provides a simple way to log off TMX in order to end your
session, to log on with another user ID, or to change the database in which
you are working. Selecting the Exit button, you will be provided with the
option to login immediately with another User ID, or to end the TMX session.
TMX Exit Window allows you to immediately log back in using a different User ID.
Right Mouse Button Menu
In addition to the push buttons located down the left side of the Tests List,
there are additional functions that can be accessed only by the right mouse
button when viewing tests or folders.
There are three versions of the right mouse menu. The version you see is
determined on where the cursor is placed when the right mouse button is
pressed. These are invoked from the root level, folder level and test level.
1/19/2015
Page 44
The three different versions of the right mouse menu are determined by the cursor placement.
The versions are found (shown left to right) at the root level, the folder level and the test level.
Right Mouse – Root Level
Add Test
The Add Test function can be access by the right mouse menu or by using
ctrl + T. This will produce the Add Test window for creating the test name. For
a complete description of the function, refer to the Add Test section above.
Edit Recent
The Edit Recent function accessed from the right mouse menu opens a listing
of the ten most recently modified tests. Selecting one of the tests will open
that test case in the Tests Editor tab.
A complete review is available in the Edit Recent section above.
Paste Test
The Paste Test function is used to complete a copy of an item from the TMX
internal clipboard to the Tests List or to paste a previously “cut” test.
Whenever a test is pasted, TMX avoids duplicate test names by checking the
Tests List for identical names. If a duplicate exists (such as when a test case
is copied), TMX provides the opportunity to rename the new copy.
Tests being copied must be renamed before completing the paste.
1/19/2015
Page 45
Since a “Cut” test doesn’t exist on the Tests List, no conflict occurs, and the
test is inserted alphabetically in the Tests List.
The Paste Test function can be accessed by the button, using the right
mouse button then selecting Paste Test, or the accelerator keys ctrl + v.
The Paste Test function also allows the entire contents of a test to be copied
into another existing test.
To Paste a Test
1. After copying or cutting a test, verify that the correct test is still
available in the Clipboard by checking the bottom right hand corner of
the TMX work area. If the test is not noted there, either cut or copy the
desired test using the steps outlined above.
2. If prompted, enter the new test case name.
3. Press OK to complete the save.
Note: The pasted test case remains in the TMX Clipboard until a new Copy
Test or Cut Test command is performed. In this way, you can paste multiple
copies of the test case.
Expand All Folders
From the root level, this option will expand all folders in the Test List
structure.
Add Folder
To provide increased organization of your test cases, TMX provides the
ability to add folders and subfolders to the Tests List structure. This allows
you to group similar tests within a folder for easy identification, sorting,
filtering and access.
The folders are associated with the Test Properties and the Sort section of
the Sort/Filter function.
To view the current structure of the Tests List, activate the Filter by clicking
on the Sort/Filter button or by selecting Sort/Filter from the right mouse button
menu to open the Sort/Filter window. If you are using the Sample Database
and the default settings, activate the filter-using Sort by Property and select
Test Type from the drop down list.
1/19/2015
Page 46
Select the Sort Property using the drop-down list. Then indicate if the folders and sub-folders are to be
used in the sort process. Press Apply Now or Apply and Close to complete the sort and display the
folders.
There are two ways to create a folder: using the Add Folder button or by
creating a folder property. The method described below utilizes the Add
Folder button. The other method is detailed in the Test Property Section.
To Add a Folder
1.
Confirm the Show Folders Only and/or Show Sub-folders options are
checked in the Sort/Filter Window by clicking on the Sort/Filter button.
If they are not selected, choose a property from the drop-down list and
click one or both of the folder options and press Apply and Close. This
will provide the Tests List view using the folders associated with the
property selected in step 1.
2.
To add a folder, highlight the root level and press the Add Folder
button or use the right mouse button and select Add Folder from the
menu. This opens the Add Folder window.
1/19/2015
Page 47
3.
4.
Enter the name of the new folder in the Add Folder window and press
OK.
The new folder will be added to the list in alphabetical order.
Note: For the folder to remain – test cases must be added to the
folder by adding a new test or by dragging and dropping an existing
test into the newly created folder.
To Add a Subfolder
1. To add a sub-folder to the Tests List, the folders must be visible. If
not, follow step one in To Add a Folder.
2. Highlight the parent folder in the Tests List.
3. Press the Add Folder button or select Add Folder from the right
mouse button list.
4. Key in the name of the new sub-folder and press OK to complete
the transaction.
5. The new sub-folder will be added under the highlighted folder.
Note: For the folder to remain – test cases must be added to the
folder by adding a new test or by dragging and dropping an existing
test into the newly created folder.
The Add Folder function allows you to add in as many folders and sub-folder
levels as you wish. The view of the folders, however, is not seen when the
filter is inactive and is controlled by the Sort/Filter functions.
Export List
The Export List function allows you to produce a text document of the test
cases displayed in the Tests List view. Selecting the Export List button
generates the Export Test List window allowing you to save the generated
text file in the desired location.
To Export a Test List
1. Open the folders to display the subfolders and test cases you wish
to include in the exported list.
2. Select the Export List button or click the right mouse button and
select Export List from the displayed list.
3. TMX generates the Export Test List Window for you to enter in the
new File Name for the test list.
4. Select the folder in which you want to save the test list and enter
in the desired File Name.
5. Press Save.
To View the Exported Test List
1. Using Microsoft Word, Notepad or other text editor or viewers,
locate the Test List file in the folder where you saved it.
2. Open the file using the application commands (i.e. in Word, use
File_Open).
1/19/2015
Page 48
3. The Test List can be printed or modified using the selected text
editor.
The exported test list can be opened and modified in any text editor.
Generate
In addition to using the button, the right mouse button will provide access to
the Generate functionality. Selecting Generate from the right mouse button
menu will produce a secondary menu from which you can select the specific
action to be performed.

Generate Selected Test
Selecting this option will cause TMX to updated the executable script
of the highlighted test case and copy it to the designated script output
location (Admin/System/Property). Only the highlighted test will be
generated.

Generate All Tests in Folder
The Generate All Tests in Folder option will update the executable
script for every test case in the currently selected test folder and
copy them to the designated script output location
(Admin/System/Property).
1/19/2015
Page 49

Generate All Flagged Tests
The Generate All Flagged Tests option will update the executable
script for each flagged test case and copy them to the designated
script output location (Admin/System/Property).

Flag All
This option sets the flag for all test cases. The test cases can then be
generated using the Generate All Flagged Tests or deleted using the
delete function.

Flag None
The Flag None option turns the flags to “off” for all test cases in the
database.

Toggle Flag
The Toggle Flag option sets the flag to the opposite condition of its
current state. If the flag is currently set to “on” the flag will be turned
off.

Export Test to CSV
TMX provides the option to export the flagged test cases into a CSV
format that can then be used in external documentation or
spreadsheets. Selecting the Export Test to CSV option will create a
sub-folder in the current database and create a comma CSV
formatted file containing the contents of the selected tests.
The exported test case contains three columns: Step, Action, and
Expected Results as shown in the example below.
Generate TestIF
The Generate TestIF from the right mouse button menu will open the
Generate TXM Scripts to TestIF window. From this window you can have
TMX ouput the tests in the OMG standard TestIF format. This format makes
for easy transfer of tests into other TestIF standard accepting testing tools.
1/19/2015
Page 50
Generate TMX Scripts to TestIF window will output tests in TestIF output format for easy transfer to other
TestIF standard products
Set Property for Flagged Tests
The Set Property for Flagged Tests provides the user with the opportunity to
quickly change the assigned property of all flagged tests. This allows you to
move tests into new folders or subfolders or create new categories to place
tests and folders.
Copy Flagged Tests
Once tests (or entire folders) have been flagged, a mass copy can be
accomplished using this option. Selection of the action will open the Copy
Flagged Tests window.
Once opened, you have different options for copying existing tests. The
“Prefix” option allows you to add a prefix before all of the flagged tests. For
example, if you wish to add “Example” before all of the flagged test names,
select the Prefix radio button and type in the word “Example”. When you
press Apply, all of the flagged tests will be copied with the prefix “Example”
as in the example below.
1/19/2015
Page 51
TMX Copy Flagged Tests window
Another option is to rename specific tests by using the Replace option. This
allows you to key in the test’s original name and the copy name.
Press “Apply” to complete the copy. TMX will review the current database
and provide a warning if a duplicate name exists.
Sort/Filter
The Sort/Filter action in the Tests List folder allows you to change the view of
the Tests List using test properties and folders by controlling the sort
sequence of test cases and the display of folders and sub-folders.
For a complete review of the topic, refer to the Sort/Filter section above.
Refresh
The Refresh button provides a re-read of the current database and update
with the most current values. This is especially valuable in a multi-user
environment where several updates may be made to the database during
your session. Refresh assures that you are working with the most current
information.
This function can be accessed by the button or using the right mouse button
then selecting Refresh.
Print
The Print command allows you to print the current Tests List displayed in
the TMX work area. Select the right mouse button to display the available
commands, then selecting print, will produce the Print Window. This provides
the option to change your Printer Setup, Print the Tests List, or cancel the
command.
This function can be accessed by the button or using the right mouse button
then selecting Print Test.
1/19/2015
Page 52
Exit TMX
The Exit button provides a simple way to log off TMX in order to end your
session, to log on with another user ID, or to change the database in which
you are working. Selecting the Exit button, you will be provided with the
option to login immediately with another User ID, or to end the TMX session.
Right Mouse – Folder Level
Same as above with these unique options:
Rename Folder
The Rename Folder option allows you to change the name of an existing
folder by highlighting the folder and selecting Rename Folder from the right
mouse menu.
Changing or Renaming a Folder changes the property values for all tests contained within that folder.
Changing the folder’s name also changes that property of the tests contained
in the folder. This allows the new name to be used as sorting and filtering
criteria when managing or searching test lists.
Additional information regarding filtering and sorting can be found in the
Sort/Filter section above.
Create Set
This option provides a quick way to create an execution set of all tests within
the selected folder. Select the folder and then select Create Set from the right
mouse button. This creates a complete set of the tests within this folder in the
order shown in the folder. You can then go to the Sets tab to modify as
needed.
Toggle Flag
Flags are used to indicate which tests are available for “generation” or “regeneration” (see Generate for a complete description). When used at the
Folder level, the Toggle Flag option allows you to change the flag on all tests
contained within that folder. Using the Toggle Flag button again will change
all tests back to their previous state.
Delete Folder
The Delete Folder will remove the folder and all tests contained in it. Prior to
completing the transaction, you will be provided with a confirmation message
to prevent the inadvertent deleting of needed tests. Note that this command
cannot be un-done.
1/19/2015
Page 53
Right Mouse – Test Level
Same as above with these unique options:
Edit Test
Selecting Edit Test from the right mouse menu will open the highlighted test
in the Tests Editor tab, allowing you to add test and process steps.
A complete discussion of editing and creating tests is found below in the
Tests Editor section.
Cut Test
Test cases can be moved in position on the Tests List or incorporated into
other tests using the Cut Test button.
This function can be accessed by the button, using the right mouse button
then selecting Cut Test, or the accelerator keys ctrl + x.
To Cut a Test
1.
Highlight the test from the Tests List.
2.
Press the Cut Test button.
3.
The system copies the test to the clipboard and removes the
test from the Tests Lists.
4.
The test is now available to be pasted back into the Tests List
or pasted into another test.
Note: If a test is cut and not pasted before a second test is cut or copied, the
first test will be deleted. The name of the test currently in the Clipboard is
noted at the bottom right corner of the TMX work area.
Copy Test
Test cases are easily copied in TMX using the Copy Test button. This
function copies the test case, its properties and all associated steps in its
entirety, making fast replication of complex tests easy and accurate.
Test cases may also be added to the Tests List by copying a current test. The
Copy Test function copies the selected test to the clipboard and displays a
message at the bottom right of the work area, indicating that the test case
has been successfully copied.
1/19/2015
Page 54
Entire test cases can easily be copied by highlighting the test case to be copied then using the button,
right mouse button or by pressing "ctrl + c”.
This function can be accessed by either the button, using the right mouse
button then selecting Copy Test, or the accelerator keys ctrl + c.
Note: When pasting the test case, TMX performs a check to prevent of
duplicate test names by checking the Tests List for identical names. Since a
copied test still exists on the Tests List, a conflict occurs. The user is given an
opportunity to resolve the duplication conflict by renaming the test.
To Copy a Test
1.
2.
3.
4.
5.
6.
7.
Highlight the desired test from the Tests List.
Press the Copy Test button.
The system copies the test to the clipboard. Note the test
name is displayed at the bottom right of TMX as long as it
remains in the system clipboard.
Select Paste to complete the copy.
TMX displays the Paste Window with the original test name.
Modify the test name so that it is unique and press OK to
complete the paste into the database.
TMX inserts the new copy into the Tests List in alphabetical
order.
Notice that the copied test remains available in the system Clipboard allowing
you to make multiple copies by repeating steps 4 through 7.
Rename Test
Selecting Rename Test from the right mouse button allows you to change the
name of the selected test. An edit is performed prior to saving the change to
assure that a test with the same name does not exist in the current data
base. If a test does have the same name, a message will be displayed
advising you of the conflict.
1/19/2015
Page 55
Renaming a test does not affect the folder in which it resides. To change the
folder, you can either drag the test into the desired folder or change the test
property in Tests Editor.
Color Tag
Often, it’s necessary to flag a test case for one reason or another. The Color
Tag option in the Test List allows you to highlight the test name by selecting
one of seven colors using either the right mouse button or the ctrl + number
keys. Using ctrl + 0 removes the color tag from the test name.
Flagging tests with colors is a simple way to highlight critical tests or those that may need additional work
or modiciations.
The colors available using the ctrl key are:










Black
Blue
Grey
Green
Red
Pink
Yellow
Cyan
Magenta
None
ctrl + 1
ctrl + 2
ctrl + 3
ctrl + 4
ctrl + 5
ctrl + 6
ctrl + 7
ctrl + 8
ctrl + 9
ctrl + 0
Where Used
The Where Used command provides a listing of all test cases that either Call
or Include the selected test or where the selected test is used in Sets.
Double-clicking on one of the listed tests will open the Tests Editor for that
test case.
To return to the normal view of Tests List, click on the List tab.
Delete Test
Individual tests can be deleted by highlighting the desired test and using the
Delete Test from the right mouse button. This action cannot be reversed once
completed.
1/19/2015
Page 56
Tests Editor
The Tests Editor folder contains the detail of the tests displayed under the
Tests List folder. It is accessed by selecting the target test from the Tests List
folder, then selecting the Editor folder, or by highlighting the test and pushing
the Edit Test button, or double clicking on the selected test.
When viewed under the Editor folder, there are two primary components to a
test: Properties and Test Steps.
TMX Test Editor workspace
Test Properties contain all of the descriptive attributes for the selected test.
Five primary test attributes are initially available. These are:





Description
Author
Last Generated
Script Path
Test Type
Additional properties may be added as necessary (ex. Trace Point seen in
image above). The adding and editing of the Test Properties is explored in
Chapter 8 Admin Functions under the Admin - Properties section.
When viewing the Tests Editor folder, the function buttons change to provide
the editing options for tests.
1/19/2015
Page 57
Save
Pressing the Save button will save the test case in its current state and allow
you to continue editing the test. Upon saving the Narrative and Executable
Script is generated.
Save & Close
The Save & Close button saves the test case and closes it, returning you to
the Tests List.
Save As…
The Save As... button allows you to save the current test with a new test
name. Simply modify the test name as presented and press OK to same. This
will not replace the current test – but will change the test that you are working
in to this new test. The newly created test will be included in the current folder
you are working in.
Close
The Close button allows you to close the current test without saving the
changes that have been made. If changes have been made since the last
time the test case had been saved, a confirmation message will be displayed
to prevent inadvertently losing any changes.
Add Step
The Add Step view provides four distinct functions that provide additional
flexibility when creating a test case. These include:




Select Object
Add Window
Add Object
Cancel
Add Step – Select Object
Once a test has been established (see section To Add a Test) or you have
selected a test to edit, you can easily insert new steps. Steps may be defined
as a single action or set of actions within a test case.
To Add a Step
1. Indicate where the step will be added in the test case. This is done by
selecting the test step immediately above the spot where you want the
new step to appear.
1/19/2015
Page 58
2. Press Add Step button and TMX generates a selection window that
displays all application windows and objects available. This selection
window will be overlay the Tests Editor workspace. Select the object to
be included in the step by double clicking or highlighting the object and
pressing the Select Object button from the left menu.
3. With the Add Step window open, you also have the option of adding a
Window or Object (via left menu buttons) if they don’t yet exist in your
Object Tree via the buttons on the left menu.
4. Once an object has been selected, the step will be added to the script
and the Test Step Editor window will open. The object selected will
display in the Object field and the object type in the Type field. These are
not changeable.
1/19/2015
Page 59
Activity Settings
Name of Object
Object Class
Keyword Action
Detailed help
Data Value
Data Type
Typical Test Step Editor window. Note: the fields and appearance is
dependent upon the action and object selected.
Notes to appear
on test script
5. There are five Activity Setting checkboxes available for each action.
Select those applicable to your test:





Skip This Step: Checking “Skip this Step” will cause this particular
step to be ignored during test execution.
Generate Step Logging: Checking this option assures that the
outcome of this step test is included in the execution log.
Continue on Error: When checked, the test will continue execution
even if an error occurs in this step.
Expert Action: Checking this option will include all actions – even
those designated as Expert Actions – in the Action drop down list.
When unchecked, TMX filters the available actions for those not
checked Expert. This is especially useful when complex and/or
seldom-used actions are included in the application.
Highlight Step: When checked, displays the test step in bold font in
order to distinguish it from other steps. This is useful when there are
critical steps being tested in a long test case.
6. Select the appropriate Action for the selected object in the test step.
Action names should be designed so they indicate what they do. (ex.
Verify Exists).
7. Depending on the action selected, there may be up to seven input
arguments displayed between the Action pull down, and the Step Note
field. Complete these as required by the test. The default Data Type will
be displayed for each input argument. These can be changed, but since
this affects the generated code, it should only be done when fully
understood. When changed, it will only affect the test step being edited,
not all test steps using this object/action.
8. When appropriate, enter any comments or references in the Step Note
field. These comments will appear in the Editor view, preceded by an
asterisk, immediately below the saved step.
9. The Action Help button will open a text box that should include additional
details for the selected Action.
1/19/2015
Page 60
10. Select Save to complete the test step.
Add Process
Occasionally, test steps do not involve the testing of a specific object –
instead they are concerned with a process or a no-object action. Examples
include the starting or closing of a browser, calling or including other test
cases, using custom designed processes or invoking user defined code.
TMX provides the option of adding processes or no-object action test steps
using the Add Process button.
When selected, the Add Process button opens the Step Editor window and
provides for the selection of Process Types and specific Processes.
The Add Process button opens the Step Editor for selection of Process Types and Processes.
Under the “General” Process Type several processes are available using the
drop-down list. Among these are the processes needed to reference external
data sources, read and loop through data, as well as call_test, Include Test,
start and close browsers.
External Data
One of the more important processes available in TMX is the ability to utilize
external data sources to drive your tests. TMX can reference any CSV
formatted spreadsheet or database as an external data source. This is
typically seen as Excel spreadsheets or Access databases.
There are three concepts to consider when using an external source. The first
is to create a process that will identify and read the data source. The second
is to add steps that will get the data from that source. The final process is to
tell the script to loop through the available data.
The sample databases provided with TMX provide generic processes used to
access external data. These are the Read and Loop processes.
Experienced automation engineers may want to modify or replace these
functions with ones that are more applicable for their environment or
requirements. This is done under the Actions Tab.
1/19/2015
Page 61
Additionally, in the external functions library, specific to the automation tool
the TMX Sample database is designed for, there are ‘LoadDatasheet’ and
‘GetExternalVal’ functions that work with DTT model-generated CSV
datasheets and TMX scripting for external argument values. These too may
require some modifications for proper operation of your system and testing
environment.
For the explanation below, the generic process are used.
To Use External Data
1. In your test script, when you’ve reached the point where you want to use
external data, you need to add a “Read” Process. This is done from the
Tests Editor.
2. Select Add Process from the available buttons to open the Step Editor
window.
3. Select “general” from the Process Type dropdown list.
4. In the Process dropdown, select Read.
5. Leave the Data Type as a “Literal” value since you will be entering in the
source of your external data as a literal value.
6. Under the User CSV, enter in the path and name of your data source.
This must be a CSV formatted spreadsheet or database.
The completed step shows that we are performing a read function on a CSV datasheet.
7. Press Save to complete this step.
Next you will be adding in the steps that reference the external data
source.
In this example, we will be adding in data into a field called “Name” using
data from the spreadsheet identified in step 6 above.
8. Add a new step to input data into the desired field. In this example, we’ve
selected the Name field.
9. When the Step Editor Window opens, select the Action “Input” from the
dropdown list.
1/19/2015
Page 62
10. In the Value field we will enter the name of the column from which we will
be pulling data. In this example, the first column in the CSV spreadsheet
is named “name”.
11. Select “External” from the Data Type dropdown list.
The completed step shows that we are performing a data input into the object Name. The data value
will be taken from an external source. In this case, the column “name” in the spreadsheet defined in
the prior step.
12. Press Save to complete the step.
After adding steps for each of the data entries, the final process for using
external data is to add the “loop” statement. This
13. From the Tests Editor, select Add Process to open the Step Editor.
14. From the Process Type dropdown list, select “general”.
15. From the Process dropdown, select “Loop”. The “Loop” statement will
allow the test to continue to use the next row of data in the designated
data source until it encounters an empty row, at which time the read of
the external data source will end.
16. Press Save to complete the step.
Using Other Tests
When creating multiple tests in a complex library, it is often more efficient to
reference test cases that have already been created into new test cases. For
example, a series of test cases may be created to represent logging into the
application under test using various user permission levels. These test cases
can then be easily referenced by other test cases that test various functions
associated with the defined permission levels.
Call Test
This process imbeds a command into the test case that calls the target test
case for running during execution.
1/19/2015
Page 63
When examining the executable script you will notice that the test step for the
called test indicates that it will be run at the specified point in the test
execution.
In the example below we’ll use the same test case that we created in Chapter
2 and insert a call_test step prior to the first step. The inserted step will call a
test case entitled “Browser Testpage” before the first step.
To Add Process – Select Process ‘call_test’
1. From the Tests List, select the desired test case (in this example we’ll use
Test 01 created in Chapter 2) and double click on it to open Tests Editor.
2. Select the step immediately above where you want to insert the new step.
Since we want to insert the call_test prior to the other test steps, we’ll
highlight the line above the first step as show below.
3. Press Add Process to open the Step Editor window.
4. In the Step Editor window, select the Process Type “General” from the
drop down list:
5. Select call_test in the Process drop-down list:
6. Select the appropriate test case from the list – in this example, we’ll select
“Browser Testpage”:
1/19/2015
Page 64
After inserting the call_test step, the test case should resemble the following:
Step one now indicates that the test case Browser Testpage should run first
1/19/2015
Page 65
The call_test action places a step into the test case (indicated by the customer) which runs the designiated
test during execution. Note that this example is using generated QTP script
Add Step – Add Window
TMX allows for the creation of new windows during the building of test cases.
The process begins with adding a step into the existing test case, then
selecting Add Window. This opens the Add Object window allowing for entry
of the window name.
1/19/2015
Page 66
The Add Window button allows new windows to be created while editing test cases. Notice the object class
has been defaulted to "Window".
Add Step – Add Object
Similar to adding new windows, TMX allows new objects to be created while
editing test cases. When adding a test step, select Add Object to open the
Add Object Window. Select the Object class from the drop down-list and
complete the rest of the window.
Add Step – Cancel
To cancel adding a test step, push Cancel. This returns you to the Tests
Editor.
Add Note
Notes can be added to each line of a test case. Highlight the step in which
the note is to appear. TMX will produce an edit box in which text can be
entered into or copied from. When viewed in the Tests Editor, the notes
appear in bold green italics.
1/19/2015
Page 67
Notes can be added to specific test steps or as a stand-alone step.
Once saved, the notes will appear in the Narrative as well as the executable
scripts as a separate test step.
Edit Step
Editing test steps is a straightforward process from the Tests Editor folder.
Highlight the step to be modified and press the Edit Step button or doubleclick on the step. The Test Step Editor will be displayed showing the current
attributes and settings for the selected step.
When you have completed making the desired changes, select Save or
Cancel.
Shared Data
The Shared Data button is used where the same text strings are used in
multiple steps as arguments. This eliminates the need to retype the same
text string into each test.
This is especially effective in field length boundary testing against multiple,
different input fields. The tester can establish two Shared Data values of
specific length; for example, “30 Alpha Characters”, and “31 Alpha
Characters”. Then, using these two data sets in various tests, you avoid the
necessity of retyping 30 characters into the maximum field length tests, and
31 characters in the tests that exceed the maximum.
Up to 30,000 characters are permitted for a single shared data item.
Also, if multiple business paths lead to the same error, that error text can be
captured in Shared Data. Let’s say there are three paths that lead to the
common error. Then three tests will end with the error. Testers can simply
1/19/2015
Page 68
create a Shared Data set, then point to the same data from each test, and
avoid having to re-type the same error message three times. Additionally, if
the error message changes, the shared data can be updated and the tests
regenerated without having to identify the targeted tests and make three
separate changes.
Where list-boxes are modified by applications, the correct list-box contents
can be entered in shared data. An action can be authored to compare the list
box served by the application under test with the list stored in shared data.
Where items must appear in specific sequences, the proper list sequence can
be itemized in shared values.
To Create Shared Data
1. Select the Shared Data button or use the right mouse button and select
Shared Data. The Shared Data window will be generated.
2. Select Add to input the title of the new Shared Data set. The Add Shared
Value window will be generated. Key in the name of the new data set.
3. Press OK to save the title.
4. Enter in the shared data values. [Note that TMX counts the number of
characters entered and displays that count below the Close button.]
5. Press Save to complete the entry.
Once the shared data set has been saved, it can be modified, copied,
renamed or deleted from the Shared Data button in the Tests Editor folder.
To Modify Shared Data
1. Select the Shared Data button or use the right mouse button and select
Shared Data from the Tests Editor folder. The Shared Data window will
be generated.
2. Select the Shared Data set that you wish to modify from the pull down list.
3. Once the Shared Data set is displayed, push Modify to edit the contents.
At the top left of the Shared Data window, an indicator will appear
showing that you are in edit mode.
1/19/2015
Page 69
4. When modifications have been completed, press Save to complete the
step.
Note: The current character count for the Shared Data, including the
number of control key uses is displayed in black text in the left hand
margin. This is important when establishing test cases related to testing
the field maximum and minimum limits.
To Copy Shared Data
1. Shared Data can easily be copied for use in additional data sets by
selecting the data set to be copied using the drop down list.
2. When the Copy button is pressed, the Add Shared Value window is
displayed prompting you for a unique name to the new Shared Data set.
3. TMX will edit the name for uniqueness among the existing Shared Data
sets.
4. Press OK to save the copy under the new name.
5. TMX returns you to the edit mode to modify the copied data.
6. When finished, press Save to complete the copy.
To Rename Shared Data
1. From the Shared Data window, select the Shared Data set to be renamed
from the drop-down list.
2. Push the Rename button.
3. Enter the new name for the Shared Data set and press OK to save.
To Delete Shared Data
1. From the Shared Data window, select the dataset to be deleted from the
drop-down list of names.
2. Highlight the selected name and press the Delete button.
3. TMX will prompt you for a confirmation of the delete.
4. Press Yes to complete the delete or No to cancel and return to the
Shared Data window.
Once the shared data has been created and saved it can be used in various
test cases where data input is used. This is done in the Test Editor while
adding or editing the individual test steps.
To Use Shared Data
1. When editing a test case in Tests Editor, select the specific test step that
is to use the shared data.
2. In the Test Step Editor select Shared from the Data Type drop-down list.
3. In the Value drop-down, select the appropriate shared data.
4. Press Save to confirm the changes and return to the Test Editor.
Note: Once the test step has been changed to point to the Shared Data,
it will use that data set for the future executions of the test. Should the
Shared Data set be modified, the test case will use the modified data.
1/19/2015
Page 70
Generate Test
Selecting the Generate Test button while editing or viewing a test script will
refresh the current view, refresh the narrative of that test and re-generate the
executable scripts. This allows you to quickly update all aspects of the current
test without having to leave that test script.
Exit TMX
The Exit TMX button allows you to leave TMX from the Script folder, without
having to return to the main menu or window. Prior to leaving the application,
TMX allows you to sign back into TMX under a different User Id or to select a
different database.
Right Mouse Button
As with the other tabs and folders, the right mouse button contains some
unique functions when used in the Tests Editor. Note that the functions are
different depending on where in the Tests Editor the mouse is placed.
Right Mouse Button – Test Level
Save
The Save function is the same as hitting the Save button on the left side of
TMX. This will save all changes made to the test to the database and keep
the current test in the Editor.
Save & Close
The Save & Close function, saves all changes made to the current test to the
database and closes the test returning you to the Tests List.
1/19/2015
Page 71
Save As….
The Save As… function will save the current changes under the name your
choose in the New Test window. This will not make changes to original test.
Close
The Close function will close the test currently opened in the Tests Editor and
return to the Tests List. If changes have been made a window will open
prompting you to either save the chances or just close the test.
Shared Data
The Shared Data function will open Shared Data window, similar to using the
Shared Data push button described above.
Display Stickynote
The Stickynote is unique to the test properties. This function available from
the right mouse menu or from pressing ctrl + d displays the entire property
value in a temporary “stickynote” window.
This is particularly useful when the Test Description or other user defined
property is extensive. You can use the Stickynote to display the entire
description while editing the test case. This provides the user with a quick
reference to details that would otherwise not be visible.
The "Stickynote" contains the complete contents of the select property and remains visible while editing
test cases. Double-clicking on the note closes the view.
The Stickynote can be re-sized and positioned anywhere in the TMX
workspace thereby allowing it to remain visible during all phases of the test
case editing. This becomes extremely valuable when the user needs to
reference long descriptions or narratives that are contained within the user
defined properties.
1/19/2015
Page 72
The note is easily re-sized by stretching the lower right hand corner.
Reposition the note by clicking on the note and holding down the left mouse
button while moving to the desired position.
To close the Stickynote double-click within the space of the note.
Format
The Format function allows the user to change the look of the Tests Editor in
terms of the icons displayed next to the test steps, the arguments displayed,
and whether the Step Notes are displayed as a separate line.
Color Tag
The Color Tag function provides for the “flagging” of the test names with
different colors. This provides for a quick temporary designation of the tests
for later identification and sorting or filtering.
Generate Test
The Generate Test function is similar to those provided by the left button. For
a complete description, see the Generate Test section above.
Print
The Print function provides the same function as the button described above.
Exit TMX
This function exits the user from TMX.
Right Mouse Button – Properties Folder Level
The only difference at the Properties Folder Level for the Right Mouse menu
is the addition of the Reset Properties function.
1/19/2015
Page 73
Reset Properties
This function resets all properties for the selected test to the current saved
values and will not save any changes that have been made to this test
following the last “save”.
Right Mouse Menu – Properties Level
When at the individual property level, two new functions are available: Set
Property and Clear Property.
1/19/2015
Page 74
Set Property
Property values can be selected by highlighting the property and either
double clicking or using the right mouse button and selecting Set Property
from the menu.
This will produce the Property Value Editor window displaying the current
value. Depending on the property selected, select the desired value from the
drop-down list or enter in the correct value.
Clear Property
Property values can be removed from the selected field by selecting Clear
Property from the right mouse button.
Right Mouse Menu – Test Steps Level
The Tests Step Level provides four unique options to the right mouse button:
1/19/2015
Page 75
Add Step
The Add Step is the same function as the button. It will insert a new step into
the first position in the test case, or line 001.
Add Process
This adds a process to the first step position, step 001.
Add Note
Similar to the Add Step and Add Process, this function will add a note to the
first position in the test.
Shared Data
This function opens the Shared Data functionality as described above.
Right Mouse Menu - Test Steps
1/19/2015
Page 76
Cut Steps
Test steps can be cut from the test case by highlighting the step or multiple
steps and selecting Cut Step from the right mouse menu or by using ctrl + x.
This will remove the step(s) and place it in the clipboard where it will remain
until pasted or copied over.
To select multiple consecutive steps, highlight the first step to be selected,
then while holding down the shift key, select the last step to be selected by
clicking on it with the mouse. Then using press ctrl + x to cut the selected
steps.
To select multiple non-consecutive steps, select the first step, then while
holding down the ctrl key, select the other steps to be cut.
If multiple steps have been selected, a confirmation message will be
displayed indicating how many steps are to be cut. Press Yes to complete
cutting the steps or No to cancel the transaction.
The steps are saved to the clipboard as shown in the lower right hand corner
of TMX until they have been used or copied over.
1/19/2015
Page 77
Copy Steps
To copy a step, highlight the step by clicking on it. Then select Copy Step
from the right mouse button or use ctrl + c.
Multiple steps can be copied using the selection method described above.
Complete the copy by using the Paste Steps command described below.
Paste Steps
Test steps that have been cut or copied can be pasted into the current test
case or a different test by using the Paste Steps command.
To complete the copy or paste steps that have been cut from a test case,
navigate to the desired test case and highlight the step immediately prior to
where the cut or copied test steps are to be placed. Then using either the
right mouse button, select Paste Steps from the menu list, or use ctrl + v to
complete the paste.
Notice that the steps remain in the clipboard. This allows you to paste the
same tests into multiple test cases if desired.
Delete Steps
Deleting a step in a test case is similar to the Cut command – the difference
being that the deleted step is not retained in the clipboard for future use.
To delete a step, highlight the step or steps using the method described
under Cut Steps above. Then use either the right mouse button and select
Delete Step or press the Delete key to complete the function.
Find
Find opens a Find Step window that allows for various ways of searching
through all scripted test steps in TMX.
Highlight
TMX provides the user with the opportunity to highlight important steps within
the test case using the right mouse button. Select the step to be highlighted
and then press the right mouse button and select Highlight.
1/19/2015
Page 78
This same feature can be accomplished using the ctrl +h.
Multiple steps can be highlighted by using pressing ctrl + h after selection.
The highlighted steps will remain highlighted in the Tests Editor as well as the
Narrative.
Highlighting steps allows you to call attention to important or critical steps within the Narrative.
Steps can be “un-highlighted” and returned to a normal state by selecting the
steps and repeating the highlight command.
Skip Step
TMX provides the ability to temporarily flag test steps that are to be skipped
during execution. This allows the user to temporarily remove the step but not
permanently delete it.
Test steps that are to be skipped during execution are displayed with a line through the step.
This is useful for test cases that contain references to functionality that is not
yet available – or temporarily unavailable – in the application under test.
To skip a step, highlight the step or steps then use the right mouse button
and select Skip Step – or use ctrl + k.
To “un-skip” a step, highlight the step and repeat the command.
1/19/2015
Page 79
Show Object
While editing a test case, the Object involved in the selected test step can be
quickly displayed using the Show Object command.
Highlight the step, then using either the right mouse button, select Show
Object from the menu or press ctrl + w to display the object.
TMX will display the Object associated with the selected step.
To close this view, select the Close Objects button, use the right mouse
button and press Close Objects, or click on the test tests.
Show Action Definition
Similar to displaying the object information, you can easily view the action
definitions associated with test steps by using the Show Action Definition
command.
Select the test step, then press the right mouse button to display the available
options. Select Show Action Definition from the menu. The same command
can be selected using ctrl + q.
While no editing of the action is allowed from this view, it is often a useful
feature when editing a complex test case.
1/19/2015
Page 80
The Show Action Definition function allows the user to view the details associated with the actions for the
selected test step.
To return to the Tests Editor, select the Cancel button.
Tests Narratives
The Narrative folder found under the Tests tab provides an English version of
the test that has been created under the Tests Editor. Narratives are used to
verify that the scripts are clear and legible and assist test authors in verifying
that the appropriate steps have been created and that the test case is
complete.
1/19/2015
Page 81
The Tests Narrative is also used to display and/or print test cases for manual execution as well as general
documentation. Note that Step1 has been skipped. This is shown by a line through the skipped step(s).
Narratives are re-generated along with the executable script whenever the
Generate Tests function is called.
There are four buttons available from the Tests Narrative folder.
Export
The Export function allows the user to export the test case narrative report to
a file as rich text. When pressed, the Export Narrative to file window opens
allowing you to designate the folder in which the narrative should be stored in
addition to editing the name of the file.
Export CSV
Similar to the Export function, the Export CSB provides the opportunity to
save the narrative as a csv file in the desired folder or location. Pressing the
button will open the Export widow, allowing you to change the folder and
name.
Print
Pressing the Print button will print the Test Narrative on the default printer.
Exit
This function exits the user from TMX.
1/19/2015
Page 82
Executable
The Executable folder under the Tests tab provides a view of the complete
executable script. There are no modifications or changes that can be made to
the executable script from the Executable folder. All changes to the test steps
are made through the Tests Editor folder.
Examination of the Tests List Executable reveals the structure and nature of the TMX generated test
script.
The executable script is built from several different areas within the TMX
system – primarily the Actions and Objects tabs with the Notes provided via
the Tests Editor. For a detailed review of how the executable is generated,
refer to Chapter 9 in this guide.
1/19/2015
Page 83
As a default, the executable does not display where the source is generated
from. This can be changed under the System Properties “Show Code
Source”. Chapter 8 explains how to turn this property on and off.
There are two functions available on the Executable folder.
Copy Code
This potion copies the entire Executable into the system clipboard.
Exit TMX
This function exits the user from TMX.
1/19/2015
Page 84
5
Chapter
5. Set Functions
The Sets functions provide batching and ordering functions within TMX. This
allows you to specify what tests should run in which order, as well as the
ability to group tests into ordered batches or sets for automated execution.
The Set function provides the ability to build test functions from one test to
the next and determines the execution order of executable scripts within
TestPartner.
The Sets tab has three sub-folders associated with it: List, Editor and
Executable. The most commonly used functions are those of Add Set and
Edit Set followed by Filter and Batch functions.
1/19/2015
Page 85
Sets List
The Sets List provides all of the basic functions for adding, managing, and
ordering sets of test cases. This is accomplished using the various buttons
available on the left hand side of the window as well as using the right mouse
button.
Similar to Tests Lists, the Sets List can be sorted and filtered as required.
As with the other views available in TMX, there are various commands
available using the buttons on the left hand column as well as the rightmouse button menu.
The Sets List with the options displayed.
Add Set
Similar to creating a new test case, the creation of a new set is a two-step
process: creating the set name and then adding set steps.
Adding a set can be accessed by either the Add Set button or by using the
right mouse button, then selecting Add Set, while in the Sets List sub-tab.
To Add a Set
1. Go to the Sets Tab and select the List folder.
2. Highlight the set immediately above the point where you want the new
set to appear.
3. Press the Add Set button. TMX produces the New Set window. Note that
the new set will be added in alphabetical order.
1/19/2015
Page 86
4. Enter in the unique name of the new Set.
5. The new set will be added to the list.
Edit Set
Editing sets is very similar to how test cases are edited. First select the set to
be edited and either double click on the set name or push the Edit Set button
to open the Sets Editor view.
The Sets Editor with the properties displayed.
To Edit a Set
1. From the Sets List highlight the set to be edited.
2. The Sets Editor window can be opened in three ways:
 Click on the Edit Set button
 Double-click on the set to be edited
 With the set highlighted click on the Editor folder.
3. The Sets Editor window will open.
Copy Set
The Copy Set function allows you to copy a complete set. The copy will
include all of the test cases contained in the original. Once copied, you can
use the Sets Editor to add or delete individual test cases.
1/19/2015
Page 87
To Copy a Set:
1. From the Sets List folder highlight the test set you wish to copy.
2. Using the right mouse button, select Copy Set or push the Copy Set
button on the left hand side of the work area.
3. TMX will produce the New Set window with the copied set’s name
appearing.
4. Enter in a unique set name for the new set. TMX will check to make sure
there are no duplicates.
5. Press OK to save the new set.
Delete Set
Deletion of a test set can be made using the buttons, right mouse button or
the delete key.
To Delete a Set
1. From the Sets List folder highlight the set to be deleted.
2. Using the button, right mouse button select Delete Set, or press the
Delete key.
3. TMX will prompt you to confirm the deletion.
4. Press Yes to complete the delete transaction or No to cancel.
Note: There is no “undo” available for delete actions. Once you’ve
confirmed the intent to delete by pressing Yes, you cannot restore the set.
Import Set
Sets contained in a different database can be imported into the current
database similar to the Import function in the Tests List.
Click on the Import Sets button to open the Import from Database window.
From here, you can select the test library from which you want to import the
sets. If the database is not included in the dropdown list, press the Browse
button to select the appropriate folder. Note that TMX will not let you import
from the database in which you are logged into.
When the database has been selected, the Import Sets window will open
allowing you to search for the desired sets using the Sets Property or Name
filters.
1/19/2015
Page 88
The Import Sets window.
Once you’ve made your selection, press Show Set List to display a list of
Sets available for import.
To Import a Set
1. Press the Import Sets button on the left side of the Sets List view.
2. Select the target database from the dropdown list. If the database is not
listed use the Browse command to locate the appropriate database.
3. Once selected press “Connect” to open the Import window.
4. The Import Sets window allows you to narrow the list of available sets by
filtering your list on the basis of Sets Properties or the Set Name. When
the criteria has been specified, click Show List to display the available
Sets.
5. From the displayed list, highlight the Sets you wish to import or use the
Select All button to highlight all Sets.
6. When you have highlighted the Sets for importing, use the radio buttons
to determine what is to be done if there is a Set by the same name in your
current database. The options are to “Warn” you of any conflicts, “Keep”
the Sets from the current database, or “Replace” those with the Sets in
the selected database.
7. Press Import Sets to complete the import.
Rename Set
Renaming a set is accomplished by highlighting the target set and using the
button or right mouse button. The New Set window is displayed which allows
you to enter in the new name of the set. Press OK to confirm the change.
TMX will edit against existing sets to assure duplicates are not created.
1/19/2015
Page 89
TD Export
Upcoming TMX enhancement.
Generate Set
Pressing the Generate Set button will generate and update those test sets
not yet created in TMX. You will be prompted by a warning message
indicating which sets will be generated and requesting confirmation of the
action. Pressing Yes completes the generation.
Batch Sets
The Batch Sets button provides several options for flagging tests cases and
generating the executable scripts within TMX. Pressing the Batch Sets button
provides four options: Flag All, Flag None, Toggle Flag and Generate
Flagged Sets.
1. Flag All sets the flag on all test sets to On
2. Flag None sets the flag on all test sets to Off
3. Toggle Flag will change the current setting of the selected test to either
on or off depending on the initial setting
4. Generate Flagged Sets will complete generation of the narrative and
executable on all positively flagged sets and re-set the flag to off
Sort/Filter
Similar to the functions found under Tests List, the Set List can be sorted and
filters to suit your current project. This is done under the Sort/Filter button.
When selected the Sort/Filter window opens allowing you to sort or filter the
Set List view using the Object Folder Properties.
Export
TMX allows you to export the narrative descriptions of selected sets into a
rich text document (.rft format) for printing or importation into other
documentation or reports.
To Export a Set
1. From the Sets List folder highlight the set to be exported.
2. Select the Export button, right mouse button and select Delete Set, or
press the Delete key.
3. TMX will prompt you to confirm the deletion.
4. Press Yes to complete the delete transaction or No to cancel.
Print
The Print button allows you to print the Sets List as displayed. This provides
a hardcopy of the filtered or unfiltered list.
Printing is routed to the default printer.
Exit
The Exit button allows you to quit TMX entirely or to log off the current user or
database and immediately re-log back into the application.
1/19/2015
Page 90
Right Mouse Menu
As with the other functions throughout TMX, the right mouse menu provides
some additional functionality depending on where in the Sets List you are.
The unique functionality (different from the left buttons) is described below.
Toggle Flag
The Toggle Flag option when pressed at the root level will flag all sets for
generation. If the cursor is at the individual Set level, then it will flag only that
set.
Refresh
Periodically while working in Sets, the Executable may lag behind the work
you are doing within the Sets tab. This is automatically updated once you
navigate to the Executable tab or press the Refresh button.
The Refresh button provides a re-read of the current database and update
with the most current values. This is especially valuable in a multi-user
environment where several updates may be made to the database during
your session. Refresh assures that you are working with the most current
information.
This function can be accessed by the button or using the right mouse button
then selecting Refresh.
1/19/2015
Page 91
Sets Editor
The Sets Editor provides the functions related to adding, deleting and
ordering specific tests within the Set. Through a combination of buttons, right
mouse buttons and keyboard commands, you can manage aspects of
batching and controlling the execution order within the execution engines.
The Sets Editor view is laid out similarly to the Tests Editor view.
The top portion of the view contains the set property information. This can be
expanded or collapsed by clicking on the Properties folder.
The Sets Editor with the properties displayed.
Each Set contains four default properties. Additional properties can be added
via the Admin functions discussed in the Add Property section in Chapter 8.
The Set Properties provide high-level information regarding the creation and
maintenance of the set. These attributes are available for use in
documentation (via hardcopy printouts or exports).
There are no button functions specific to the Property section of the Sets
Editor – however, there are a number of functions that can be accessed by
the right mouse button. These functions will be explained below.
Below the Set Properties are the Set Items. This is presented in the order in
which they will be executed. Set Items may be individual tests or other sets
1/19/2015
Page 92
within the current database. Note that TMX will not allow you to add a Set to
itself.
Each Set Item is accompanied by two icons to the left of the Set Item
number. The first Icon indicates whether the Set Item is a Test or a Set. The
image of a document with a check mark denotes a Test. An image of a
document in brackets denotes a Set.
The second item indicates wither the Set Item will continue on error or not.
The down arrows denote the Set will continue to run even if a non-fatal error
occurs during the execution of that Set Item.
An inverted “T” denotes that the Set will stop execution at that item if an error
occurs within that Set Item.
Save
Following the creation or editing of a set, use either the Save button or select
Save from the right mouse button to complete the transaction and preserve
any changes that have been made.
Save As…
TMX provides the ability to save the current Set with a different name or path
using the Save As function.
Close
The Close function allows you to exit a modified set without saving the
changes.
Add Test Item
Once a set has been created, individual tests can be added to the set using
the Add Test Item button or via the right mouse button. Selecting the Add
Test Item produces the
Tests are added in the order in which they are selected.
To Add Test Item
1. From the Sets Editor, select either the Add Test Item button, the right
mouse button, or ‘ctrl’ + a.
2. TMX will produce the Add Test selection list, which displays all of the
available test scripts on the right hand portion of the window.
3. Highlight the test script to be added to the set and press Select Test – or
– double click on the desired test.
4. The selected test will be added to the set immediately following the test
script that was highlighted in the set list.
5. The available test list remains active allowing you to continue adding
additional tests without returning to the List or Editor.
6. When finished adding tests, select Cancel to return to the Sets Editor or
click in the Sets portion of the work area.
1/19/2015
Page 93
The Test Selection window displays all tests available in the current database.
Selecting Add Test Item from the Sets Editor temporarily changes the view of
the Sets Editor folder and provides a unique set of functions until the Cancel
button is pressed.
Add Test Item – Select Test
The Select Test view under the Add Test Item provides a list of all tests
available in the current database for selection into the current Set. Double
clicking on the test will add it to the Set in the order selected.
Add Test Item – Select Flagged
Using the Select Flagged option will add any test that has been flagged in
previous activities into the current set. You can also flag tests by highlighting
the desired test within the list and pressing the space bar.
Add Test Item – Add Test
While in the Sets Editor additional functions are made available when adding
tests to sets. The Select Test button allows you to continue selecting and
adding tests to the current set. In addition, the Add Test button allows you to
add a new test case to the available tests without leaving the Sets Editor and
the set building process.
Selecting the Add Test button allows you to create a new test folder and to
include it in the set being built. Note that the newly created test script is
empty. This test script cannot be completed while in Sets Editor. Instead,
when you have finished creating the set, return to Tests List to select the
newly created test and complete the steps as described in section Edit Test
in Chapter 4.
1/19/2015
Page 94
Add Test Item – Sort/Filter Tests
The Sort/Filter option is also available while creating sets. This allows you to
quickly identify the desired tests without leaving the set building process. This
is especially useful when dealing with large test libraries. All of the standard
filter options are available while in Sets Editor. For a complete description on
filtering, refer to section Sort/Filter Tests in Chapter 4.
Add Test Item – Cancel
When you have completed adding all of the targeted tests to the set, select
the Cancel button to return to the Sets Editor view.
This function can also be called by clicking in the white area of the Sets
Editor. The Tests List will close returning you to the Sets Editor.
Add Set Item
In addition to Test Items, sets may also contain other sets. This simplifies
creation of complex sets that use repeated patterns of test cases. For
instance, one set may be created for logging into your application, which is
comprised of several tests. This could then be used for several sets that
involve logging into the application then selecting functions from the initial
menu. Rather than creating the logging on tests from scratch, create one test
set for the log in process then embed that set into the subsequent sets testing
the initial menu selections.
To Add a Set Item
1. From the Sets Editor folder, highlight the test immediately preceding the
location where the embedded set is to appear.
2. Use either the Add Set Item or right mouse button to add the new set.
3. TMX will produce the Set Selection list from which you can choose the
appropriate set.
4. Highlight the target set and push the Select Set button – or – double click
on the desired set to add it to the Set being constructed.
5. If additional sets are required they can be added now.
6. When finished click in the work area or select the Cancel button to
complete adding sets.
Note: Only one level of sets may be embedded into a Set. Nested
embeds are not permitted.
Add Note Item
The Note function in Sets allows extensive comments within a set such as to
describe the data used in the set or to explain how to verify some testing
result manually after the set has run. It may be used to keep notes about the
set as it being constructed or notes about skipped items that are working
around bug in the application under test until they are fixed.
1/19/2015
Page 95
Delete Item
Tests or sets can easily be removed from sets using the Sets Editor Delete
functions. This permanently removes the test or step and is not reversible.
Should you remove a test or step in error, you will have to go through the Add
Test Item or Add Set Item steps outlined above.
To Delete an Item
1. Select the appropriate Set using the Sets List to invoke the Sets Editor.
2. Highlight the test or embedded set to be deleted.
3. Press the delete key, the Delete Item button or the right mouse button.
4. TMX will produce a confirmation message to verify that you want the
delete to proceed.
5. Press OK to complete the deletion.
Item Detail
While in the Sets Editor, you can easily view the detail of any embedded test
or set by highlighting that item and selecting the Item Detail button, using the
right mouse button and selecting Item Detail from the available functions, or
by double clicking on the step.
When selected on a test the Item Detail provides a detailed list of the test
steps and notes, similar to the Tests Narrative view.
The Item Detail view displays the Test Narrative for the selected test. The window can be re-sized or
moved to a convenient place on the desktop.
When selected for a set, a list of the included tests is produced on the right
hand side of the work area.
1/19/2015
Page 96
Skip Item
In some instances, tests or sets within a set should not be tested. This may
be due to know defects within the application area that the test or sub-set is
testing, or where the functionality has not been moved into the test
environment. To avoid encountering those conditions, a test or sub-set may
be noted within the set to be skipped during the execution rather than
creating a copy of the set without the specified tests.
To Skip Test Item
1. In the Sets Editor, highlight the test or set to be skipped during execution.
2. Press the Skip Item button or right mouse button.
3. TMX will strike thru the test or set, indicating that it will be skipped during
execution.
4. To “un-skip” the step and include it back into the active set, highlight the
step and press the Skip Item again.
On Error
The On Error button allows you to designate what should happen if an error is
detected during execution of the test or set. Normally, the test execution is
suspended should an error occur during executions in TestPartner.
The On Error indicator is immediately to the left of the step number. In this example, Set Items
004 and 007 will stop the Set from running if they contain an error.
The On Error indicator in the form of a downward pointing arrow indicates the
step will proceed should an error occur during execution. The inverted “T”
indicates the execution will stop at this point should an error occur during
execution of the step.
Move Up
The order in which the tests and embedded sets appear in the Set Editor
determine the execution order in TestPartner. When adding tests and sets,
you can control the execution order by the sequence in which they are added
to the set. Should you make an error in the selection, you can still manipulate
the order by using the Move Up and Move Down buttons.
1/19/2015
Page 97
To Move Set Item Up
1. In the Sets Editor, highlight the test or set that is to be moved up in
execution order.
2. Press the Move Up button (or use the right mouse button) to move the
step up in the order.
3. Repeat the process for each position the step should move.
Note: only one test or embedded set can be moved at a time. Multi select
move is not permitted.
Move Down
In addition to moving the highlighted step up, you can re-position the step
down in the execution order by using the Move Down button or the right
mouse button.
Export
The Export command allows you to convert the displayed test set to a Rich
Text Format (.rtf) document and save it for use in requirements or
documentation. The exported file is comprised of the Set level information,
including the Properties, followed by the individual test narrative views.
To Export a Set
1. Select the test set you wish to export from the Sets List.
2. In Sets Editor, push the Export button.
3. In the Export Set to File window, select the file folder destination and file
name. TMX defaults to an rtf document format.
4. Press Save to complete the export.
5. To view the document, use Windows Explorer to select the document or
open the .rft file in Microsoft Word or other word processor.
Generate Set
Once the set has been created in TMX, you will need to generate the
executable code for use with your automation tool. This is accomplished by
the Generate Set button and the five options available.
1/19/2015
Page 98
The number of options available under the Generate Set push button is
determined by the cursor placement in the Set. If you have the cursor placed
outside the Set Items, only
The five options available are:





Run All Items: This option generates a set for all items specified in the
set.
Generate a Set with Item starting FROM: When selected, all items
following the step highlighted by the cursor through the end of the set are
generated.
Generate a Set with all items THRU: All items are generated from the first
step through the highlighted step.
Generate a Set with JUST item: This option limits generation to the
highlighted set item only.
Generate an individual Executable Script for each Item: Instead of
generating one complete set, this option will generate a separate
executable for each item in the set.
Exit TMX
The Exit button allows you to exit TMX or to log out and re-log in with a
different user id or database.
Right Mouse Menu
Save
Following the creation or editing of a set, use either the Save button or select
Save from the right mouse button to complete the transaction and preserve
any changes that have been made.
Save As…
TMX provides the ability to save the current Set with a different name or path
using the Save As function.
Close
The Close function allows you to exit a modified set without saving the
changes.
Set Property
The Set Property option allows you to select the value for the chosen
property. The options available will vary depending on the property
highlighted when the Set Property option is chosen.
To change or set the property value – highlight the property and select Set
Property from the right mouse list. The Property Value Editor will be displayed
which provides a list of applicable selections.
1/19/2015
Page 99
Clear Property
The Clear Property function removes the current value from the selected
property and re-sets it to the default value.
Print
The Print command from the Sets Editor provides three options for hardcopy
documentation. The default view provides a print of the expanded properties
and the set items as seen from the Sets List view.
The second print options provide a print of all steps that failed during the
execution of the set. This is selected by checking the Failed Steps Only box
on the Print Sets menu.
The final option provides a complete set of the test and set narratives. This is
invoked by checking the box next to Test Narratives.
All prints are routed through the default printer.
Exit
As with every tab within TMX, you can opt to exit using the right mouse
button as well. This provides you with the opportunity to quickly log in as a
different user or log into a different database.
1/19/2015
Page 100
Sets Executable
The Executable folder provides a view of the completed script that is used to
drive the testing engine (ex. TestPartner) during execution of the test. This
view provides the test authors with a complete inspection of the script prior to
execution. No modifications are allowed to the executable script from this
folder. All changes are completed using the Sets Editor.
The Sets Executable is created using the Test Executables and System
Actions associated with Sets. These include the Set Begin, Set End and Set
Item Actions located in the Actions Tree under the System Action Type.
Exit
As with the other TMX folders, the Exit button allows the user to exit the
application or logoff and login as another user or to select a different
database.
Right Mouse Button Functions
While in the Executable folder, you have the option of using Select All and
Copy via the right mouse button. The copy function places the selected text
into the clipboard.
1/19/2015
Page 101
6
Chapter
6. Objects
All objects in the application under test that can be “seen” by Windows are
maintained in the “Objects” tab. While a tester might refer to these as User
Interface – or UI – objects, the same is not true from a developer’s
perspective. This point needs to be clear when discussing this application
with developers.
1/19/2015
Page 102
The Objects tab consists of the Tree, Usage and Values folders.
Objects are arranged in a hierarchical or “tree” structure. At the top is the
“Object Trees” collection of an unlimited number of possible object trees.
The next level hosts an actual object tree. Generally, object trees are named
after applications. For instance let’s say that one is testing an online banking
application. Some tests require database queries to validate values added,
deleted, or modified in the database itself, since the presentation layer
doesn’t provide a way to observe these changes.
The tester would create two object trees, one for the online banking
applications and the other for the database application. The same test would
be able to integrate one or the other object tree in various steps as required.
1/19/2015
Page 103
Objects Tree
Adding Objects are generally a simple process. Occasionally, however, the
Object can be a complex procedure that will have to be followed carefully to
insure proper execution of the test cases.
The following will describe the left menu button functions found in Objects
tab.
Add Object
There are two options available under the Add Object which are dependent
on where you have the cursor placed. If the cursor is on the highest level of
the Object Tree when the Add Object button is pushed, the Add Object
Window appears with the Object Class prefilled as “Window”.
Adding a new Object Window is a simple process, starting with the highest
level – or root directory – of the test database. Once created, the individual
windows and objects are then added below the Object Window using the Add
Object button. Note that if you are not in the highest level of the view – you
will not produce this view.
To Add an Object Window
1. Highlight the highest level of the Objects Window window.
2. Select the Add Object button or right mouse button to produce the Object
Window entry window. Note that TMX pre-fills the class in as Window and
does not provide the opportunity to change it.
3. Enter in the name of the new Object Window.
4. TMX will compare the entered name against the current database to
prevent duplicate entries.
5. Press OK to complete the add. The new Object Window will be added in
alphabetical order.
If your cursor is placed on a line other than the highest level, the Add Object
window will open with the Class dropdown available. Select the Class of
object to be added, and then assign an object name.
Object classes are defined in the “Action” tab as “Action Type”. Then,
specific instances of these classes are defined in the “Objects” tab, modeling
the application to be tested.
The Object Tree is an object name repository that ensures each object is
uniquely named within each window. Objects should be named to be easily
recognized by the TMX test authors or business proponents rather than the
program name. This minimizes errors and defects caused by ad hoc
terminology.
Once the Class has been assigned, and the object named, testers need
simply press the “Save” button. Upon saving,
1/19/2015
Page 104
To Add Object
1. Highlight the parent Object Tree in which you want the new object to
appear.
2. Press the Add Object button or select Add Object from the right mouse
menu.
The Add Object window.
3. Select the Class of the object being added from the drop down list.
4. Enter in the Object Name.
5. When saved, TMX will generate the name of the logged in user in the
Change User field and the current date and time into the Change Date
field.
6. Enter in the applicable GUI Attributes if available.
7. Push Save to complete the add.
Edit Object
The Edit Object button opens the Edit Object dialog box which contains the
attributes and properties of the Object selected. This is the same information
that is captured by the underlying test tool and imported into TMX. The import
functions will differ depending on your automation tool.
1/19/2015
Page 105
The Edit Object window can be opened using the push-button, right mouse button and selecting Edit
Object, or by double-clicking on the object to be edited. This example is from the Name field in the sample
Testpage application that was installed with TMX.
The following data is found on the Edit Object window:
Action Type
This is the class of the object. (Note that the Object Class has been
set during the import of the object and cannot be changed once
assigned and saved.)
Object Name
This is the name assigned to the object. Initially this is determined by
the import file but can be changed by the user. It is suggested that the
Object Name be similar to the label identifying the object on the
application window. This will make it more obvious to the automation
tester.
A change made to the Object Name will result in the regeneration of
affected test scripts.
Change Type
The Change Type is a system setting that indicates the status of the
object and can be updated by the user. This setting also determines
the icon displayed immediately to the left of the Object Name on the
Object Tree view. The values available are:
Other values and icons may be assigned by TMX through the object
import process.
1/19/2015
Page 106
Change User
TMX will update this field with the name of user logged into TMX who
updated the object. This is determined by the User ID and is not
editable.
Change Date
The current system date and time are inserted when a change is
made to the Object. This is not editable.
Repository Identifier
The Object attributes and settings captured by the underlying
automation tool. This field is referenced in Action code via {Object
Identifier} System argument. This field is commonly used for
automation tool object repository names/pointers to the object.
Changing this field will affect all test scripts where action code use
{Object Identifier} for this object.
Element Attributes
Object attributes and settings captured by the underlying automation
tool. This field is referenced in Action code via {Object Definition}
System argument. This field is commonly used for object attribute
name/value information used for dynamically locating the object in the
Application Under Test. Changing this field will affect all test scripts
where action code use {Object Definition} for this object.
Delete Object
The Delete Object button – or right mouse button – allows you to delete the
highlighted object. To delete a Window, you must highlight the Window and
use the right mouse button. Select Delete Window to complete the command.
Note that TMX will not allow the deletion of Objects if they are used in
existing test scripts. If attempted, you will receive a warning which includes
the number of test steps using the Object or Object Window. Such Objects
are marked as deleted (shown with a line through the Object Name) and
cannot be used in new scripts. The Object will not be removed and will
continue to be used by the affected test scripts.
Sort/Filter
Similar to the functions found under Tests List, the Object Tree can be sorted
and filters to suit your current project. This is done under the Sort/Filter
button. When selected the Sort/Filter window opens allowing you to sort or
filter the Object Tree view using the Object Folder Properties.
As a default, the Objects contain three properties: Application, Status, and
Window Type. According to the project, you may add, delete, or change
these properties under the Admin tab. Note that you must have Admin
authority to access this area of TMX.
1/19/2015
Page 107
Clear Locks
Being a shared application, access to data records is sometimes locked by
other users in TMX. Occasionally, these locks may not be cleared due to an
interruption of communication with the database. These are typically the
result of improperly shutting down a workstation. This is especially true when
using the default Access database
If a lock is encountered, verify that it is not the result of work being performed
on the database by other users. If not, the locks may be cleared using the
Clear Locks button.
Exit
As with the other TMX folders, the Exit button allows the user to exit the
application or logoff and login as another user or to select a different
database.
1/19/2015
Page 108
Right Mouse Menu
As in the other areas of TMX, the Right Mouse Menu under the Objects tab
provides different functions depending on where the cursor is located within
the Object Tree. These are at the root level, the window or folder/application
level, and at the individual Object level.
There is an additional Right Mouse Menu available when viewing the Objects
Tree in the Folder View. This is when you have used the Sort/Filter function
to display the Object Tree on the basis of one of the Object Properties. That
menu is:
This menu provides four additional functions: Add Common Object Window,
Add Window Folder, Rename Window Folder, and Delete Window Folder.
The final Right Mouse Menu is unique to deleted objects. This menu is visible
when the cursor is placed on an Object within the Object Tree view that has
previously been deleted:
1/19/2015
Page 109
This menu provides the option to delete or undelete the selected object.
The following will cover each of the unique items within the menus as they
occur in the menus as listed above. If the function is a duplicate of the
buttons, or of a prior menu discussion, you can find a review of that function
above in the section above.
Refresh
The Refresh button reloads all object information from the database. This
includes the object attributes and object trees. This is especially useful when
multiple users are working on the same test database and have been
updating the object trees.
While you are working on the database, your view may not reflect the latest
changes made by your co-workers. Prior to generating the tests or exporting
the latest GUI Map, use the Refresh button.
Print
The Print button provides the opportunity to obtain a hardcopy of the entire
object tree or those highlighted.
There are two options available beyond the default print. Those allow you to
select only those notes expanded (the default is to print all notes) and to limit
the print to the highlighted branch only.
All prints are routed to the default printer.
Add Object / Edit Object / Delete Object (or Undelete)
These buttons function as their name implies and are the same as the Add
Object, Edit Object and Delete Object left menu buttons used at the object
tree level.
Add Window / Edit Window / Delete Window
These buttons function as their name implies and are the same as the Add
Object, Edit Object and Delete Object left menu buttons used at the window
object level.
Add Window Folder / Edit Window Folder / Delete Window Folder
These buttons function as their name implies and are used for adding a new
window folder, editing existing window folders and deleting window folders.
Mark Unchanged
This button will set all objects in the selected window to an unchanged status
icon. This can be useful to track future changes. When any future changes to
this objects are made, the icon will change and be easy to spot. (Note, this
cannot be undone one set)
1/19/2015
Page 110
Show Unused Objects Only
This function will refresh the object list and only show objects that are not
used in any test scripts. It’s a quick way to see if you’re using all the defined
objects. To remove this filter, right click the mouse and unselect this option.
Sort Objects by Name
This function will sort all the objects for a window by name as opposed to the
default order they were created in. To undo this sort and return to default,
right click the mouse and unselect this option.
Add Child Object
Using the right mouse button, you can add child objects to those objects
already displayed on the Objects Tree.
The Add Child Object function is only available via the right mouse button.
Add Common Object Window
TMX allows you to create a folder within the Object Tree that contains all
objects that are common throughout the application windows under test. With
this, you won’t need to create the same objects over and over for each of the
windows you are testing. Items such as common navigation buttons are
typically included in the Common Object folder.
To add Common Object, you must be in a folder view of the Object Tree.
Then, using the right mouse menu, select Add Common Object Window while
the cursor is placed on any of the folders.
1/19/2015
Page 111
The Add Common Object function is only available via the right mouse button.
A “Common Object Window” must be added to the Object Tree. Choose this
menu item from the popup menu by right clicking on the Object tree node.
Once an “Object Tree Window” is created you may add objects to that
window in a very similar manner to adding objects to ordinary window. Once
you have created Common Objects they may be “included” in other window in
the Object Tree. This allows objects such as tool bars or common navigation
links to be defined one time and then “included” in other windows without
having to define the same objects over and over. If the common objects
change, they only need to be maintained in one place.
1/19/2015
Page 112
Objects Usage
The Objects Usage folder provides a complete listing of all instances where
the selected object is used. The list is provided by Test Case in alphabetical
order.
The expanded view provides the step number, or numbers if used multiple
times within one test, of the object selected.
The Objects Usage folder displays where the selected object appears in test cases and steps.
Double clicking on the test name will navigate you to the Tests Editor folder to
view the selected test in its entirety. You can easily return to where you were
by clicking on the Objects tab.
Generate
Selecting the Generate button on the left menu or right mouse click menu will
generate all tests related to the Object being displayed. This option assures
that all tests affected by changes to the Object are updated to reflect the
changes without having to leave the Object Usage folder.
1/19/2015
Page 113
Export List
Selecting the Export List button on the left menu will open an Export Usage
List window that allows you to save the Usage List into an external CSV file.
Refresh
The Refresh button (right mouse click menu only) updates all views within the
application with the most current data from the database. The system rereads the database to update any changes that may have been made during
the session.
This is extremely valuable in multi-user environments where changes may
have been made during the session. It is a good idea to get in the habit of
using Refresh prior to Generate and Execution of tests.
Print
The Print button (right mouse click menu only) provides the opportunity to
obtain a hardcopy of the entire object usage folder.
All prints are routed to the default printer.
Exit
As with the other TMX folders, the Exit button on the left menu or right click
mouse menu allows the user to exit the application or logoff and login as
another user or to select a different database.
1/19/2015
Page 114
Objects Values
The Objects Values folder provides a view of those objects within the current
database that have argument values defined. This is useful when attempting
to update and identify specific data values used in tests. Through review of
the Objects – Values, you can quickly view the data used within the Object’s
arguments and determine the frequency in which the value is used
throughout TMX.
Once the appropriate value is located and the Object is known, switching to
the Usage folder identifies the specific test cases utilizing the data values.
Using the Replace command in the Objects Values allows quick updating of
the data.
The Objects Values folder displays the selected object argument input values.
1/19/2015
Page 115
Replace
The Replace command is an extremely powerful tool within TMX. With it, you
can easily update large sets of test cases that have been affected by new
table values or code changes.
For example, assume the application under test has a series of product
codes that are updated periodically by jurisdiction. Rather than recreate the
suite of test cases for each new product code, one comprehensive set can be
easily updated with the Replace command. A newly created product code
can be substituted into the suite of tests and the entire set re-generated and
executed in a matter of minutes.
The data type of the input argument value can also be changed by selecting
the desired data type from the drop-down list. This is useful, for instance, if
the input arguments were mistakenly scripted as literals when they should
have been variables or vice-versa.
The Replace Values window showing replacement options.
To Replace a Data Value or Data Type
1. Navigate to the Objects Values folder.
2. Locate the data value to be changed. Notice that TMX provides a count of
instances this data value is used throughout the current database.
3. Highlight the data value and select the Replace button.
4. The Replacement Value window is displayed. Update the data value with
the new argument and/or the data type and press OK to complete the
transaction.
TMX will update all instance of this value where used in the selected
argument and object.
Note: Before running the tests following a Replace, you will want to generate
the tests again to assure all of the values have been updated in the
executable scripts.
Generate
Selecting the Generate button (right mouse click menu only) will generate all
tests related to the Object being displayed. This option assures that all tests
affected by changes to the Object are updated to reflect the changes without
having to leave the Object Value folder.
1/19/2015
Page 116
Refresh
The Refresh function (right mouse click menu only) re-reads the database
and updates the views with the most current information. This is especially
beneficial in multi-user environments where data can change rapidly during
your working sessions. Using the Refresh command frequently assures that
you are working with the most current information.
Print
The Print command (right mouse click menu only) provides a readily
accessible hardcopy of the current Objects Values folder via the default
printer.
Exit
The Exit command (right mouse click menu only) allows you to exit TMX
entirely or log back into the application with a different User ID or to change
databases.
1/19/2015
Page 117
7
Chapter
7. Actions Functions
Actions are the fundamental building block of the Narrative and
Executable code within TMX. They can be defined as those things that
cause some change to an object. Actions are defined and controlled
within the Actions tab and the associated Tree, Usage and Values
folders.
The Action Tree folder provides a list of all Actions contained in the
current TMX test library or database divided into three types:



Actions: A behavior or activity that can be performed on a
particular object.
Processes: Similar to actions, but do not relate to a single
object. These may be activities like keyboard functions (i.e.
backspace, space, enter, etc.) that are not related to a specific
object – or processes may be related to several objects such as
logging into a test application.
System Actions: These are actions that are used by TMX
without being specified by the user for a particular test case.
Examples of these are Test Begin, Step Begin, Change Window,
etc. These are used by the system and cannot be selected by
the user for inclusion in a test case.
Under each group of Actions, there are Action Types, which are a
collection of behaviors or keyword activities that can be performed
against objects of that type. For example, if the Action Type is “Check
Box”, then you will see Actions that make sense for Checkboxes like
“Check On” or “Verify Off”.
Each Action contains a segment of executable script. When combined
with specific objects in a test, TMX uses the actions to generate both
structured English narratives, and executable scripts. The action code is
then combined to produce the actual test case script.
The Actions Usage folder, much like the Objects Usage folder, provides
quick access to locating particular actions and where they are used
throughout the test database. The Actions Values folder, much like the
Objects Values folder, provides a view of those actions within the
current database that have argument values defined.
Actions – Tree
The Actions Tree displays all current Action Types in alphabetical order.
Clicking on the checkbox to the left of the Action Type will expand the
folder to display the underlying Actions.
The Action Tree defaults to the alphabetical listing of all actions grouped by Action Type.
Under each Action Type, the associated Actions are displayed in
alphabetical order. For example, in the picture above, there are three
actions defined as possible with the Action Type “Checkbox”.
The default action for the Action Type is underlined – in this case the
default action for “Checkbox” is “Check On/Off”. The default action will
1/19/2015
Page 119
always appear first in the Action Editor window when a step is scripted
using an object of this Action Type.
There are three groups or classifications of Actions: Actions, Processes,
and System.
The majority of the Action Types included in the sample database are
contained in the Actions. These are the keyword activities or actions
that can be performed on a particular field or object contained in the
application under test (AUT). Actions pertain to only one object at a
time.
The available actions are determined by the object class. For example,
under the “Editbox” Action Type in the TMX sample database, the
available actions are those that are applicable to the object class
“input”, “edit box” or “text box”. As such, you would not have access to
actions that are applicable to checkboxes or radio boxes.
Processes are similar to Actions, but either do not have a relation to an
object or object class, or maybe related to many objects. For example, a
process may relate to a keyboard action such as “enter”, “tab”, or
“backspace”. These do not relate specifically to an object included in the
AUT.
A Process may be defined as interacting with many different objects as
is the case with logging into the AUT. In this case, the process may
include actions relating to various objects such as the “url” or location of
the AUT, the “user ID”, and “password”.
The other class of Actions are the System Actions. These are the
actions that are used by TMX to complete the test case and cannot be
individually selected by the TMX user.
The following will review the Action functions starting with the buttons
found in the left menu of the work space, followed by the unique
functionality found in the right mouse menus.
Add Action
The Add Action function opens the Action Editor and allows the user to
create an action within the Action Type that was selected. Note that you
must be on an Action Type in order to create the Action which will
appear under that type.
A complete review of the Action Editor appears below in the Edit Action
section.
Copy Action
Actions can easily be copied from one Action Type to another or into the
same Action Type by using the Copy Action button. Highlight the Action
1/19/2015
Page 120
to be copied and press the Copy Action button. The Action and
associated properties will be copied into the TMX clipboard for
subsequent pasting.
Note the information message in the lower right corner of TMX indicates
that the Action has been copied and remains in the copy buffer.
Paste Action
Actions may be pasted into the same or different Action Types simply
by using the Paste Action button. The action residing in the copy buffer
will be pasted.
TMX will generate the Action Name entry window with the original name
provided. Press OK to complete the transaction or modify the name
prior to saving.
Should an action with the same name already exist in the Action Type,
TMX will generate a warning message and require that the name be
modified to make it unique within the Action Type.
Edit Action
Actions may be modified or changed by highlighting then, then using
the Edit Action button or via the right mouse button. The current
attributes and arguments will be displayed.
The Action Code Editor window is comprised of several buttons, entry
fields and sub-windows. The following will review each of the major
components of the editor.
1/19/2015
Page 121
Save
The Save command will capture all of the entry on the editor and save it
to the database making the new Action available for future editing and
selection within tests.
Choose Icon
Select the icon you wish to display in the Tests from the drop down list.
The selected icon will display to the right of the list when selected.
Arg(ument) Popup
The Arg Popup is the list of arguments available in TMX. This provides
immediate reference to those arguments that may be used in building
test cases.
Three lists are available in the popup window: Local Arguments, System
Arguments and (Test) Properties.
The values associated with the arguments are available for inserting
into the Narrative, Executable, and Notes by double clicking on the
value.
Whether the value of the argument is inserted with or without doublequotes around it, can be selected via the ‘Omit Quotes’ and ‘Include
Quotes’ radio buttons.
The Argument List Pop-up window displays the availlabe Local Arguments, System Arguments and
Properties for the selected Action.
1/19/2015
Page 122
Cancel
The Cancel function will clear all entries made on the Action Code
Editor and return you to the Actions Tree without saving any of your
work.
Type:
The Action Type corresponds to the Object Type on which the action is
performed.
This is determined from the Action Type you were in when the Add
Action button was selected. You cannot edit this field, so if the Action
Type is not correct, select Cancel to return to the Actions Tree, then rehighlight the correct Action Type and then select Add Action.
Action:
Enter the name of the Action you are adding to TMX. Action names
cannot be blank or contain special characters such as ( ‘ \ / : * ? “ < > !
etc.
Icon:
Displays the currently selected icon for this Action.
Message Box:
The Action Code Editor provides various messages regarding the status
of the Action as it is being created and used within TMX. For instance,
once the Action has been created and is used within test cases, the
arguments within the Action cannot be changed without unpredictable
results when executed. TMX recognizes when these conditions occur
and provides informational messages advising you of potential
problems.
Checkboxes:
There are four checkboxes to consider while adding or editing an
Action:
 Action Is Inactive: Actions can be designated as inactive by clicking
on this checkbox. The attributes and properties of the Action are
saved into the current Database but it is grayed-out in the Actions
Tree and not available for selection in the Actions Step Editor or in
tests. This is useful when the specific action has been made
obsolete or has not yet been provided in the application under test.

1/19/2015
Expert Action: Activating this checkbox will flag this action as
available to “Expert”. This means that the Action will only be visible
in the Action Dropdown Lists when “Expert Actions” is activated.
The most frequent occurrence of this is while creating tests and
adding a step. The default in the Step Editor is for Expert Actions to
be excluded from the dropdown list.
Page 123
Clicking on the Expert Actions checkbox will display all availalbe actions.

Generate Logging default for adding steps: Checking this box
automatically adds logging code into the Action. When active, the
action when used in test cases will be tracked within the run logs.

Continue On Error default for adding steps: Checking this box will
allow the test script to continue past the step with this action in the
event that this action fails.
Last Change:
TMX tracks changes within the Action Code Editor and indicates when
the most recent changes were made. This is system generated and
displayed in the Last Change box.
Arguments:
For each Action created, there may be up to 7 arguments provided.
Details For “:
For each Argument entered, you may select the appropriate Value Type
using the radio buttons to the right of the Argument. There are 9 Value
Types available:




1/19/2015
Literal: The argument value specifically keyed in by the user. This is
used within the narrative and executable scripts.
Shared: The argument value is obtained from the shared value
designated by the user. Selecting the “Shared” Value Type will
cause the argument field to generate a pull-down list of shared data
names to be selected.
Variable: The argument value is the variable name designated by
the user. For example, a text or numeric value can be captured from
the application into the variable.
Numeric: The argument value allows only a numeric character
(value from 0 to 9) to be used. The entered argument value is
placed in the TSL without quotation marks.
Page 124

List: The List option restricts the test author’s input to items
contained in the list. When used, the List radio button will generate a
button immediately to the right of the list. This provides the list
values for the argument that is easily edited and maintained.
These values are available for the user to select from when creating
the test case.
.
The List Values is displayed using the button to the right of the List radio button




Window: When a Window name is used as an argument, this
creates a window name drop-down list in the Test Editor to be
selected.
Test: Another test name may be set as the argument value. Used in
an action that calls another test in the library. The test step editor
provides a dropdown list of tests stored in the current database.
External: The argument value is obtained from an external
spreadsheet, based on the user’s input. Used in conjunction with
“Read” and “loop” actions
Code: When selected, this tells TMX that the argument value
entered by the user is code.
Default Value
The Default value is used to provide the default data source for an
action. Deleting the default value is easiest if you set the data type to
‘Literal’ first.
Action Background Color
This listbox allows you to select the color that every scripted step using
this action will be highlighted.
1/19/2015
Page 125
Action Code Editor Tabs:
There are three specialized tabs available on the Action Code Editor,
each performing a separate function within TMX. These include the
creation of the test narrative, the executable for the selected Action and
the Action Help that defines the Action and explains how it is to be used
within the test case.
All tabs make use of specialized function buttons:

Argument Pop Up: This function is used to insert argument list
variables that have been previously defined in TMX. Pressing the
Insert Argument button generates a pop-up list of all possible
acceptable variables.
There are three kinds of variables: Local Arguments, System
Arguments and Properties
The System Variables (both System Arguments and Properties)
include many arguments like Action Type, Object, Step, Comment,
Test Name, Window Name, Test Path, Test XLS, and Date
Generated.
The User variables (Local Arguments) includes all of the user
defined argument names defined in the Arguments section as the
Action Code Editor.
The actual value of the variable is substituted in the narrative and
executable scripts. For example, in the narrative, using the “UserID”
object, the correct entry would be:
In the field {“Object”}
The narrative would appear as:
In the field “UserID”




1/19/2015
Insert Tab Button: Provides for quick formatting of the Narrative
or Executable entries. Selecting this assists the script developer in
indenting code lines according to accepted standards.
Delete Tab Button: This option deletes the tab or positions the
text line to the left. As with the Insert Tab Button, this is used to
assist developers in the proper placement of executable code.
Font Size Button: Provides for quick formatting of the
window font sizes. It cycles through small-medium-large font
The font size will be remembered.
Tabs to Spaces Button: This will convert all tabs in the
window into spaces. This can be useful for test code
formatting.
editor
sizes.
editor
script
Page 126

Search: The search/find box provides search function for all editor
windows. Insert the value to search for in the box.
o ‘a=A’ button sets case sensitivity
o ‘ + ’ moves to next found match
o ‘ - ‘ moves to the previous found match
o text will turn red when no matches exist
Narrative Tab:
The Narrative Tab contains the information that constitutes the
structured English narrative associated with the action. This entry is
inserted into the Narrative folder when the test cases are created. Use
of the User and System variables help make this narrative very
descriptive of the object this action is being used with.
Executable Tab:
The test script author can enter the script code segment associated with
the Action. The script segment for each action is assembled into a fully
executable test script in the Executable sub-tab when test scripts are
generated. This code will be in the syntax used to create valid test
scripts to be executed by the automation tool being used.
Action Help Tab:
The Action Help Tab provides the opportunity to describe the Actions’
behavior, purpose and possibly the context in which it is to be used. In
the Step Editor-Action Help-Notes box, the Actions Help button is used
by the test authors to understand how the action could be used in the
context of the test being created.
The ‘Action Help’ button on the Step Editor window opens the ‘Notes’ box that will display the text
entered into the Action Help tab.
When modifications are complete, select Save to complete the
transaction or Cancel to abort the changes.
1/19/2015
Page 127
Rename Action
The Rename Action button allows the highlighted action’s name to be
modified or changed within the same Action Type.
Highlight the target Action and select the Rename Action button or right
mouse button. TMX will produce the Rename Action window with the
current Action name. This can be modified or completely renamed.
Note: Systems Actions may not be renamed.
Delete Action
To delete an Action, highlight the target Action and use the Delete
Action button or the right mouse button. A confirmation message will be
displayed. Press OK to complete the delete.
Note: System Actions may not be deleted from the database.
Import Action
The Import Action button allows you to easily copy actions from one
database into the current database.
To import an action, TMX requires that the current database have the
same Action Type as the Action to be imported. If the Action Type is not
available, you must create it prior to importing the Action.
Import Actions window used to import actions from other databases.
1/19/2015
Page 128
To Import and Action
1. Highlight the Action Type within the current Action Tree that you will
be importing into.
2. Select the Import Action button.
3. In the browse window, locate the target database and select Open.
4. TMX produces a list of the actions associated with the Action Type.
Select the action to be imported from the list and press Import.
5. If the same Action exists in the current database, a warning
message will be displayed offering you the option of importing just
the Executable script and Narrative for the selected Action.
6. Select Yes to complete the transaction.
Keyword Grid
The keyword grid is a useful tool to view some or all the keywords
(actions, processes, system actions) in an easy to read grid format.
This grid can also be exported via the ‘Export’ button.
Keyword Grid window that puts all keywords (actions, processes, sys actions) into an easily
viewable form.
Refresh
The Refresh button updates the script display by executing a complete
re-read of the database. This is especially useful in multi-user
environments where rapid changes can occur frequently during working
sessions.
Exit
The Exit button allows you to leave TMX from the Actions folder, without
having to return to the main menu or window. Prior to leaving the
application, TMX allows you to sign back into TMX under a different
user Id or to select a different database.
Actions – Usage
The Actions Usage folder provides a view of the selected Action and
where it has been used within the current database.
The default view provides a compressed view of the test cases that use
the action selected in the Actions Tree. To view the test steps within the
listed test case, click on the “+” immediately to the left of the test name.
1/19/2015
Page 129
Action Type
Test Case Name
Object Name
Value used in test
step
Test Case step where action is used
The Actions Usage folder provides an alphabetical list of the test cases using the Action selected
under the Action Tree.
Double-clicking on a test within the Actions Usage folder will navigate
you to the selected test case in the Tests Editor.
Generate
Selecting the Generate button on the left menu or right mouse click
menu will generate all tests related to the Action being displayed. This
option assures that all tests affected by changes to the Action are
updated to reflect the changes without having to leave the Actions
Usage folder.
Export List
Selecting the Export List button on the left menu will open an Export
Usage List window that allows you to save the Usage List into an
external CSV file.
Filtered
The Filtered button on the left menu will filter the current view to only
show tests that are currently displayed in the Test List view. Press the
button again to undo this filter.
1/19/2015
Page 130
Refresh
The Refresh button (right mouse click menu only) updates all views
within the application with the most current data from the database. The
system re-reads the database to update any changes that may have
been made during the session.
This is extremely valuable in multi-user environments where changes
may have been made during the session. It is a good idea to get in the
habit of using Refresh prior to Generate and Execution of tests.
Print
The Print button (right mouse click menu only) provides the opportunity
to obtain a hardcopy of the entire actions usage folder.
All prints are routed to the default printer.
Exit
As with the other TMX folders, the Exit button on the left menu or right
click mouse menu allows the user to exit the application or logoff and
login as another user or to select a different database.
1/19/2015
Page 131
Actions Value
Similar to the Usage folder, the Actions Value folder displays the values
used for the selected action. Along with the view, the folder provides the
functionality to globally change the selected value.
Action Type
Action Name
Value used in test
Data Type
Number of
instances the data
value is used in
current database
The Actions Value folder displays all values for the action selected in the Action Tree folder.
The default view of the Actions Values displays all values used by the
selected action along with the number of instances.
Replace
The Actions Value Replace function allows you to update the selected
value throughout the current database with one transaction.
1/19/2015
Page 132
The Replace Values window for action argument values.
To replace the current value of an Action, select the Action and press
the Replace button. The Replace Values window will appear displaying
the current value used for the Action. Key in the modification or replace
the current value with a new value and press OK to complete the
change.
The data type of the action argument values can also be changed by
selecting the desired data type from the drop-down list. This is useful,
for instance, if certain input arguments were mistakenly scripted as
literals when they should have been variables or vice-versa
TMX will produce an informational message that this is a global change
and cannot be undone. Press OK to finalize the change.
Exit
The Exit button allows you to leave TMX from the Actions folder, without
having to return to the main menu or window. Prior to leaving the
application, TMX allows you to sign back into TMX under a different
user Id or to select a different database.
Generate / Refresh / Print
Same buttons and functionality as described in Actions Usage above.
1/19/2015
Page 133
How Actions Work
The key to executable code generation in TMX is the keyword actions
and how they relate throughout TMX. Once you understand what the
actions control and how they interact with the different functions and
components of TMX you will appreciate how the automation engineer
has complete control over what is generated and how.
The diagram on the following page provides a synopsis of where
actions influence different features and functions of the TMX framework
and how you can control and effect how the executable code is
generated.
Appreciating this interaction, however, does not diminish the need for
an automation engineer to be knowledgeable and experienced with the
underlying automation tool, programming, and automation in general. It
is imperative to the success of the automation project that a qualified
automation engineer is in place within your testing organization.
The diagram below displays the interaction of the Action Code Editor
and the primary functions of TMX starting with the Tests Editor
displayed in the upper left corner.
Each Action corresponds to one step in the Tests Editor view. The icon
that appears to the left of the test step is determined by the action.
In addition, the default value of the Generate Step Logging and
Continue on Error options are controlled by the Action. These two
options can be over-ridden within the Step Editor.
1/19/2015
Page 134
Keyword Action Components
1/19/2015
Page 135
8
Chapter
8. Admin Functions
All TMX administrative functions are contained under the Admin tab.
Only those User Ids with the proper authority level have access to these
functions. Managing users, backups, database releases and
miscellaneous functions can be found under this tab.
Figure 8-1: the Admin tab.
1/19/2015
Page 136
Admin - Tools / Users
All User ID management functions are located under the Tools/Users
folder.
Add User
Adding new users within TMX is an easy process consisting of creating
a unique User ID, User Name and Password. Concurrent with setting up
the User ID, you will need to determine the access permissions. In TMX
the access level is controlled at the tab level with the exception of the
Action Code Editor.
To Add a New User
1. Select the Add User button in the Admin Tools/User folder.
2. Create a unique User ID for the new individual. The User ID can be
up to 30 characters long.
3. The User Name is an optional field. Typically this is the user’s
complete name. If not specified, this filed will be set to be the same
as the User Id.
4. The Password is optional within TMX. If not entered, a password will
not be required for this User ID in order to log into the system.
5. Select the access levels appropriate for the new user. This is
accomplished by checking the appropriate tab access.
6. The Actions Tab is the only area that can be controlled at a lower
level by specifying whether the user has access to the Actions Code
Editor.
Edit User
Once the User ID has been created, the User Name, Password, and
Access Levels can be modified by highlighting the User ID to be
modified and selecting the Edit User button.
Press Save to complete the modifications.
1/19/2015
Page 137
Delete User
Deleting a User ID from TMX is accomplished by highlighting the User
ID on the Tools/Users folder and selecting the Delete User button. A
confirmation message will be produced. Pressing Yes will complete the
transaction.
Import Users
This function allows you to import Users from different TMX databases.
Pushing the Import Users button will allow you to select a database to
open. If it’s not currently listed in the drop-down list, use the Browse
button to open the Windows Database list and then select the
appropriate library.
Once selected, use the Connect button to open the Import Users list.
This list will allow you to select which users are to be imported.
Backup
As with any mission critical application, frequent backups of your data
should be made to insure security and easy recovery should
unrecoverable errors occur. User Ids with Admin access rights have the
ability to create database backup copies on demand via the Backup
button.
To Backup the Current Database
1. Select the Backup button to display the Backup Database window.
1/19/2015
Page 138
Backup Database window: TMX suggests a file name using the current date and time. Should
you have a different naming convention or backup procedure, you will want to modify the
name accordingly.
2. TMX provides a default file name consisting of the current system
date and time.
3. Verify the Backup database name and location are correct. Make
any desired changes, such as changing the file location or drive).
4. Select Save to complete the backup.
Note: This process creates backup copies of the current database,
and does not create a complete system backup or unselected
databases. To insure complete data security, refer to your system or
network administrator.
New Release
The New Release function allows you to create a new test database
with or without copies of the existing test cases, resetting the status of
all objects within the current database, clearing shared values,
removing the current user access, or creating a backup of the current
database.
The options available allow you to create a complete copy with the
existing test cases and user accesses. This is useful when preparing for
a new release of the current software. You can maintain the tests for the
current release and duplicate the entire suite of tests for the new
release, which will be modified in accordance with any release changes.
The options also allow you to completely clear the existing test suite
and start fresh. The option of clearing the users associated with the
database is useful for those instances where different teams may be
employed for testing different applications.
1/19/2015
Page 139
To Create a New Release
1. Press the New Release button to generate the New Release
window.
2. Enter the new database name. You can modify the name as
displayed in the field or press the icon to the right to browse the
available folders.
3. If a duplicate name is entered, TMX will generate a warning
message and prompt you for a unique name.
4. Select the conditions in which the new database is to be created:
a. Clear All Tests & Sets: When checked, this option will create an
empty database – useful for creating a test database for testing a
new application. Leaving this option un-checked will create copies of
the existing Tests and Sets into the new database – useful when
preparing a new suite of tests for a version of the existing
application.
b. Reset all objects to “Unchanged”: This allows you to reset all object
properties to “unchanged” regardless of their current status.
c. Make Backup of Current Database first: This command will create a
backup copy of the existing database as well as creating the new
database.
5. Press Save to complete the creation of the new database.
6. TMX will prompt you to enter the newly created database without
going through the login process. If you select no, you will remain
logged into the old database.
Compact DB
Since the default database for TMX is a runtime Access database,
many of the Access database utilities are available under the Admin
functions. One of these that should periodically be run is the Compact
DB. This action runs the Access Compact and Repair function. If you
delete data or objects in an Access database that is related to a
particular topic or purpose the file can become fragmented and use disk
space inefficiently. Compacting the Access file makes a copy of the file
and rearranges how the file is stored on your disk.
Compacting optimizes the performance of the TMX Access databases.
It does not affect database objects.
1/19/2015
Page 140
The Compact DB function is not available if you have ported your
database to another OBDC standard database format such as Oracle or
SQL.
Cleanup DB
This utility will scrub the database and remove orphaned values and
data in the database tables.
Clear Locks
Being a multi-user application, TMX has a number of system generated
database locks that will prevent unauthorized or accidental updating of
shared scripts or objects. Admin level users using Admin > Tools can
clear all system locks by using the Clear Locks function.
A typical message indicating that additional users have locked a function on TMX.
Clearing Locks releases all database and record locks currently in place. This may allow
conflicts to occur over record access.
Review Record Locking under Chapter 9: Troubleshooting prior to
using this function.
Reset Display
The Reset Display utility will immediately reset all screen and window
sizes to the original TMX default sizes. This is useful after you have
repositioned and re-sized windows to view large Test Lists or Object
Trees and you wish to return to the normal views.
1/19/2015
Page 141
User Message
The User Message function is particular to those with Admin access.
This allows the TMX administrator to send messages to all users who
are currently logged into the TMX database. In addition to the message,
the sender may force the users to log off the database within the
specified time frame. This is especially user when performing database
or back up utilities that require all users to be logged off TMX.
Pressing the User Message button opens the User Message window
allowing entry of the message along with expiration times.
The User Message window.
Clear Profile
During the use of TMX, changes made to window sizes, filter settings
and other user defined settings are saved. Sometimes you may wish to
clear these settings and return to the original configuration. This is
easily done using the Clear Profile utility under the Admin functions.
When selected, TMX will prompt you to confirm that the settings should
be restored to the default values.
Clr DSN User
The Clr DSN User function clears the saved UserID/Password for the
currently logged in database. Upon next logon, the Admin will have to
re-establish users for the database.
1/19/2015
Page 142
Clone DB
The Clone DB functions allows you to make a copy of your existing
database.
UnRegister
To un-register your copy of TMX select the UnRegister button found in
the Admin Tools/Users folder. You will be presented with a confirmation
message prior to completing the transaction.
Caution: once the process is completed, your copy of TMX may not
have the full functionality of a registered copy of the software. This step
is not reversible – you will have to re-register your copy with Critical
Logic in order to gain full functionality.
1/19/2015
Page 143
Exit
The Exit button allows you to leave TMX from the Admin folder, without
having to return to the main menu or window. Prior to leaving the
application, TMX allows you to sign back into TMX under a different
user Id or to select a different database.
1/19/2015
Page 144
Admin - Properties
The Properties functions within TMX provide complete control over test
case organization, sorting and filtering. With the advanced capabilities,
you can create any classification arrangement necessary to suit your
particular organizational and procedural requirements.
One of the best places to see the effect of properties is within the Tests
List folder. With the Filter applied, test cases can be seen within a
number of organizational views. These views are controlled by the
properties associated with the individual test cases.
The properties listed in the Sample Database (shown in the examples
throughout this guide) are provided for illustrative purposes and may not
fit your particular requirements.
It is suggested that prior to creating large test libraries, that you
consider what attributes of test cases may be need for organizational
and sorting purposes. From there, you have the basis on which to add
test case properties.
Each of the Properties trees contains the same available buttons and
right mouse buttons. These provide the ability to add, delete and
manage the properties and functions within each property.
Sample Database Properties
The following items are listed in the Sample Database Properties.
These include both system generated and user defined properties.
Properties – Window
Properties – Test
The system generated properties under Test are Last Generated
and Script Path. These have specific TMX program code
associated with them and cannot be deleted.
The other properties listed in the Sample Database are included
for illustrative purposes and may not be suitable to your specific
procedures or requirements. These include the Author,
Description and Script Path.
The Script Path indicates where the executable scripts are
placed in the database.
Properties – System
System Properties control how TMX operates and helps to
configure how and where tests are generated.
1/19/2015
Page 145
Properties - Set
By default, Sets contain four system-generated properties:
Author, Automated, Last Generated, and Priority. As with the
other properties, user defined properties can be added and
managed through the Admin functions.
The fifth property included in the Set properties in the sample
database is that of Path.
Others not listed in the Sample database:
Properties – License
The License properties describe what functions and add on
utilities are installed with your TMX application. There are a
number of specialized add-on applications that may have been
purchased and installed with your system.
Properties – Backup
A history of the system backups is stored under the Backup
folder under Properties.
Figure 8-2: Clicking on the Backup folder under the Admin tab provides a chronological list of the
system backups and location.
Add Property
The Add Property button allows you to add new properties to any of the
folders: Tests, System, and Set. License and Backup properties are
system generated and may not be modified.
To Add a Property
1. Select the tree of the property you wish to add by highlighting it or
one of the subsequent properties.
2. Click the Add Property button or right mouse button to generate the
Property Definition Editor window.
1/19/2015
Page 146
The Property Definition Editor
3. Check the first box if the property being defined should appear on
the Tests Narrative.
4. The property’s Sequence determines where the new property is to
be displayed on-line and in the narrative descriptions. The default
value of 99 allows the newly added property to be displayed at the
bottom of the list. To move in to the top, you would enter “1”. If there
is a property with the same number you’ve indicated, the two
properties will be listed in alphabetical order.
5. Check the Required box if the new property is to be required.
6. If a Property Type of ComboBox is selected, an additional checkbox
– Restrict to List – will appear on the Property Definition Editor. If
checked, only values contained in the defined list will be allowed.
7. Checking the Allow multiple values checkbox provides the option of
multiple property values being selected and saved with the test.
8. TMX will provide the Object Type according to the Property you
selected.
9. Enter in the Name of the Property to be added. This is the narrative
that will be displayed in TMX on-line descriptions and narrative
reports.
10. Select the Property Type form the drop-down list that best describes
the attribute being added. If the Property Type ComboBox is
selected, an additional function will be available allowing the list of
acceptable values to be created.
1/19/2015
Page 147
When ComboBox is selected from the Property Type drop-down list, the List Values icon is
presented to the right of the list. Clicking on the icon opens the List Values editor.
11. Next, if a Default Value is to be used, it can be selected from the
drop-down list or added if the value is not shown.
Edit Property
All user-defined properties may be edited. Select the property by
highlighting it and using the Edit Property button, using the right mouse
button, or by double clicking on the property. TMX will produce the
Property Definition Editor.
When finished updating the attributes, select Save to complete the
modifications or Cancel to return to the Admin Properties.
Delete Property
User defined properties may be deleted by highlighting the property and
selecting the Delete Property button or the right mouse button. TMX will
produce a confirmation message. Select Yes to complete the delete.
Clear Locks
Being a multi-user application, TMX has a number of system generated
database locks that will prevent unauthorized or accidental updating of
shared scripts or objects. Admin level users using Admin > Tools can
clear all system locks by using the Clear Locks function.
1/19/2015
Page 148
Exit
The Exit button allows you to leave TMX from the Actions folder, without
having to return to the main menu or window. Prior to leaving the
application, TMX allows you to sign back into TMX under a different
user Id or to select a different database.
1/19/2015
Page 149
9
Chapter
9. Putting It Together
The key to TMX is how the keyword actions interact with objects
imported from your automation tool to produce executable scripts. The
Automation Engineer has complete control over this process and needs
to understand how the interaction occurs and where changes will affect
the output.
Anatomy of an Executable Script
To properly understand the generation of the Executable script, we
need to review each component of an example. In this case, we’ll use
the test case created in Chapter 2: “Test Case 01”.
Regardless of the automated tool being used in conjunction with TMX,
the Tests Editor and Narrative views will appear the same. The first true
difference between the how the tools are used will appear when
examining the executable script.
To show the differences and to view the detail of the executable scripts,
the following sections will look at two different versions of the same test.
The “Anatomy” views were both generated on the basis of the test case
created in Chapter 2.
1/19/2015
Page 150
The Tests Editor view in both versions will be somewhat identical:
1/19/2015
Page 151
The Narrative of Test 01 for both versions, too, is virtually identical:
Difference occurs, however, with the Executable since these have been
designed to operate with different automation tools. The differences are
due, both, to difference in the scripting language used by the underlying
tools as well as due to differences in how the keyword actions are
created by the automation engineer using TMX.
The following provides a glimpse of how TMX generates the actual
executable scripts for QTP and TestPartner.
1/19/2015
Page 152
Anatomy of a TMX for QTP Script
Test heading
Test initialization
and setup with
error handling
'--------------------------------------------------------------------------------------------------------------'
Test 01
'
Generated by TMX "9/23/2008 12:33:57 PM"
'------------------------------------------------------------------------------------------------------------'On Error Resume Next
tmxTestName = "Test 01"
if tmxCallingTest = "" then
tmxLogComment = ""
tmxStatus = "pass"
tmxDir = "C:\Program Files\TMXqt\SampleQT_Original.mdb\"
tmxLogFile = tmxCreateLogFile ()
tmxPass = 0
tmxFail = 0
else
tmxTestName = tmxTestName & " (called)"
End If
'-------------------------------------------------------------------------------------------rc = tmxMain()
'run the test steps
'-------------------------------------------------------------------------------------------If tmxFail > 0 Then
tmxStatus = "fail"
else
tmxStatus = "pass"
End If
System Action:
Test Begin
if tmxCallingTest = "" then
If rc = true Then
tmxNarrative = "Test complete, all steps were run."
else
tmxNarrative = "Test stopped, not all steps were run."
End If
tmxAction = ""
tmxStep = "END"
tmxNarrative = tmxNarrative & vbnewline & "Passes: " & tmxPass & "
& tmxFail
Fails: "
TMXRunLog()
TMXCloseLogFile
reply = msgbox ( tmxNarrative & vbnewline & "Do you want to view the log
now?" ,vbYesNo, tmxTestName )
If reply = vbYes Then
systemutil.Run tmxLogFile
End If
End If
' END OF "Test 01"
'--------------------------------------------------------------------------------------------------------------Function tmxMain()
System Action:
Step Begin
1/19/2015
Denotes Step,
Action used
'--------------------------------------------------------------------------------------------------------------tmxStep = "1"
Page 153
Test Action:
Edit > Input
System Action:
Step Logging
System Action:
Step Begin
Test Action:
Edit > Input
System Action:
Step Logging
and what
appears in the
Narrative
Defines the
Input action into
an Edit box
object – in this
example the
data “Bob” into
the object
“Name”.
Defines Step
Logging
Denotes Step,
Action used
and what
appears in the
Narrative
Denotes Step,
Action used
and what
appears in the
Narrative – the
email address
into the email
object.
Defines Step
Logging
System Action:
Step Begin
Test Action:
Checkbox > Set
On
System Action:
Step Logging
System Action:
Step Begin
1/19/2015
Denotes Step,
Action used
and what
appears in the
Narrative –
setting
checkbox “on”
tmxAction = "Input"
tmxNarrative = "Input 'Bob' into the object 'Name'."
tmxValue = DataPrep("Bob"
)
set tmxObj = Browser("IE").Page("testpage").WebEdit("Name")
tmxOName = "Name"
If tmxObj.exist(0) then
tmxObj.set tmxValue
else
tmxLogComment = "Can't find object '" & tmxOName & "'"
tmxStatus = "fail"
End If
tmxStatus = TMXRunLog ()
if tmxStatus = "fail" then
tmxMain = false
Exit Function
End If
'--------------------------------------------------------------------------------------------------------------tmxStep = "2"
tmxAction = "Input"
tmxNarrative = "Input 'bobsmith@critical-logic.com' into the object 'Email'."
tmxValue = DataPrep("bobsmith@critical-logic.com"
)
set tmxObj = Browser("IE").Page("testpage").WebEdit("Email")
tmxOName = "Email"
If tmxObj.exist(0) then
tmxObj.set tmxValue
else
tmxLogComment = "Can't find object '" & tmxOName & "'"
tmxStatus = "fail"
End If
tmxStatus = TMXRunLog ()
if tmxStatus = "fail" then
tmxMain = false
Exit Function
End If
'--------------------------------------------------------------------------------------------------------------tmxStep = "3"
tmxAction = "Set ON"
tmxNarrative = "Set the Checkbox 'New Customer' ON."
tmxValue = "ON"
set tmxObj = Browser("IE").Page("testpage").WebCheckBox("New Customer")
tmxOName = "New Customer"
If tmxObj.exist(0) then
tmxObj.set tmxValue
else
tmxLogComment = "Can't find object '" & tmxOName & "'"
tmxStatus = "fail"
End If
tmxStatus = TMXRunLog ()
if tmxStatus = "fail" then
tmxMain = false
Exit Function
End If
'--------------------------------------------------------------------------------------------------------------tmxStep = "4"
tmxAction = "Push"
Page 154
tmxNarrative = "Push the 'Reset Form' button."
tmxValue = "ON"
set tmxObj = Browser("IE").Page("testpage").WebButton("Reset Form")
tmxOName = "Reset Form"
Test Action:
Edit > Input
If tmxObj.exist(0) then
tmxObj.Click
else
tmxLogComment = "Can't find object '" & tmxOName & "'"
tmxStatus = "fail"
End If
tmxStatus = TMXRunLog ()
if tmxStatus = "fail" then
tmxMain = false
Exit Function
End If
'--------------------------------------------------------------------------------------------------------------tmxStep = "5"
tmxAction = "Verify"
tmxNarrative = "Check that '' appears in the edit box 'Name'."
expectedValue = ""
set tmxObj = Browser("IE").Page("testpage").WebEdit("Name")
tmxOName = "Name"
If tmxObj.exist(0) then
actualValue
=
Browser("IE").Page("testpage").WebEdit("Name").GetROProperty("Value")
If actualValue <> expectedValue Then
tmxStatus = "fail"
tmxLogComment = "Expected value '" & expectedValue & "' NOT
found, actual value was '" & actualValue & "'"
End If
else
tmxLogComment = "Can't find object '" & tmxOName & "'"
tmxStatus = "fail"
End If
tmxStatus = TMXRunLog ()
if tmxStatus = "fail" then
tmxMain = false
Exit Function
End If
'--------------------------------------------------------------------------------------------------------------tmxStep = "6"
tmxAction = "Verify"
tmxNarrative = "Check that '' appears in the edit box 'Email'."
expectedValue = ""
set tmxObj = Browser("IE").Page("testpage").WebEdit("Email")
tmxOName = "Email"
If tmxObj.exist(0) then
actualValue
=
Browser("IE").Page("testpage").WebEdit("Email").GetROProperty("Value")
If actualValue <> expectedValue Then
tmxStatus = "fail"
tmxLogComment = "Expected value '" & expectedValue & "' NOT
found, actual value was '" & actualValue & "'"
End If
else
tmxLogComment = "Can't find object '" & tmxOName & "'"
1/19/2015
Page 155
tmxStatus = "fail"
End If
tmxStatus = TMXRunLog ()
if tmxStatus = "fail" then
tmxMain = false
Exit Function
End If
'--------------------------------------------------------------------------------------------------------------tmxStep = "7"
tmxAction = "Verify OFF"
tmxNarrative = "Verify that the checkbox 'New Customer' is set OFF. "
set tmxObj = Browser("IE").Page("testpage").WebCheckBox("New Customer")
tmxOName = "New Customer"
If tmxObj.exist(0) then
if tmxObj.GetRoProperty("checked") = 1 then
tmxlogComment = "'" & tmxOName & "' was not set OFF"
tmxStatus = "fail"
End If
else
tmxLogComment = "Can't find object '" & tmxOName & "'"
tmxStatus = "fail"
End If
tmxStatus = TMXRunLog ()
if tmxStatus = "fail" then
tmxMain = false
Exit Function
End If
'--------------------------------------------------------------------------------------------------------------tmxMain = true 'all step run
End Function
1/19/2015
Page 156
Anatomy of a TMX for TestPartner Script
Ideally, the test case will look something like the following when viewed
in the Tests Editor:
Figure 9-1 The Tests Editor view of Test 01 displays 7 steps that were created in Chapter 2.
To further check Test 01, go to the Tests Narrative folder in TMX and
compare the results to the narrative created when you completed the
test case in Chapter 2 (see section
The First Test).
Anatomy of a TestPartner Executable
The complete view of the executable script can be viewed under the
Executable folder in Tests. We’ll explore the Tests Executable segment
by segment to understand where each of the components is generated
by TMX, starting with the first line in the Executable:
The first identifies the test case by Test Name as it appears in the Tests
List, the author, and date the executable was last generated.
1/19/2015
Page 157
The next section begins with the “on error” statement. This segment
sets some of the basic error logging routines for the test.
Generated from the action “Begin Test”, you can view the source by
clicking on the Actions tab, and then expand the “System” Action Type.
There you should find an action entitled Test Begin. Click on the
Executable tab to display the code that you see in this section of the
complete test executable.
The section starting with “If Window” denotes the beginning of the
System Action: Change Window. Here, the test is defining the use of
the Internet page entitled “testpage” for the steps that follow and
designating the routine to use if the page is not found during execution
of the test.
The final part of the first segment defines the step logging for the
Change Window action.
Following this, the executable then starts with the first step of the test
case Test 01.
The first line of the step defines the action that has been defined by the
test case. In this case: Input. The executable code can be reviewed by
1/19/2015
Page 158
going to the Actions tab and selecting Input found under the Action
Type “Edit Box”.
The second line repeats the test step description. This can be reviewed
in the Test Narrative.
The third line of the step is the executable code found in the action
“Input”. This sets the GUI object name in the application and the data
that is to be used in the defined action. In this instance, the text “Bob” is
to be entered into the edit box “Name”.
The final line in this test step sets the run log action. This can be found
in the Step Logging action.
Since Step 2 uses an edit box like Step 1, it uses the same Input Edit
Box action. The description of the executable is the same except for the
description in line two refers to the data to be entered and the name of
the edit box is Email.
Step 3 of the test case involves a different action, setting a checkbox
value to “on”. As with the prior two steps, you can find the action
description under the Actions tab.
The first line indicates that this step involves the action Set On under
the action type “Checkbox”.
The line entitled “tmxStepDescription” provides the narrative description
for the test step.
The next segment describes the object name on the page and the
action to be performed. In this case “click” on.
The last line of the segment is the step logging.
1/19/2015
Page 159
Step 4 describes pushing the push-button entitled “Reset Form”. As with
the other steps, the first line describes the action to be performed and
defines the object.
The second line provides the narrative description of the step.
The third line provides defines the GUI object on the target page.
As with the other test steps, the final line of the segment provides for
the step logging.
Step 5 of the test case is a little more complicated in that its defined
action is to verify entry of a specific value in the edit box. In this case
the action being used (Verify) is found under the action type “EditBox”.
The test description in the second line indicates that the step is to check
that there is no data in the Name editbox.
The third line contains the GUI definition of the object; in this case we’re
looking for the NameEditBox located on the testpage. The executable
for the action contains a check to determine if the anticipated value is
found.
The final step is the step logging.
The last step, step 6, is similar to the prior step except that it uses the
Verify OFF action instead of just Verify.
1/19/2015
Page 160
As the description in the second line indicates the test step is looking to
verify the New Customer checkbox is set to OFF.
The action definition in the third line provides the object and action
definitions as well as starting the if-statement for the error.
The last statement provides the step logging.
The final segment of the executable script contains the action Test End
found under the System Action Types.
This contains two sections that define the error handling and logging for
the entire test case.
1/19/2015
Page 161
10
Chapter
10. Help & Troubleshooting
Help
In order to provide the quickest and most effective means of getting you up to
speed and working with TMX, the Critical Logic team has created several
different ways to offer help and assistance.
The TMX User Guide is easily accessed from the TMX Help Tab by selecting
the User Guide button.
In addition, Critical Logic is frequently adding new TMX support videos on our
website. Please check www.critical-logic.com for the latest titles.
Expand/Collapse All (+/-)
Within the Help tab, the Expand All and Collapse All function will display the
entire Icon Tree when selected.
User Guide
This will open the online PDF version of the latest TMX User Guide.
About
The About button displays the current TMX version and database type.
Should your version appear old, please check with your system administrator
or www.Critical-Logic.com to obtain the most recent version of the
application.
Database
The Database button displays the database location, path and type of the
database currently in use by TMX.
Password
This button will open a Change Password window for the currently logged in
user to change their password.
Exit
The Exit command allows you to exit TMX entirely or log back in with a
different User ID or to a different database.
1/19/2015
Page 163
Troubleshooting in TMX
Record Locking
TMX has been designed as a multi-user application. As such, certain
precautions have been taken to prevent accidental conflicts with records
being used or modified. For example, to prevent two users from concurrently
updating or modifying the same test case or object, a lock is placed on the
test case or object by the first user who requests that object.
Reasons for Improper Locks:



Disk Drive Full or
inaccessible
Network connectivity
problem
Workstation shut down
while TMX was
running
Should another user attempt to update that
object, TMX will respond with an error
message advising that the record has been
locked and the user name of the person
owning that object.
Occasionally, due to certain conditions, a lock
may be inappropriately set that will prevent
others from updating a record or object.
To clear the locks and continue working, you must have Admin level
authority.
To clear all locks:
1. Verify that the user named in the error message does not have the
target object or script in use on their TMX.
2. Go to the Admin > Tools tab and select Clear Locks.
3. You will receive the following message:
4. Select “Yes” to clear all system locks.
5. Resume work on the target object or script.
1/19/2015
Page 164
Tests List Not Displaying
Occasionally after logging into TMX you may experience a blank Tests List.
This is usually immediately after downloading and installing a new version of
TMX and is typically the result of an old version of a filter being applied
against a new database structure.
An error message may be produced indicating that an item cannot be found,
such as:
To correct the problem you’ll need to clear the current filter.
To Clear Existing Filter:
1. Select Exit from any view – selecting ‘Yes’ to log back into TMX.
2. On the login window make sure the Show Test Filter First check-box
is marked.
3. Log-in to TMX as normal.
4. Rather than displaying the Tests List, the Sort/Filter window will be
displayed when you complete the logon.
1/19/2015
Page 165
5. Press the Clear Filter button in the Filter section to clear the current
filter values.
6. Press the Apply and Close button to complete the correction and
return to the Tests List view.
Test List:
 Organize your Tests List: To organize your test list utilize the filter
feature and folders. You can organize your tests by such groupings as
requirements and/or test author.


1/19/2015
Can't find a test in your test list? Be sure that your filter is not on. The
green icon next to the filter tests button indicates whether the filter is
active.
Test Editor:
Inserting a Test Step: To add a test step between existing steps,
highlight the step above where you would like to insert a test step and
select add step.
Page 166

Notations: To clarify difficult to understand test steps, add a note with
additional details. This note will appear in the test narrative, and will not
affect the test executable.

Copy & Paste: To be sure the correct step or steps are being copied;
note the TMX status bar (bottom bar). The status bar will indicate what is
in the clipboard.

Current Generation: To be sure a test is being generated, note the TMX
status bar. The status bar will indicate when a test is being generated.
Objects:
 Naming Conventions: To help with tester understanding intuitively name
your objects and windows.

Impact Analysis: To identify the impact of an application change, use the
usage feature to examine how many tests an object is used in.

Impact Analysis - Objects Value: To change the arguments used by an
object use the object value feature. This will allow you to globally change
the arguments for a particular object. For instance if a logon id is no
longer valid, you can use this feature to input the new logon id without
editing every test.

Avoid Duplicate Objects: To avoid duplicating objects, use the common
objects feature. This feature will allow for easier maintenance of objects
that are multiple windows.

Unused Objects: To avoid confusing test builders delete objects that are
not used (or not planned to be used) in tests.
Actions:
 Unused Actions: To avoid test builder confusion set Unused Actions to
Inactive.

Naming Conventions: To help with testers’ understanding intuitively
name your actions.

Pre-Testing: To avoid problems running tests, be sure to test your
actions before putting the actions into production.
Maintenance:
 To unlock a test use the Admin feature clear locks.
1/19/2015
Page 167

To uncover hidden objects, or reset your TMX display, use the reset
display feature on the admin tab.

To avoid losing too much data frequently backup your database.

To accommodate a major functional change or new release, use the new
release function on the Admin tab. This feature will archive a copy of your
objects, tests, and actions.
Running Tests:
 To avoid problems with running test sets, run your tests before adding
them to your regression suites.
Appendix B: Special Note on Windows
Appearance Settings
TMX is designed to be viewed with the default Windows appearance settings.
Adjusting the Windows appearance settings to anything other than the default
may result in an abnormal display of TMX.
If you experience an abnormal display of the contents in TMX, you may need
to reset your Windows to the default appearance settings. This can be done
by opening the Control Panel and clicking on the “Appearance and
Personalization” menu item (Category view), then clicking on the “Make text
and other times larger or smaller” option under the Display category. Select
the “Smaller – 100% (default)” option and click Apply:
1/19/2015
Page 168
1/19/2015
Page 169
i
Index
Index
A
B
Action Code Editor ........................ 121
Action ........................................ 123
Argument Popup ....................... 122
Arguments ................................. 124
Icon .................................... 122, 123
Last Change .............................. 124
Message Box ............................. 123
Type........................................... 123
Action Is Inactive ........................... 123
Actions ........................................... 118
Action Type ................................. 31
Actions Tree .............................. 119
Managing Actions ........................ 31
Actions Tree
Action Code Editor .................... 121
Action Types .............................. 119
Delete Action ............................. 128
Edit Action ................................. 121
Import Action ............................. 128
Paste Action .............................. 121
Rename Action .......................... 128
Type........................................... 123
Actions Usage ............................... 129
Actions Value ................................ 132
Replace ..................................... 132
Add Set ............................................ 86
Add Step – Add Object .................... 67
Add User ....................................... 137
Admin Functions ............................ 136
Add User ................................... 137
Backup ...................................... 138
Clear Locks ............................... 141
Clear Profile ............................... 142
Delete User ............................... 138
Edit User .................................... 137
New Release ............................. 139
Reset Display ............................ 141
Arguments ..................................... 124
Backup .......................................... 138
Batch Sets ....................................... 90
C
call_test ........................................... 63
Child Objec .................................... 111
Clear Locks ................................... 141
Clear Profile ................................... 142
Color Tag ......................................... 56
Command Buttons ........................ 28
Copy
Sets ............................................. 87
D
Data Type ........................................ 62
Delete
Object ........................................ 107
Set Item ....................................... 96
Delete Action ................................. 128
Delete Set ........................................ 88
Delete Test ...................................... 56
Delete User ................................... 138
Demo version of TMX...................... 11
E
Edit Action ..................................... 121
Edit User ........................................ 137
Exit.... 44, 53, 71, 82, 90, 99, 101, 108,
114, 117, 129, 131, 133, 144, 149,
163
Expert Action .......................... 60, 123
Export
Exporting Sets Descriptions ........ 90
External Data ................................... 61
data source .................................. 62
Data Type .................................... 62
F
field length boundary testing ........... 68
Filter Tests ....................................... 41
Folders ........................................... 28
G
Generate Logging Code ................ 124
Generate Set ................................... 90
GUI Map .......................................... 26
P
Print .. 52, 90, 100, 110, 114, 117, 131,
163
Printing
Sets Description .......................... 90
Process
Add .............................................. 61
Properties ................................ 29, 145
Add Property ............................. 146
Delete Property ......................... 148
Edit Property.............................. 148
R
Import Action ................................. 128
Installing TMX .................................... 5
Installing TMX XE "Installing TMX"
Test Kit .......................................... 5
Record Locking ............................. 164
Refresh ..... 52, 91, 110, 114, 117, 129,
131
Rename Set .............................. 89, 90
Reset Display ................................ 141
Right Mouse Button Menu ............... 44
L
S
Logging In ........................................ 10
Save ................................................ 58
Sets ................................................. 29
Add .............................................. 86
Add Test Item .............................. 93
Batch Sets ................................... 90
Copy ............................................ 87
Delete Set .................................... 88
Executable ................................. 101
Export Narrative .......................... 98
Generate ..................................... 98
Generate Set ............................... 90
Move Down ................................. 98
Move Up ...................................... 97
On Error ....................................... 97
Rename ................................. 89, 90
Skip Item ..................................... 97
Sets Editor ....................................... 92
Add Set Item ................................ 95
Cancel ......................................... 95
Item Detail .................................. See
Shared Data .................................... 68
Status Bar ........................................ 28
System Requirements ....................... 4
I
N
Narratives
Tests ............................................ 81
New Release ................................. 139
O
Object
Add Child Object ....................... 111
Delete Object ............................. 107
Edit Object ................................. 105
Object Class .................................. 106
Object Tree...................................... 17
Objects .................................... 30, 102
Application Objects...................... 31
Common Objects......................... 31
Generate ........... 113, 114, 116, 130
Object Usage ............................. 113
Objects Tree .............................. 104
Objects Values .............................. 115
Replace ..................................... 116
Organizing Tests ..................... See Sets
T
Tabs ................................................ 28
Test
Add Note ..................................... 67
1/19/2015
Page 171
Continue On Eror ........................ 60
Edit Step ...................................... 68
Export Narrative .......................... 82
Generate ..................................... 71
Shared Data ................................ 68
Skip Step ..................................... 60
Test Step Editor .. 17, 19, 21, 22, 59,
60, 68, 70
Test Properties
Clear Property ............................. 75
Tests
Add Step ...................................... 58
Add Test ...................................... 33
Delete .......................................... 38
Delete Test .................................. 56
Edit .............................................. 35
Edit Recent .................................. 35
Editing ......................................... 33
Executable
Anatomy of an Executable Script
........................................... 150
Executable ................................... 83
Filter............................................. 41
Filter by Name ............................. 43
Filter by Property ......................... 43
Import Test Function ................... 36
Narratives .................................... 81
Rename Test ............................... 38
Sorting ......................................... 42
Tests Editor 28, 57, 67, 68, 69, 70, 83,
113, 157
Copy Steps .................................. 78
Cut Steps ..................................... 77
1/19/2015
Delete Steps ................................ 78
Highlight Steps ............................ 78
Show Action Definition ................ 80
Show Object ................................ 80
Skip Step ..................................... 79
Tests List .... 14, 15, 28, 33, 34, 35, 38,
41, 45, 46, 48, 52, 54, 55, 57, 83,
94, 95, 145, 157, 166
Exit............................................... 44
Where Used ................................ 56
TMX
Architecture ................................. 26
Work Area ................................... 11
TMX Support Center ......................... 9
TP
TMX work area ............................. 27
Troubleshooting ............................. 164
Can't find a test.......................... 166
Impact Analysis ......................... 167
Inserting a Test Step ................. 166
Record Locking ......................... 164
Tests List Not Displaying ........... 165
Tutorial .............................................. 9
U
UnRegister TMX ............................ 143
W
Where Used .................................... 56
Page 172
Download PDF
Similar pages
Infra red control
High-Speed Testing. High-Speed Solutions - TRS
user manual
TMX Card - GlobalStreams
TallyMan MultiController Setup
TMX U517 - TEMEXPRESS
17" LCD High-Resolution Touch Screen Display
TMX W353