AUTOMATED TEST DESIGNER

Tutorial
Automated Test Designer
Tutorial
Version V6.0
ATD - Tutorial V6.0

© Copyright 2006 - AtYourSide Consulting.

All rights reserved. All text and figures included in this publication, are the sole property of
AtYourSide Consulting, or the proper third party owners, and protected under international
copyright, patent, trademark and trade secret laws. No portion of this publication may be
copied, reproduced, or used in any way without the express advance written permission of
AtYourSide Consulting. Information in this document is subject to change without notice and
does not represent a commitment on the part of AtYourSide Consulting

AtYourSide Consulting may have copyrights, patents or pending applications for the same
covering subject matter in this document. The furnishing of this document does not give you
any license, whether express or implied, to any copyright or patent of AtYourSide Consulting
For information concerning licenses, please refer to your written license agreement from
AtYourSide Consulting

This document also contains registered trademarks, trademarks, and service marks that are
owned by their respective companies or organizations. AtYourSide Consulting disclaims any
responsibility for specifying which marks are owned by which companies or organizations.

If you have any comments or suggestions regarding this document, please visit our website
at http://www.atyoursideconsulting.com or send e–mail to
support@atyoursideconsulting.com.

AtYourSide Consulting
R. Lagares d’El Rei, nº21C-1F
1700-268 Lisbon – Portugal
Table of contents

Introduction ........................................................................................................... ii
Overview ........................................................................................................... ii
Using this tutorial .............................................................................................. iii
Typographical conventions ............................................................................... iv
Lesson 1: Introducing ATD ................................................................................... 2
Overview ........................................................................................................... 2
The benefits of requirement based testing ........................................................ 3
Exploring ATD user interface............................................................................. 4
Lesson 2: Specifying Requirements...................................................................... 8
Overview ........................................................................................................... 8
Testing a login dialog box .................................................................................. 9
Creating a new project .................................................................................... 10
Creating a new requirement ............................................................................ 10
Translating requirement specifications from natural language to formal logic . 14
Creating nodes ................................................................................................ 15
Starting test case generation ........................................................................... 22
Group and sub(mit) group nodes ..................................................................... 25
Node associations ........................................................................................... 33
Termination nodes ........................................................................................... 45
Using n-wise / exhaustive test case generation methods ................................ 54
Lesson 3: Reporting ............................................................................................ 57
Overview ......................................................................................................... 57
Creating a test cases report ............................................................................ 58
Lesson 4: Specifying test data ............................................................................ 61
Overview ......................................................................................................... 61
Specifying test data ......................................................................................... 62
Starting test data generation ........................................................................... 79
Lesson 5: Test automation .................................................................................. 82
Overview ......................................................................................................... 82
Mapping test automation information .............................................................. 83
Generating automatic test scripts .................................................................... 85
Lesson 6: Export / Import .................................................................................... 86
Overview ......................................................................................................... 86
Exporting a requirement information ............................................................... 87

i
ATD - Tutorial V6.0

Introduction

Overview
Welcome to Automated Test Designer (ATD), tutorial. This guide teaches you the
basics of requirement based testing using ATD.
This tutorial will familiarize you with the process of translating requirement
specifications written in natural language to logical formal language using ATD
graphical Cause / Effect definitions tree. After specified the requirements and
generated all associated test cases you still need to execute one of the hardest
tasks before start running the generated test suite. You need to identify and
create / extract all the data needed to run the different test cases. All those tasks
will be described here.
Not all ATD functionalities will be covered here. Please read ATD – User Guide
for a complete reference.

ii
 ATD - Tutorial V6.0

Using this tutorial

The tutorial is divided in 4 short lessons.
After completing this tutorial you, you can apply the skills you learned to your own
environment.
You can find in the list below the contents of the different chapters of this guide:
Lesson 1, Introducing ATD takes you on a short tour of the ATD user interface.
Lesson 2, Specifying requirements provides an overview of the process of
creating the cause / effect definitions tree. This is the way to translate the
functional requirements into formal language.
Lesson 3, Reporting teaches how to create reports in MS Word format.
Lesson 4, Specifying test data provides you with the knowledge on how to
specify test data needed to execute all your test cases.
Lesson 5, Test automation explains how to map the test automation information
and shows how to generate automatic scripts.
Lesson 6, Export / Import shows how to export / import requirements
information.

iii
ATD - Tutorial V6.0

Typographical conventions
This tutorial uses the following typographical convention:

1, 2, 3
Numbers indicate steps in a procedure.

>
The greater than sign separates menu levels (for example, File > Open).

Bold
Bold text indicates function names and text that should be typed literally.

iv
ATD - Tutorial V6.0

Lesson 1: Introducing ATD

Overview
This lesson:

Describes the benefits of requirement based testing

Takes you on a short tour of the ATD user interface

2
 ATD - Tutorial V6.0

The benefits of requirement based testing

If you have ever created an effective test plan manually, you are aware of its
drawbacks.
One of the most demanding tasks of the whole quality assurance process is the
elaboration of an effective test plan, that is, complete and not redundant. How do
we know that we already created all of the necessary test cases to cover the
functional rules of our application?
With ATD, through the translation of the functional rules of the requirements,
usually specified in natural language, for a formal language as the logic, we got
to generate the smallest number of tests than they guarantee a covering of 100%
of all requirement rules.
Doing this manually is time consuming and tedious, requiring a heavy investment
in human resources. This leaves you wondering whether serious bugs have gone
undetected.
Worse still, due to time impositions, it becomes almost impossible to get to test
the application before the software is released.
Using ATD we can begin to develop all test cases, as soon as the functional
requirements are defined. At the same time while translating the functional rules
of the requirement you are also verifying its completeness and checking for
ambiguities (doing the thing right). ATD gives you the power to get a more
efficient process. ATD supports proven methods for reducing and prioritizing the
number of test cases while also achieving high requirements coverage.
After specified the requirements and generated all associated test cases you still
need to execute one of the hardest tasks before start running the generated test
suite. You need to identify and create / extract all the data needed to run the
different test cases. This is a very complex and very time consuming task. ATD
can now help you doing this. The new ATD Test Data Generator (TDG) module
allows you to identify your functional test data.
After test cases generation you can easily execute them against the application
under test in order to validate the application functionality (doing the right thing).
This execution process can be manual or automated. The new ATD Test Script
Generator (TSG) module allows you to automatically generate test scripts for the
main automation tool in the market, such as Mercury’s WinRunner, Mercury’s
QuickTest, Compuware’s TestPartner or IBM Rational Robot.

3
ATD - Tutorial V6.0

Exploring ATD user interface

Before you begin generating test cases, you should familiarize yourself with the
ATD main application window.

Starting ATD Server:

Do not forget ATD is a client / server application. Before you can launch the client
component you must have the ATD Server running elsewhere.
1. Choose Start > Programs > ATD – Automated Test Designer > ATD
Server. The ATD Server console opens. After a successfully start up
you will see the message “ATD Server has started successfully” in the
server console.

Starting ATD Client:

1. Choose Start > Programs > ATD – Automated Test Designer > ATD
Client. After the splash screen the ATD’s Login dialog box opens.

4
 ATD - Tutorial V6.0

2. Enter a valid Host Name. The machine name where ATD Server
component is running.
3. Enter a valid username and password in the correspondent fields. By
default ATD creates a user name “admin” with a blank password during
the installation process. If these data does not work, please ask your
ATD administrator for this information.
4. Click on the OK push button. The Select Working Project dialog opens.

Note: This dialog box only shows the projects you have access to. To manage all
project setting please look at the Administration guide chapter 4: ATD Project
Administration. This chapter teaches you how to perform project, users, groups
and security profiles management.
By default the Select Working Project dialog shows the last project selection. If
this is your first time entering in the system, this dialog will show the first project
in the list of available projects.

5. Choose your project and click on the OK push button. The ATD main
application window opens.

Note: First time you enter the project the ATD main window appears empty even
if the project already contains requirements. If you have been working in a
specific requirement before, ATD will automatically open that specific
requirement.

5
ATD - Tutorial V6.0

1 2

1)
3 4

1) Menu bar. The commands on the menu are described in detail in

subsequent lessons. Note that you can also execute many
commands using softkeys. Softkeys are keyboard shortcuts for
carrying out menu commands.
2) Toolbar. Main functions can be accessed by the correspondent
button in the toolbar.
3) Project Requirements tree. Using this graphical tree you can easily
manage your requirements.
4) Cause / Effect Definitions tree. Using this graphical tree you will
create your requirement specification rules.
5) Requirement description area. You can use this area to specify in
natural language your requirement rules.
6) Generated test cases list. After the first test case generation you
can build a list of all generated test cases.

6
 ATD - Tutorial V6.0

Note: When you open ATD for the first time, the main application window will be
empty. After you create your first requirement, if you close ATD without closing
the requirement itself, when you log in again, ATD will automatically open the last
opened requirement.

Now that you are familiar with the ATD main application window, take a few
minutes to explore these window components before proceeding to the next
lesson.

7
ATD - Tutorial V6.0

Lesson 2: Specifying Requirements

Our goal during this tutorial is to create a complete test plan in order to validate
the ATD login dialog box.
We will start to analyze the requirement specifications and translate those
specifications from natural language to formal language.
Before you can start specifying requirements rules, you must start to create a
new requirement using ATD. Then you can start to translate the requirement
specification from natural language to formal language. This is done by
populating the Cause / Effect Definitions tree.
Using the Cause / Effect Definitions tree, the project team can analyze every
aspect of the requirements. Once requirements have been reviewed and all
errors and ambiguities are corrected, ATD uses an advanced and rigorous
Neural Network Optimization algorithm, in order to produce the minimum number
of test cases to certify 100% of requirement rules.

Overview
This lesson:

Explains how to analyze requirement specifications and look for
ambiguities.

Shows you how to create a new project.

Teaches you how to create a new requirement.

Explains how to specify requirement rules in ATD.

Shows you how to generate the requirement test cases.

8
 ATD - Tutorial V6.0

Testing a login dialog box

Before starting to create the logic, you need to analyze all requirement rules. The
requirement rules are described below:

Requirement Name: Enter system.

Description: The user must first fill all required fields and validate the information
by clicking on the OK push button. All that information is then sent to the server
and after a validation process the application main application window opens.
Otherwise it presents the user with the respective error message indicating that
some data is wrong.
Field validations:

The Host Name field is a required field

The User Name field is a required field.

The Password field has to be filled out in agreement with the
corresponding User Name value.

In order to log in the Host has to be running.
Push buttons functionality:

OK push button validates the data.

Cancel push button closes the Login dialog box.
Error messages:

Error Message : Hostname is NOT On-Line

Error Message : Hostname is mandatory

Error Message : Username or Password is incorrect

Error Message : Username is mandatory

9
ATD - Tutorial V6.0

Creating a new project

In order to specify requirement rules you need first to create a new project where
you will store all your requirements. ATD is organized in a hierarchy where the
Project represents the highest entity, the top of the hierarchy. Requirements are
stored in projects and generated test cases are linked to the respective
requirements.
You use ATD Project Administration utility to create and maintain projects, users,
groups and access permissions. Please look at the ATD Administration guide
Chapter 4: ATD Project Administration, in order to create a new project.

Creating a new requirement

1. Start ATD Client. If ATD Client is not already open, start it. If you are
not sure how to start ATD Client, please go back to lesson 1.
2. In the Select Working Project dialog choose the project you have just
created.
3. From the Project Requirements tree select the node where you wish to
create the new requirement. If it’s a new project there are no child
nodes (requirements) already.
4. Choose Requirements > Create. Alternatively you can choose to right
click on the Requirements tree and select Create from the context
menu. You can also use the Ctrl + N softkey.

10
 ATD - Tutorial V6.0

5. Enter “Enter System” for the requirement name in the appropriate

field.
6. Open the requirement by double clicking on it. Alternatively you can
choose to right click on the selected Requirements and select Open
from the context menu. The Cause / Effect Definitions tree opens
allowing you to complete all the requirement information.

11
ATD - Tutorial V6.0

7. Add the requirement title and description in the appropriate fields.

Enter “Login Simpler Sample” in the Title field.
Copy the requirement description to the Description field.
8. In the Category field choose User Interface + Business Logic.

12
 ATD - Tutorial V6.0

Now you are ready for starting creating the Cause / Effect Definitions tree. You
do this by creating nodes, which represents causes and related effects.

13
ATD - Tutorial V6.0

Translating requirement specifications from natural language to

formal logic
A test is made of causes and effects statements. A cause can be defined as an
Action or State that triggers a result. An effect is an expected result.
By analyzing the Enter System requirement description you can easily identify
causes and effects. Let’s start identifying the causes:

Causes

ID Type Positive/Negative Description

1 Action Positive Enter a hostname in the field "Hostname"

2 Action Positive Enter a Username in the field "Username"

3 Action Positive Enter a Correct password in the field "Password"

4 Action Positive Validate the information

5 State Positive The Hostname is On-Line

6 Action Positive Cancel the information

7 Action Negative Do NOT enter a hostname in the field "Hostname"

8 Action Negative Do NOT enter a username in the field "Username"

9 Action Negative Enter an Incorrect Password in the field

"Password"

10 State Negative The Hostname is NOT On-Line

Table 1: Causes

Now, combining different causes using the AND / OR logical operators, you can
find the corresponding effects:

Effects

Combination Type Description

1 AND 2 AND 3 AND 4 AND 5 Final Enter the application

7 AND 4 Error Error Message : Hostname is mandatory

14
 ATD - Tutorial V6.0

1 AND 8 AND 4 Error Error Message : Username is mandatory

1 AND 2 AND 9 AND 4 Error Error Message : Username or Password is

incorrect

1 AND 2 AND 3 AND 4 AND 10 Error Error Message : Hostname is NOT On-Line

ANY COMBINATION AND 6 Final Exit the login window

Table 2: Related Causes and corresponding final Effects

Doing this analysis we are trying to find any ambiguity and at the same time
checking for requirement completeness.
It is now time to start entering all this information into the ATD’s Cause / Effect
Definitions tree.

Creating nodes
1. Select the parent node. At this time the parent node is the requirement
name itself. Optionally you can close the Project tree view.
2. Choose Nodes > Create. Alternatively you can choose to right click on
the Cause / Effect definitions tree and select Create from the context
menu. You can also use the Ctrl + K softkey.

15
ATD - Tutorial V6.0

3. Enter a logical name that identifies this node, for example “Enter
HostName”.
4. In the right pane from the Node Type combo box select Cause.
5. Specify in the Action field the text you wish to appear for the
corresponding node. Copy the corresponding text found in the Causes
table from the previous exercise.

16
 ATD - Tutorial V6.0

6. Create another cause under the previous one. Call it “Enter User
Name”. Once again, use the text from the previous exercise for the
Action field.

17
ATD - Tutorial V6.0

7. Continue to add causes as described in the Table 2. After doing that

you should have the following definition:

18
 ATD - Tutorial V6.0

8. Now let’s add the effect node. Create a new effect node under the last
cause.
9. Enter a logical name that identifies this node, for example “Enter
Application”.
10. In the right pane from the Node Type combo box select Effect.
11. Specify in the Result field the text you wish to appear for the
corresponding effect node. Copy the corresponding text found in the
Table 2.

19
ATD - Tutorial V6.0

What have we done so far?

We have started to add the logic to the ATD’s Cause / Effect Definitions tree. We
have done that for the first related causes.
Let’s continue adding all the necessary logic definitions. Now we can start to
think on the second line of Table 2. On that row we want to relate cause 7 AND
4. That means if you enter an invalid Host Name and try to validate the
information, you will receive an error message.

12. Create the new nodes under the root node in order to specify this
related rule. At the end you should have:

20
 ATD - Tutorial V6.0

With this definition we are specifying two different paths. One for the final effect
message: “Enter the application” and the other to the error message: “Hostname
is mandatory”.
Now, add remaining identified rules described in Table 2 to ATD.

Note: Creating a node under another node means that you are using an AND
logical operator. If you pretend to use an OR logical operator create a node at the
same tree level.

21
ATD - Tutorial V6.0

At the end you should have something similar to this:

Now we are ready to generate all test cases related to this specific requirement.

Starting test case generation

After completing the requirement translation from natural language to formal
language using the Cause / Effect Definitions tree, you are able to start the test
case generation. ATD will produce the minimum number of test cases in order to
validate your requirement rules.
1. Select Nodes > Start Test Case Generation. Alternatively you can
use the F5 softkey.

During the Test Generation phase, ATD will show the generation progress in the
main window status bar. When this process finish, the Test Generation dialog
box opens informing you the number of tests cases generated.

22
 ATD - Tutorial V6.0

After compilation you can see that the nodes have turned green. If you make a
change in a node you will see that the corresponding node color will change back
to yellow. This indicates that there is no compilation after that change.

2. Click on the OK push button. All generated tests were stored in the
repository.

After a successfully test case generation you can start to view the final test cases
generated in natural language using a tabular format. This standard output shows
the steps and expected results of each test case.
ATD generates the minimum number of test cases in order to certify 100% of
requirement rules. However, the number of test cases generated may still be very
large especially for complex requirements. ATD provides the ability to select the
number of Test Cases that fit your testing strategy using the Test Search
functionality. This functionality allows the control of the number of Test Cases
used in the testing process according to two main parameters: Number of Test
and Risk Coverage. This approach may significantly reduce the number of test
cases to be manually or automatically executed with the minimum impact on the
final quality.
All generated test cases can be viewed on the Test Cases tree in the Test Cases
tab. In order to se them you must:
3. Click on the Test Cases tab. In the left frame you can see an empty
Test Cases tree. First, you will have to add the generated test cases
you wish based on your criteria.
4. Right click on the Test Cases tree root node (requirement name) and
choose Select Tests from the context menu. The Select Tests –
Search Criteria’s window opens:

23
ATD - Tutorial V6.0

Let’s start to add all generated test cases for this particular requirement.
5. Select Get all Test Cases from the list box. The search results appear
instantaneously on the Select Tests - Search Criteria window.

6. Click on the Add All push button to add all the returned test cases to
the Test Cases tree.

The selected test cases are added to the Test Cases tree. ATD gives a prefix
number to all the test cases. This number represents the test case unique
identifier.

24
 ATD - Tutorial V6.0

For this particular requirement, ATD has produced only 9 test cases that certify
100% of the requirement rules.

7. Select the test case you wish to analyze. In the right pane you can see
the correspondent standard report in a tabular format.
8. You can scroll up / down to navigate through the generated output of
each test case.

Group and sub(mit) group nodes

Groups and Sub(mit) Group nodes allow you to create a set of nodes and reuse
them. You can reuse Groups in the same requirement or even among different
requirements. Groups are composed by a set of causes and/or effects. All nodes
inside a Group are not included in test case generation if a Submit Group node
does not reference them. A Submit Group node allows the execution of all
member nodes of a Group.
We will now modify the previous requirement definitions in order to use Group
and Sub(mit) Group nodes.

25
ATD - Tutorial V6.0

1. Create a new requirement and call it “Enter System 2”.

2. Create a Group node and call it “HOSTNAME”. Next, under that node,
create the two causes related with the Host Name field. Your Cause /
Effect Definitions tree should look like this:

3. Do the same for the other causes. Create the following groups:
“USERNAME”, “PASSWORD”, “ACTIONS” and “HOST”. Each of
these groups will contain nodes related to nodes inside them. You
should do something like this:

26
 ATD - Tutorial V6.0

Now, we must reference these Groups by creating a test case sequence. You do
that by creating Submit Group nodes.

4. Create a new Submit Group node under the root node and give it “SG
HOSTNAME” as name.
5. Link it to an existing Group. In this particular case, link it to the
“HOSTNAME” Group:
a. In the right pane select from the Type dropdown list the Submit
Group node type.
b. Link to a requirement. By default ATD links to the same
requirement you are working on.
c. Link to an existing Group:

d. Click on the push button next to the Group field. The Select
Group dialog box opens.
e. Select the HOSTNAME group from the list.
f. Click on the OK push button. The selected Group name appears
in the corresponding field.

27
ATD - Tutorial V6.0

6. Create the remaining Submit Group nodes, each one linked to the
related Group. In this case as we want to create a sequence like in the
previous exercise, we will create each Submit Group under its parent
Submit Group.

At the end you should have your Cause / Effect Definitions tree just like that:

28
 ATD - Tutorial V6.0

ATD will generate the following sequence: It will start to use all nodes from the
HOSTNAME group AND then from USERNAME group, and so on.
At this point, we need to include the corresponding final effects. We cannot forget
that a cause or a group of causes must have at least one corresponding effect.

29
ATD - Tutorial V6.0

If you now try to generate the test cases you will get errors:

During the test case generation process, ATD validates all formal rules you have
specified in the cause / effect definitions tree.
In case you have committed an error, ATD stops the compilation process and
displays the related error messages in the main window status bar.
For each node where an error was identified, the corresponding icon node color
will change to red. Select the node and analyze the error message. ATD
identified a group of causes with no associated effects.

7. Create the final effects identified in table 2. All effect nodes will be
created under the last Submit Group node. All of them at the same
level. Your Cause / Effect Definitions tree should look like this:

30
 ATD - Tutorial V6.0

8. Generate the test cases again. As you can see, ATD generated 32 test
cases instead of 9 as in the previous exercise.

9. Analyze the produced test cases. Click on the Test Cases tab.
10. Right click on the Test Cases tree root node and choose Select Tests
from the context menu. The Select Tests – Search Criteria’s window
opens.

31
ATD - Tutorial V6.0

11. Select Get all Test Cases from the list box. The search results appear
instantaneously on the Select Tests - Search Criteria window.

12. Click on the Add All push button to add all the returned test cases to
the Test Cases tree.
13. Back in the Test Cases tree, select the first test from the list.

32
 ATD - Tutorial V6.0

As you can see ATD is showing all the final effects for every test case. This is
happening because we did not tell ATD how to link the effects with the causes.
For example, test case 1 should have just one final effect, which is “Enter the
application”.

Node associations
To correct this situation, we need to use Node Associations. You define node
associations when you wish to define condition rules for a particular node to be
included or not in a test case. For this particular case the final effect “Enter the
application” should appear only if there are no error messages or if the user does
not choose to click on the cancel push button.
1. Create a node association for effect node “Error Message: Hostname
is mandatory”. Click on the Cause / Effect Definitions tree and select
the correspondent effect node named Error Message 1. In the right
pane select the Association tab. You will see the Node Associations
tree.

33
ATD - Tutorial V6.0

Using this pane you will create the necessary conditions for this particular node
to appear in the final generated test case.
2. To start, right click on the Node Associations tree root node and
choose Add Node from the context menu. The Select Associated Node
dialog box opens.

3. Fill in all the information you need in order to complete the association.

4. Select the cause node “NOT Enter HostName” and let the Apply
when Node does exist check box be checked.

34
 ATD - Tutorial V6.0

5. Click on the OK push button.

6. Now right click on the added Node Associations tree node and Repeat
steps 2 to 5 and add the “Validate” cause node. You should have the
following association:

After creating a node association, the selected node will appear in Bold. Bold
node names indicate that the specific node contains a Node Association.

7. Add the next node associations related to the “Error Message:

Username is mandatory” effect node named Error Message 2. This

35
ATD - Tutorial V6.0

effect, should only appear when “Error Message: Hostname is

mandatory” effect does not exist AND “Not Enter User Name” AND
“Validate” causes exists:
a) Repeat step 2 to 4 in order to achieve this goal.

b) Click on the OK push button. You have just inserted the “Error
Message: Hostname is mandatory” effect does not exist.
c) In the Node Association tree right click again and from the context
menu choose Add Node to insert the missing clauses: AND “Not
Enter User Name” AND “Validate”.
d) At the end the Node Association tree should look like this:

36
 ATD - Tutorial V6.0

8. Add the next node associations related to the “Error Message:

Username or Password is Incorrect” effect node named Error
message 3. This effect, should only appear when “Error Message:
Hostname is mandatory” effect does not exist AND “Error Message:
Username is mandatory” effect does not exist AND “Enter
Password NOK” AND “Validate” causes exists. Your Node
Association tree should look like this:

37
ATD - Tutorial V6.0

9. Add the next node associations related to the “Error Message:

Hostname is NOT On-Line“ node effect named Error message 4.
This effect, should only appear when “Error Message: Hostname is
mandatory” effect does not exist AND “Error Message: Username is
mandatory” effect does not exist AND “Error Message: Username or
Password is Incorrect” effect does not exist AND “Validate” AND
“HostName NOT OnLine” causes exists. Your Node Association tree
should look like this:

38
 ATD - Tutorial V6.0

10. Add the next node associations related to the “Enter Application“
effect. This effect, should only appear when “Error Message:
Hostname is mandatory” effect does not exist AND “Error Message:
Username is mandatory” effect does not exist AND “Error Message:
Username or Password is Incorrect” effect does not exist AND
“Error Message: HostName is NOT OnLine” effect does not exist”
AND “Validate” cause does exist. Your Node Association tree should
look like this:

39
ATD - Tutorial V6.0

11. Add the next node associations related to the “Exit Application”
effect. This effect should only appear when “Enter Application” effect
does not exist AND “Cancel” cause does exist. Your Node Association
tree should look like this:

40
 ATD - Tutorial V6.0

12. Generate test cases. Check the produced outcome.

As you can see, ATD had still generated 32 test cases instead of 9 as in the first
exercise. This is happening because we are still missing the definition of some
rules in the Cause/Effect tree. For instance, the “USERNAME” sub-group should
only be considered if the hostname is entered. Therefore, to introduce the
missing rules, we need to create a Node Association to Submit Group nodes SG-
USERNAME, SG-PASSWORD and SG-HOST.

13. Add a Node Association to “SG-USERNAME” node. Your Node

Association tree should look like this:

41
ATD - Tutorial V6.0

With this Node Association we are instructing ATD to use the nodes contained in
the “USERNAME” Group only when “Enter HostName” cause exists.

14. The “SG-PASSWORD” sub-group should only be considered if the

user name is entered. Add a Node Association to “SG-PASSWORD”
node. Your Node Association tree should look like this:

42
 ATD - Tutorial V6.0

With this Node Association we are instructing ATD to use the nodes contained in
the “PASSWORD” Group only when “Enter UserName” cause exists.

15. The “SG-HOST” sub-group should only be considered if the hostname,

user name and password were entered correctly followed by a system
validation. Add a Node Association to “SG-HOST” node. Your Node
Association tree should look like this:

43
ATD - Tutorial V6.0

With this Node Association we are instructing ATD to use the nodes contained in
the “HOST” Group only when this condition is true.

16. Generate test cases.

17. Check the produced outcome.

As you can see, ATD produced only 9 test cases. These test cases certify 100%
of the requirement rules.

44
 ATD - Tutorial V6.0

What have we done so far?

We have started using Group and Submit Group nodes in order to see how to
structure the requirement rules differently. After that we have defined node
associations to create the conditional rules for a particular node to be included or
not in a test case.

Termination nodes
Only an Effect node type can be a termination node. This means that a Test
Case will end once this node is found. This option is frequently used for error
messages effects.
We will now modify the previous requirement definitions in order to use
Termination Nodes.
1. Create a copy of the previous requirement. Select the Enter System 2
from the Project Requirements tree and choose Edit > Copy.
Alternatively you can choose to right click on the requirement and
select Copy from the context menu.
2. From the Project Requirements tree select the root node.

45
ATD - Tutorial V6.0

3. Choose Edit > Paste. Alternatively you can choose to right click on the
Requirements tree and select Paste from the context menu.
4. Next, ATD prompts you to see if you wish to include the generated
tests cases.

5. Click on the No push button. ATD will automatically rename your

requirement name to Copy of Enter System 2.
6. Rename your new requirement. Choose Requirements > Rename
and change its name to Enter System 3.
7. Open the new requirement. In the Project Requirements tree double
click on the Enter System 3 requirement.

We are now going to start modifying this requirement: change its title to “Login
Sample - Using Termination nodes sample”.

8. Let’s going to create a Submit Group node in the “HOSTNAME” Group

under “NOT Enter HostName” cause. Call it “SG ACTIONS-1”. Link it
to the “ACTIONS” Group. This will instruct ATD to execute the causes
created in ACTIONS Group.
9. Drag and drop the “Error Message: Hostname is mandatory” node
effect named Error Message 1 under “SG ACTIONS-1”.
10. Edit the corresponding node association: This effect should only
appear when “Validate” cause exists. At this point you should have
your Cause / Effect Definitions tree and Node Association tree as
following:

46
 ATD - Tutorial V6.0

11. Do the same for “USERNAME” and “PASSWORD” Groups. Create a

new Submit Group node under the negative cause, call it SG Actions
2, ...3, move the respective error message effect node under that node
and change the node association.

Your Cause / Effect Definitions tree should look like this:

47
ATD - Tutorial V6.0

12. Drag the “Exit Application” final effect to “ACTIONS” Sub Group
under “Cancel” cause.
13. Clear the Node Associations for that specific node. Right click on it and
select “Clear Association” from the context menu.

Your Cause / Effect Definitions tree should look like this:

48
 ATD - Tutorial V6.0

Now we must change the node associations for the last two effects, “Error
Message: Hostname is NOT On-Line” and “Enter application”.

14. The “Error Message: Hostname is NOT On-Line” effect node named
Error Message 4 should only appear when “Host Not Online” cause
does exist. Your Node Association tree should look like this:

49
ATD - Tutorial V6.0

15. The “Enter Application” effect should only appear when the previous
error does not exist AND the “Validate” cause does exist. Your Node
Association tree should look like this:

50
 ATD - Tutorial V6.0

16. Generate test cases. ATD will generate 15 test cases instead of 9.
Inspect the generated outcome. As you can see, some test cases are
not correct. Look at the 4th test.

51
ATD - Tutorial V6.0

After the first expected result ”Error Message: Username or Password is

Incorrect”, ATD continued generating other actions. This means we are missing
some important rules. We want to stop the generation every time ATD finds a
final effect. In order to achieve that goal, we have to define those nodes as
Termination Nodes.

17. Select the “Error Message 1” effect under the first Group and in the
right pane on the Detail tab check the Termination Node checkbox.

52
 ATD - Tutorial V6.0

18. Do the same for the other 3 final effects: “Error Message 2”, “Error
Message 3” and “Exit Application”.
19. Generate test cases.
20. Analyze the final generated test cases.

53
ATD - Tutorial V6.0

Now ATD generated only 9 test cases as we expected.

Using n-wise / exhaustive test case generation methods

As described before in this tutorial, ATD generates all tests for covering of 100%
of all requirement rules. Some times the number of tests generated can be
hundreds or even thousands. If you don’t have resources to execute all these
tests you can opt to generate a reduced number of test cases. This reduced
number of test cases is defined as the number of test cases needed to use at
least once all Causes and Effects defined in ATD Client. If you want to use this
method just select the N-Way option.

To generate the smallest number of test cases:

1. Choose Options > Preferences from the menu. The Preferences
dialog box opens:

54
 ATD - Tutorial V6.0

2. ATD uses the test case generation method defined previously in ATD
Project Administration utility. By default this parameter is set to
Exhaustive. Select the N-Way radio button.
3. Select 1 in the N-Way Testing Level. By default this value is set to
one. N-Way testing of level one emulates what is known as cyclomatic
complexity applied to test case generation. Mathematical analysis has
shown that cyclomatic complexity gives the exact number of test cases
needed to validate every requirement decision point (cause) that
produces a different outcome (effect). These generated test cases
does not guarantee all cause/effects combinations but ensures that
each cause node will be used at least once thus reducing the
generated test cases needed to validate your requirement rules. In
order to increase the number of test cases in a controlled manner, you
can increase the N-Way testing level. By using N-Way testing level of
2, we can guarantee that every pairs of causes will be tested at least
once. This is also called pairwise testing. ATD extends this concept in
the sense that you are able to use higher N-Way testing level, so you
can defined your test cases based on triple of Causes (N-Way of 3) or
any combination of n Causes (N-Way of n).
4. Click the OK push button to close the Preferences dialog.
5. In case you have test cases loaded in the Test Cases tab, ATD will
display the following information dialog:

55
ATD - Tutorial V6.0

6. Click on Yes push button in order to close the information dialog.

7. Generate test cases again. ATD will now generate 5 test cases instead
of 9. Inspect the generated outcome by adding all generated test cases
to the Test Cases tree.

What you see in the Test Cases tab is the minimum number of tests cases you
will need to execute. As you can see, the tests you will need to execute are test
1, 2, 5, 6, 8. These tests were filtered from the result of using the exhaustive
method.

What have we done so far?

We have defined the same requirement rules using a different approach.
Depending on the requirement rules complexity you can always choose the one
you like most.

56
 ATD - Tutorial V6.0

Lesson 3: Reporting

ATD is closely integrated with Portable Document Format (pdf), Web Page
(html), Microsoft Excel WorkBook (xls), Microsoft Word Rich Text Format (rtf),
Comma Separated Value (csv) and Extended Markup Language (XML) allowing
users to generate a suite of test case reports in any of these formats in an easy-
to-read format. Business analysts and project stakeholders can collaboratively
review the natural language test cases generated by ATD, enabling them to
identify and correct any requirement errors made earlier in the development
cycle.

Overview
This lesson:

Shows you how to create a test cases report in pdf format.

57
ATD - Tutorial V6.0

Creating a test cases report

After successfully generating all test cases to validate our requirement rules, let’s
go on to create a PDF well formatted document with all test case specifications.

To create a test case report:

1. Select Tools > Generate Report. The Document Generator dialog box
opens.

2. Just click on the Search push button. ATD will list all the available
requirements associated with this project. Choose “Enter System 3”
requirement.

Note: This list will only show only the updated and compiled requirements.

58
 ATD - Tutorial V6.0

3. Click on the Options push button. The Document Generator Options

dialog box opens.

4. Here you can choose to parameterize your report settings by choosing

a Report Title, Project Name, a Report Template, Report Format,
Report Scope and the Destination Folder. Just choose PDF as Report
Format.
5. Click on the Close push button.
6. Back in the Document Generator dialog window click on the Start
Generation push button. ATD starts the word report generation
process. ATD will show the word report generation process progress in
the Document Generator dialog box status bar. When finished ATD
displays an information message informing you of the result of the
report generation process.

59
ATD - Tutorial V6.0

7. Click on the OK push button to close the information dialog box. Now
you can open the generated document and distribute it to your testing
team.

60
 ATD - Tutorial V6.0

Lesson 4: Specifying test data

Our goal for this lesson is to provide you with the knowledge to specify test data
needed to execute all your test cases.
After specified the requirements and generated all associated test cases you still
need to execute one of the hardest tasks before start running the generated test
suite. You need to identify and create / extract all the data needed to run the
different test cases.
This is a very complex and very time consuming task. ATD can now help you
doing this. The new ATD Test Data Generator (TDG) module allows you to
identify your functional test data.
Using ATD TDG you can easily identify data to use as valid or invalid input for
causes as well data to use as output for effects in order to validate your expected
results. ATD is a requirement based testing tool. That means you identify the
data for the generated test cases based on your requirement needs.
Once test data has been specified, ATD generates all test data in order for you to
execute your test cases. From now on you can choose to run all your test cases
manually or let ATD generate all the respective automated test scripts for your
automated software quality tool.

Overview
This lesson:

Explains how to identify your requirements test data.

Teaches you how to generate the test data.

61
ATD - Tutorial V6.0

Specifying test data

In order to illustrate how to specify test data we’ll use the Enter System 3
requirement we’ve specified before on this tutorial. After finishing this chapter
we’ll have test data that allows us to execute all generated test cases. These
tests can then be manually or automatically executed.

To identify test data

During this process we’ll identify test data for all cause and effect requirement
nodes.
1. Open the “Enter System 3” requirement.
2. Expand the requirement Cause / Effect Definitions tree.
3. Select the first cause under HOSTNAME group node named “Enter
HostName”.
4. Click on the Data Identification tab on the right pane.

We’ve selected a cause node. A cause as you already know specifies an Action
or State that triggers a result. This action provides an input value to a text field.
Let’s define that by specifying a User Interaction – Set Value node category. This

62
 ATD - Tutorial V6.0

node category is used when you want to define data to use as input. That data
can be extracted from a database, expression result, or just defined as a single
constant.

5. Select User Interaction – Set Value from the Node Category combo
box. The Field Definition and Data Generation Strategy group boxes
get visible.

We must now fill the Field Definition group. We’ll create a User Interface and the
proper Logical Name that identifies the GUI object that will receive the input data.

6. Click on the push button next to the User Interface field. The User
Interface Selection dialog opens.

63
ATD - Tutorial V6.0

At this time we have no User Interfaces identified. We need first to set the
window context where the GUI Objects reside. Let’s create a User Interface
(window).

7. Click on the New push button. The User Interface Detail dialog opens.

8. In the Name field type the name you want to give to the window. Call it
“Login”. In the Description filed type “ATD Login window”.
9. Click on the OK push button. The User Interface Detail dialog closes.

It’s now time to define the GUI Object’s logical name associated to this cause
node.

10. Back on the ATD main window click on the push button next to the
Logical Name field. The Logical Name Selection dialog opens.

64
 ATD - Tutorial V6.0

11. Click on the New push button in order to create a new logical name.
The Logical Name Detail window opens.

As you can see the User Interface field is automatically filled with the previously
selected one.

12. In the Name field type “hostname”.

13. Now its time to specify the field format. Click on the push button
next to Field Format field. The Field Format Selection window opens.

65
ATD - Tutorial V6.0

14. Click on the New push button in order to create a new field format. The
Field Format Detail window opens.

15. In the Name field type “text”.

16. Set the scope for this field format type. Let’s select Public, e.g.
available to the project.
17. From the Field Type combo box select “String”.
18. From the Field GUI Type combo box select “EditField”.
19. In the Field Size field type “10”.
20. Click on the OK push button. The Field Format Detail window closes.
21. Click on the OK push button. The Logical Name Detail window closes.

It’s now time to define a data generation strategy for this node.

66
 ATD - Tutorial V6.0

22. Click on the push button next to the Strategy Name field. The
Strategy Name Selection dialog opens.

Let’s create a Single Constant strategy. This strategy type allows us to specify a
formula that produces the exact value we wish to use for this cause node.

23. Click on the New push button. The Strategy Detail dialog box opens.

24. In the Name field type “valid hostname”.

25. From the Strategy type combo box select Single Constant.
26. In the Formula field type “localhost” with the double quotes.

67
ATD - Tutorial V6.0

27. Click on the OK push button. The strategy is saved in your central
repository and can now be reused.

68
 ATD - Tutorial V6.0

Continuing with the test data identification process let’s go to the next node.

28. From the Cause / Effect Definitions tree select the next cause node
named “NOT Enter HostName”.

This node does not actually interact with any GUI Object. We do not need to
provide input or output data for it. For these cases we define a Cause Comment
– No Data Required node category which.

29. Select Cause Comment – No Data Required from the Node Category
combo box. Although this node category does not need an associated
data generation strategy you can optionally specify one providing the
exact comment you wish in order to complement this action.

Continuing with the test data identification process let’s go to the next node.

30. From the Cause / Effect Definitions tree select the effect node named
“Error Message 1”.

This effect result describes the appearance of an error message which will be
displayed in a message box. In order to specify this we’ll define a User Interface
Check – Alert Message node category.

31. Select User Interface Check – Alert Message node category.

69
ATD - Tutorial V6.0

32. Click on the push button next to the User Interface field. The User
Interface Selection dialog opens.

33. Here you can search for an existing user interface (window). The
search results scope is the project, i.e., you can search for a window
previously created for this project. Just click on the Search push

70
 ATD - Tutorial V6.0

button. The ATD Login window will be listed. Select it and click on the
OK push button.

It’s now time to define a data generation strategy for this node.

34. Back on the ATD main window click on the push button next to the
Strategy Name field. The Strategy Name Selection dialog opens.
35. Click on the New push button. The Strategy Detail dialog box opens.
36. In the Name field type “error_message_1”.
37. In the Alert Title field type “Error” with the double quotes.
38. In the Alert Message field type "Hostname is mandatory" with the
double quotes.

39. Click on the OK push button. The strategy is saved in your central
repository and can now be reused.

Let’s do the same for the remaining error messages effects. Repeat step 30 to 39
for each of the following nodes: ”Error message 2”, “Error Message 3”, and “Error
Message 4” just changing the strategy detail Alert Message parameter according
to the node you are working on.

71
ATD - Tutorial V6.0

Continuing with the test data identification process let’s go to the next node.

40. Select the first cause under USERNAME group node named “Enter
UserName”.

Another cause node, another text field that requires input data. Let’s define that
by specifying another User Interaction – Set Value node category.

41. Select User Interaction – Set Value from the Node Category combo
box. The Field Definition and Data Generation Strategy group boxes
get visible.

42. Select the user interface field. Click on the push button next to the
User Interface field. Search for the ATD Login window. Select it and
click on the OK push button.
43. Create a new Logical Name for this node. Call it “username”. See
steps 10 to 12 if you are not sure how to proceed. For the Field Format
select “text”, the one we’ve created before.
44. Create a new Single Constant strategy as we’ve created before. Call it
“enter_username” and type “Admin” in the Formula field. See steps 22
to 27 if you are not sure how to proceed.

The next node is similar to the “NOT Enter Hostname” cause node, i.e. this node
does not actually interact with any GUI Object, so let’s just defining it as a Cause
Comment.

45. From the Cause / Effect Definitions tree select the cause node named
“NOT Enter UserName”.
46. Select Cause Comment – No Data Required from the Node Category
combo box.

The next two cause nodes under PASSWORD group are very similar to the ones
under HOSTNAME and USERNAME groups. These two causes are also
mapped to a text field. Let’s define their test data as we’ve done so far.

47. From the Cause / Effect Definitions tree select the cause node named
“Enter Password OK”.
48. Set up a new User Interaction – Set Value, Single Constant strategy for
each of these causes. See steps 5 to 27 if you are not sure how to

72
 ATD - Tutorial V6.0

proceed. You will need to create a new logical name to map with this
node. Call it “password” and associate it with the “text” field format
already created. Finally, create two new Single Constant strategies for
each of the cause nodes associated with the password group. For the
“Enter Password OK” cause defines the single constant formula value
as “” while for the “Enter password NOK” specify “xpto” as for the
formula value.

Continuing with the test data identification process let’s go to the next node.

49. Select the first cause under ACTIONS group node named “Validate”.

This cause specifies the way the user information will be sent to the server for
login validation. Let’s map it with a click on an OK push button. In order to do that
we’ll define a User Interaction – Command node category.

50. Select User Interaction – Command from the Node Category combo
box.

51. Select the user interface field. Click on the push button next to the
User Interface field. Search for the ATD Login window. Select it and
click on the OK push button.
52. Create a new Logical Name for this node. Call it “ok”. See steps 10 to
12 if you are not sure how to proceed. Now we need to create a new
field format that maps to a push button GUI object.

53. Click on the push button next to Field Format field. The Field
Format Selection window opens.

73
ATD - Tutorial V6.0

54. Click on the New push button in order to create a new field format. The
Field Format Detail window opens.

55. In the Name field type “pushbutton”.

56. From the Field Type combo box select “Graphical Object”.
57. From the Field GUI Type combo box select “CommandButton”.
58. Click on the OK push button. The Field Format Detail window closes.
59. Click on the OK push button. The Logical Name Detail window closes.

It’s now time to define a data generation strategy for this node. Our goal is to
specify a click on the OK push button in order to validate the user information.
We can do this by specifying a User Interaction strategy.

60. Click on the push button next to the Strategy Name field. The
Strategy Name Selection dialog opens.
61. On the Strategy Name Selection window click on the New push button.
The Strategy Detail window opens.
62. Name this strategy as “click”. In the Name field type “click”.
63. From the Strategy Type combo box select “User Interaction”.
64. From the Command combo box select “Mouse Click”. Just let all other
available parameters as default.
65. Define this strategy as Public. This way we can reuse it latter for other
actions.

74
 ATD - Tutorial V6.0

66. Click on the OK push button. The strategy is saved in your central
repository and can now be reused.

Continuing with the test data identification process let’s go to the next node. The
next cause node named “Cancel” is similar to this last one. Our goal is to specify
a click on the Cancel push button in order to cancel the user information.

67. From the Cause / Effect Definitions tree select the next cause node
named “Cancel”.
68. Select User Interaction – Command from the Node Category combo
box.

69. Select the user interface field. Click on the push button next to the
User Interface field. Search for the ATD Login window. Select it and
click on the OK push button.
70. Create a new Logical Name for this node. Call it “cancel”. See steps
10 to 12 if you are not sure how to proceed. For the Field Format select
“pushbutton”, the one we’ve created before.
71. For the strategy select the “click” strategy we’ve previously created.

Continuing with the test data identification process let’s go to the next node.

72. From the Cause / Effect Definitions tree select the next effect node
named “Exit Application”.

This node does not actually interact with any GUI Object. We do not need to
provide input or output data for it. For this effect we define an Effect Comment –
No Data Required node category.

73. Select Effect Comment – No Data Required from the Node Category
combo box. Although this node category does not need an associated
data generation strategy you can optionally specify one providing the
exact comment you wish in order to complement this result.

Continuing with the test data identification process let’s go to the next node.
These two next nodes actually represent what we call a system state or test case
initial condition.

75
ATD - Tutorial V6.0

74. Select the first cause under HOST group node named “HostOnLine”.
75. Select System State from the Node Category combo box.

76. Let’s create a new strategy for this node. Click on the push button
next to the Strategy Name edit field and Name it “host_online”.
77. In the Formula field type “ATD Server running.” with the double
quotes.
78. Check the Execute Command check box.
79. In the Command Line field type “C:\Program Files\AtYourSide
Consulting\ATD Server\QMServer\ATDServer.exe" with the double
quotes.

80. Click on the OK push button. The strategy is saved in your central
repository and can now be reused.

Continuing with the test data identification process let’s go to the next node. Let’s
do the same for the next node. For this node we’ll define the opposite situation,
i.e. the ATD Server not running.

81. From the Cause / Effect Definitions tree select the next cause named
“HostNOTOnline”.

76
 ATD - Tutorial V6.0

82. Select System State from the Node Category combo box.
83. Create a new Single Constant Data Generation Strategy and name it
“host_NOT_Online”.
84. In the Formula field type “ATD Server NOT running.” with the double
quotes.
85. Check the Execute Command check box.
86. In the Command Line field type "taskkill /IM "ATDServer.exe"" with the
double quotes.

87. Click on the OK push button. The strategy is saved in your central
repository and can now be reused.

Continuing with the test data identification process let’s go to the last node.

88. From the Cause / Effect Definitions tree select the next effect node
named “Enter Application”.

After fill all the fields and validate the information we must verify that the main
ATD window opens. Let’s just define a validation procedure that will check this.

77
ATD - Tutorial V6.0

89. Select User Interface – Check Attribute from the Node Category
combo box.
90. Create a new User Interface. Call it “ATD main window”.

91. Click on the push button next to the Strategy Name edit field.
Create a new Strategy named “enter_app”.
92. From the Strategy Type combo box select “List Attributes”.
93. Select “true” for the Visible available attribute.

94. Click on the OK push button. The strategy is saved in your central
repository and can now be reused.

What have we done so far?

We’ve identified all test data needed to execute the generated test cases for the
Enter System 3 requirement.
We’re now ready to start the test data generation process.
If you’ve had some doubts about doing this, please import this same requirement
we provide on the samples folder.

78
 ATD - Tutorial V6.0

Starting test data generation

After completing the test data identification you are able to start the test data
generation process. ATD will provide test data in order for you to execute all test
cases.
1. Click on the Cause / Effect Definitions tab and select Nodes > Start
All Test Data Generation. Alternatively you can use the F9 softkey.
During test data generation process, ATD will show the generation
progress in the main window status bar. When this process finish, the
Test Data Generation dialog box opens informing you the process has
finished.

2. Click on the OK push button. All generated test data was stored in the
repository. A new tab appears on ATD main window.
3. Click on the “Test Data” tab. In the left frame you can see an empty
Test Cases tree. Right click on the test cases tree root node and add
all test cases.

79
ATD - Tutorial V6.0

The test cases are now grouped by system state.

4. Expand the tree and select the first available test.

80
 ATD - Tutorial V6.0

You can now start to execute all test cases. You can even choose to automate
them in order to turn your test execution process more effective and efficient.

81
ATD - Tutorial V6.0

Lesson 5: Test automation

Our goal for this lesson is to provide you with the knowledge in order to map the
test automation information and generate automated test scripts for HP
QuickTest Professional.
Once test data has been specified and generated you can choose to run all your
test cases manually or let ATD generate all the respective automated test scripts
for your automated software quality tool.
The biggest benefit of automated test tools is that they (if implemented properly)
allow you to be more productive, testing your systems quicker without losing
quality. With automated test scripts you will improve the speed and the reliability
of your test cases execution. The new ATD Test Script Generator (TSG) module
allows you to automatically generate test scripts for the main automation tool in
the market.

Overview
This lesson:

Explains how to map the test automation information.

Teaches you how to generate automatic test scripts.

82
 ATD - Tutorial V6.0

Mapping test automation information

In order to illustrate how to map test automation information we’ll use the Enter
System 3 requirement we’ve specified before on this tutorial. After finishing this
chapter we’ll have HP QuickTest Professional automated test scripts to execute
all generated test cases.

To map test automation information

During this process we’ll identify test data for all cause and effect requirement
nodes.
1. Open the “Enter System 3” requirement.
2. Expand the requirement Cause / Effect Definitions tree.
3. Click on the Test Automation tab on the right pane.
4. Select “Quick Test 9.2” from the Automation tool dropdown list.
5. Select the file that contains the object physical descriptions. Provide an
object repository file exported to xml (*.xml). Click on the and
select the correspondent file that contains the object’s physical
descriptions you want to map to your pre defined objects used on the
opened requirement.

83
ATD - Tutorial V6.0

6. From the ATD test automation object tree select the logical object
you wish to map. The Logical description grid shows two parameters
allowing you to easily identify the selected logical object facilitating the
map process. The two attributes are field format and correspondent
description.
7. From the Automation tool objects tree select the correspondent
object you wish to map the logical object to. Every time you select an
object on the Automation tool objects tree the physical attributes grid
gets populated with the information related to the selected automation
tool object physical attributes.
8. Click on the Map push button. In case the selected objects belong to
different classes ATD displays an error message informing you that the
two selected objects are not compatible. After a successfully map the
mapped ATD test automation object tree node changes to black. This
is a visual indicator informing you that the logical object is already
mapped to an automation tool object physical description. At the end
when all the ATD test automation objects tree nodes are black
(mapped) you are ready to start generating automatic test scripts for
the mapped tool.

84
 ATD - Tutorial V6.0

Generating automatic test scripts

After mapping all information regarding the user interfaces and logical names
defined during the data definition process and the object’s physical description
needed by the automated testing tool, you can finally start generating all
associated automated test scripts.

To start test script generation:

1. Click on the Cause/Effect Definitions tab and select Nodes > Start All
Test Script Generation. Alternatively you can use the F10 softkey.
The Automated Script Generation dialog box opens.

2. Select “Quick Test Professional 9.2” from the Automation Tool

dropdown list
3. Now select the location where you to store the automated scripts by
clicking on the push button next to the Target Directory field.
4. Click on the OK push button. The test script generation process
begins. During the Test Script Generation phase, ATD will show the
generation progress in the main window status bar.

85
ATD - Tutorial V6.0

Lesson 6: Export / Import

ATD provides a process to export / import requirement definitions and

correspondent generated test cases, data identification and generated test data,
and test automation information to / from different servers. This functionality is
very useful when testing teams are working in different locations and needed to
share resources among them.

Overview
This lesson:

Teaches you how to export requirement information to a test file.

Shows the process of importing requirement specification and
generated test cases.

86
 ATD - Tutorial V6.0

Exporting a requirement information

We will now export the Enter System 3 requirement to a text file. This file will
have an *.atd extension.

Note: This option will not be available if you are using an evaluation version.

To export a requirement:
1. Select Requirements > Export Requirement to File…. The Export
Requirement to File dialog box opens.

2. Choose a location where to store the exported text file by clicking on

the Browse… push button.
3. Click on the OK push button. ATD will ask if you want to include the
generated test cases information in the exported file.

4. Click on the Yes push button in order to export information regarding

the generated test cases. Then ATD will ask you if you want to include
generated test data.

87
ATD - Tutorial V6.0

5. Click on the Yes push button in order to export information regarding

the generated test data. ATD starts the export process. ATD will show
the export process progress in the main application window status bar.
When finished ATD displays an information message informing you the
result of the exportation process.

6. Click on the OK push button to close the Export requirement dialog

box.

88
ATD - Tutorial V6.0

R. Lagares d’El Rei, nº21C-1F

1700-268 Lisbon – Portugal

www.atyoursideconsulting.com
info@atyoursideconsulting.com

Telf.: +351 21 848 7117

Fax: +351 21 849 8119

"@YourSide for better software"