Test Director - Overview and Best Practices

1. Purpose................................................................................................3
2. Overview on TestDirector........................................................................3
2.1 Requirements...................................................................................3
2.2 Test Plan.........................................................................................3
2.3 Test Lab..........................................................................................3
2.4 Defects...........................................................................................3
3. Site Administration.................................................................................3
3.1 Projects...........................................................................................3
3.1.1 Adding New Domains...................................................................4
3.1.2 Querying the data in project.........................................................4
3.1.3 Restoring the Project...................................................................4
3.1.4 Renaming the Project..................................................................4
3.1.5 Activating the Project..................................................................4
3.1.6 Deactivating the Project...............................................................4
3.1.7 Deleting the Project.....................................................................4
3.1.8 Removing the Project..................................................................4
3.2 Users..............................................................................................4
3.3 Connections.....................................................................................5
3.4 Licenses..........................................................................................5
3.5 TD Servers......................................................................................5
3.6 DB Servers......................................................................................5
4. TD Server Overview...............................................................................5
4.1 DomsInfo........................................................................................5
4.2 Project directories.............................................................................5
4.3 Significance of some other directories.................................................6
5. Creating the Project...............................................................................6
5.1 Pre - requisite for Creating MS Access Project......................................6
5.2 Pre - requisite for Creating Oracle Project............................................6
5.3 Pre - requisite for Creating SQL Project...............................................8
5. Managing the Project (Project Customization)............................................9
5.1 Overview.........................................................................................9
5.2 Change Password.............................................................................9
5.3 Set up Users....................................................................................9
5.4 Set up Groups..................................................................................9
5.5 Customize Project Entities.................................................................9
5.6 Set up workflow..............................................................................10
5.6.1 Add Defect Field Customization...................................................10
5.6.2 View Defect Field Customization..................................................10
6 Managing the Database.........................................................................10
6.1 Taking Backup using script...............................................................10
6.2 Taking cold back up........................................................................10
7 Report Generation in TD........................................................................10
7.1 Test Director Inbuilt Reports............................................................10
7.2 Document Generator.......................................................................11
7.3 Data Model for TD...........................................................................11
7.4 Report generation for Projects..........................................................12
8 Frequently occurring Problems with TD...................................................14
8.1 User gets Blank page on TD. User can’t access any module in TD.........14
8.2 User Changes the execution status in Test Lab module........................14
8.3 User gets runtime errors while accessing TD......................................14
8.4 User gets C++ Runtime error while accessing TestDirector..................15
9 FAQs & Best Practices in TD...................................................................15
9.1 What is the prerequisite for installing TestDirector Server?..................15
9.2 How do I upgrade the TD project?.....................................................15
 9.3 How do I export the test cases from TestDirector to MS Excel?.............16
9.4 How do I import the data from MS excel to TD?..................................16
9.5 How do I copy the existing Test cases from a Project to Other?............16
9.6 How do I arrange the test lab module if two iterations of execution is
planned?................................................................................................16
9.7 How do I migrate from MS access database to Oracle?........................17
9.8 Can I move the Project directory on TD server to some other location?. 17
9.9 Can I generate the document on requirement/Test plans/Defects?........17
9.10 Which is the database recommended for TestDirector?........................18
9.11 What do I do if MS Access database size is too large?..........................18
9.12 How do I rearrange the Test cases in Test set?...................................18
9.13 What is “unattached” in Test Plan and Test Lab module?......................18
9.14 Can I take Snapshot of screen while logging the defect?......................19
9.15 Can I maintain History for any of the attribute of defect/Test Case etc?. 19
10. Drawbacks of TestDirector..................................................................19
1.Purpose
The Purpose of this document is to get brief idea on Test Director as a testing
tool, understanding on report generation using database tables and different
kinds of problems user normally faces along with their solution.

2.Overview on TestDirector
TestDirector is Web-based test management tool. It helps you organize
and manage all phases of the application testing process, including
specifying testing requirements, planning tests, executing tests and
tracking defects. TestDirector is organized in four modules as mentioned
below.

2.1 Requirements
All the testing requirements are organized in this module.
Requirement tree shall be build to define overall testing requirements.
For each requirement topic in tree, create the detailed requirement. It
is better practice to update description for each of these requirements.
Each requirement is associated with the test cases in “Test Plan”
module. This is done in “Coverage View”.

2.2 Test Plan

This is repository for all the test cases. Test cases are organized in
hierarchically so as to build tree structure. Test cases are created with
detailed design steps. It is recommended to update description and
other related details for a test.

2.3 Test Lab

Actual Execution of the test cases happens in this module. Here you
define the groups of tests to meet various testing goals in the project.
E.g. it could be adding group of test cases in a test set to test specific
functionality in a module.

2.4 Defects
This contains all the defects for the application. All the activities like
adding new defect, fixing the defect, review and tracking the defect
are accomplished in this module.

3.Site Administration
This is Web environment provided for monitoring the Test Director
application. Site Administration provides you with the tools needed to
monitor the key aspects of Test director server and web environment. Site
Administration keeps you informed of the status of your TestDirector
system in real time.

3.1 Projects
This is used to manage your TestDirector projects. This includes adding
new domains and projects, querying data in a project, restoring a project,
upgrading a project, renaming a project, and activating or deactivating a
project, Deleting the project, removing the project.
Following section explains in brief each of these functionality.
 3.1.1 Adding New Domains
Projects are added through site administrator and associated with
domain. Domains are nothing but logical grouping of the projects.

3.1.2 Querying the data in project

Database details like database user, database type, database
instance etc can be viewed when user selects the project in Site
Administrator. User can also see all the tables associated with
project with query window. Database operations like
Select/delete/update etc are allowed using this query window.

3.1.3 Restoring the Project

TestDirector Project can be restored if user has project folder which
contains project details. Any TestDirector project contains
“Dbid.ini” file having project information like database name,
databse type, database user etc. This file is used to restore the
project.

Usually restoring is required if TestDirector project location is

changed or project folder is moved from default project location .

3.1.4 Renaming the Project

A Project can be renamed only if it is deactivated.

3.1.5 Activating the Project

When Project is activated, it can be viewed in available project list in
TestDirector login page.

3.1.6 Deactivating the Project

When Project is deactivated, it can not be viewed in available project
list in TestDirector login page. All the active users are disconnected
while Project is being deactivated .

3.1.7 Deleting the Project

When user deletes the project, it deletes all the project details from
server including folder structure etc.

3.1.8 Removing the Project

Removing project doesn’t delete the folder from the TD server but
project disappears from Site Administrator window. Also no user can
login to this project unless it is restored.

3.2 Users
You manage TestDirector users in the Site Administrator. You can add and
import new TestDirector users, define user properties, and change user
passwords. You add users here, to be available for giving specific access to
projects. For associating users to the project, please refer to “Managing
the Projects” section.
 3.3 Connections
You can view all active users and their details, which are connected to TD
at real time.

3.4 Licenses
This allows viewing Number of licenses used, available, expiry date etc.
New Licence key for the TD shall be updated here. Licenses are counted
per desktop.

3.5 TD Servers
It lists out all the TD servers available. By default it updates with the
current Test Director server.

3.6 DB Servers
It lists out all the database servers available. Following are the important
parameters in this.
Server Alias = This is the database SID name.
DB Admin user = User required to connect to the Database instance. This
user shall have admin access given to the database. This is “system” level
user.
DB Admin Password = Admin password for connecting to DB instance.

4.TD Server Overview

There are few important directories used by TestDirector.

4.1 DomsInfo
This is very important folder wrt TD server is concerned. It contains
mdb file which has all the admin related information, project details,
Schema name for the oracle user for oracle project , All the user
names and passwords etc.
This mdb file is located at “C:\Program Files\Common Files\Mercury
Interactive\DomsInfo\doms.mdb”. Default password for this mdb file
is “tdtdtd”.

4.2 Project directories

All the TD projects are located at following directory.
“C:\TD_Dir\<domain name>\<project name>”. Table below describes
significance of each of directories inside any TestDirector Project.

Sl Folder Name Description

No.
1 Attach This contains all the attachments in the project.
Attachments are usually added in Test Plan/Test
Lab /Defect module.
2 Script_Templates Project can be customized to change User
Interface look for Add Defect/View Defect
window. When it is customized for a project it
creates .tds file and is stored in this folder.
3 Scripts This is the default workflow definition (Add
 Defect window layout) available.
4 Settings\Private Whenever users re-login to TestDirector, User
usually sees the same setting as it was there last
time. All these user preferences are stored in this
folder.

4.3 Significance of some other directories

Beside the folders mentioned above, there are few other folders, which get
created at client desktop when user installs client component for
TestDirector.

Sl Folder Name Description

No.
1 C:\Program Files\ This stores all the dynamic link libraries
Common Files\Mercury (.dll) to be used for client component of
Interactive\TD2000_80 TestDirector.

2 %Local Directory Whenever user logs in to TestDirector,

%Td_80 Many times data is cached at client
desktop. Normally this data is execution
steps when user is executing any test case
(i.e. “Run” window is open at user’s
desktop). This Cached data is kept in this
directory.

5.Creating the Project

Project Creation is done in Site Administrator. There are two options for
database used for TD project. Project can use MS Access or Oracle as
database. Oracle is preferred option than MS access as it has good
performance and stability.

5.1 Pre - requisite for Creating MS Access

Project
Following are the prerequisites for creating MS Access project.
1. It is preferable to have TestDirector installed on Windows 2000 server
so that many users can connect to TestDirector.
2. IIS shall be installed on machine as TestDirector uses this service.
3. TD Server shall have MS access installed.
4. It shall have enough space to accommodate TestDirector data
like .mdb file, attachments, personal settings for each users etc.

5.2 Pre - requisite for Creating Oracle Project

Following are the prerequisites for creating MS Access project.

1. It is preferable to have TestDirector installed on Windows 2000 server
so that many users can connect to TestDirector.
2. IIS shall be installed on machine as TestDirector uses this service.
3. TD Server shall have Oracle Client installed. It is essential to have
same version of Oracle Client as Oracle Server. It is recommended that
Oracle server & TestDirector server be installed on different machines.
 Test Director support only following oracle versions 8.1.7, 9.0.1 or
9.2.0.
4. It shall have enough space to accommodate TestDirector data like
attachments, personal settings for each users etc.

Beside these, there are two more prerequisites for creating Oracle Project.
1. User shall have Table space having enough memory.
Data table space = This is Table space for actual storage
Temp table space = This is temporary table space used by oracle for
operations like sorting etc.
2. User shall have user id and password, having admin rights to connect
to database.

Minimum space recommendations

When creating a new empty database it is recommended that the Device (Tablespace)
selected have at least 50 MB of free space. When copying the data from an existing
database, it is recommended that there be at least 2 to 3 times the space that is
currently being used by the database or 50 MB, whichever is greater. The Temporary
Space Device (Tablespace) is used for things like the rollback transaction log which is
very important for recovering from errors. It is recommended that the Device
(Tablespace) used for the Temporary Space have at least half as much free space as
the size of the space being set aside for the database itself.

In Oracle, TestDirector requires space on the server where the TestDirector project
tables can be created. It is usually a good idea to set up two separate tablespaces for
TestDirector. One tablespace for the data and the other for temporary storage (for
sorting and such).

This is an example on how the user creates a “tablespace” (device) in oracle: NOTE:
Please consult your Oracle DBA before attempting to create a tablespace.

Here is the SQL for creating a 100 MB tablespace for data called "TD_DATA_SPACE."

   CREATE TABLESPACE TD_DATA_SPACE DATAFILE 'c:\orant\td_data_space.dat' SIZE

100M;

Where the tablespace is being creating in a file located at "c:\orant\td_data_space.dat"

on an NT server.

Here is similar command that might be used to create the temporary space.

   CREATE TABLESPACE TD_TEMP_SPACE DATAFILE 'c:\orant\td_temp_space.dat' SIZE

100M

Minimum Priviledges required

Oracle

The following Oracle privileges are required by TestDirector 7.6 and 8.0. Note that the
user account should be created on the Oracle database server by an Oracle database
administrator logging in as "SYS".

NOTE:
The user name must be capitalized.

CREATE USER <USER> IDENTIFIED BY <PASSWORD>

DEFAULT TABLESPACE <USERS_TABLE> TEMPORARY
TABLESPACE <TEMP_TABLE> ACCOUNT UNLOCK;
GRANT CREATE SESSION TO <USER> WITH ADMIN OPTION;
GRANT CREATE TABLE TO <USER> WITH ADMIN OPTION;
GRANT CREATE VIEW TO <USER> WITH ADMIN OPTION;
GRANT CREATE USER TO <USER>;
GRANT SELECT ON "SYS"."DBA_FREE_SPACE" TO <USER>;
GRANT SELECT ON "SYS"."DBA_TABLESPACES" TO <USER>;
GRANT ALTER USER TO <USER>;
GRANT DROP USER TO <USER>;
GRANT SELECT ON V$INSTANCE TO <USER>;

Note that this information can be found in the TestDirector Administrator's guide in the
Chapter on Configuring Servers and Parameters. It is in the section for defining new
database servers for Oracle.

5.3 Pre - requisite for Creating SQL Project

Following are the prerequisites for creating MS Access project.

1. It is preferable to have TestDirector installed on Windows 2000 server
so that many users can connect to TestDirector.
2. IIS shall be installed on machine as TestDirector uses this service.
3. TD Server shall have SQL server installed.
4. It shall have enough space to accommodate TestDirector data like
attachments, personal settings for each users etc.

Beside these, there are two more prerequisites for creating Oracle Project.
1. User shall have user id and password, having admin rights to connect
to database.

Minimum space recommendations

When creating a new empty database it is recommended that the Device selected have
at least 50 MB of free space. When copying the data from an existing database, it is
recommended that there be at least 2 to 3 times the space that is currently being used
by the database or 50 MB, whichever is greater. The Log device is used for things like
the rollback transaction log which is very important for recovering from errors. It is
recommended that the device used for the Log space have at least half as much free
space as the size of the space being set aside for the database itself.

Minimum Priviledges required

Does the "sa" user have to be used to create a SQL Server project in
TestDirector

Can the user use another subset user's permission to create or delete a SQL Server
database in TestDirector instead of using the "sa" privilege? Also, what is the password
for the "sa" user?

Another user can be created to create a TestDirector SQL Server project

It is possible for SQL Server 7.0 and 2000, but not for SQL Server 6.5. You have to use
the "sa" privilege to create or delete a TestDirector SQL Server project for SQL Server
version 6.5. This is limited by the SQL Server 6.5 end.

However, for SQL Server 7.0 and 2000, you can create a user with privileges that are
the combination of a database creator and a process administrator on the SQL Server
backend and then use this username, different from "sa," to create or delete a SQL
Server project in TestDirector.

NOTE:
You must use the "sa" user the first time that you create a MS SQL Server project
through TestDirector, or grant the user "Security Administrators" role to create the first
project. The first time TestDirector creates a project on a new SQL Server database, it
needs to create the "TD" user first.
The default password for the "sa" user is blank after first installing MS SQL
Server. If this does not work, then a password was created for the user.
Please consult you SQL Server DBA for more information. If your DBA will
not give you the "sa" password, then just have the DBA create the first
project. There is a way to keep and save the password where it will be
encrypted.

5.Managing the Project (Project

Customization)

5.1 Overview
This section gives brief description about how user manages different
projects. It also briefs different options available in TD for project
customization. This facility is available through “Customize” option on
a login screen of TD.

Using Project Customization, you control access to a project by

defining the users who can enter the project and by determining the
types of tasks each user can perform. You can also customize a
project to meet the specific requirements of your testing team.

5.2 Change Password

User can change their own password in this option. This option is
available for all the users.

5.3 Set up Users

Only Administrator has access to this link. Users are associated to the
project here. User shall be assigned to appropriate groups depending
on their responsibilities. This is same as creating the user from Site
Administrator except that default password can’t be set for the user
here. By default it will be blank.

5.4 Set up Groups

All the groups present in the project are displayed over here.
Permissions can’t be changed for default groups available. To
customize group permissions it is advisable to create new group, as
you can’t change the permissions for default roles available in TD.

Usually there are Project needs like only Testing team can close the
defect. In such scenario, you need to create new group and set such
restriction.

5.5 Customize Project Entities

Project entities like Defect, run, requirements, Test plans etc can be
customized here. Changes shall be done to this module depending on
the test execution planning for the project, reporting requirements.

User can change the attributes of the field like whether field is
mandatory, Does TD needs to maintain history for the field, LOV
values for the field etc. LOV values can be added depending upon the
project needs.
 5.6 Set up workflow
This section is used for the Customization of user interfaces in user
interfaces for “Add Defect” and “View Detail” pop up window in Defect
module.

5.6.1 Add Defect Field

Customization
This is used for the Customization of user interfaces for “Add Defect”.
Customization includes creating the tabular structure on the Add defect
window, re-arranging (deciding the sequence) the field’s positions etc.
This customization shall be done at Group level (e.g. QATester, MAXIM
Testing Group, Infosys Testing Team etc).

5.6.2 View Defect Field

Customization
This also has the same customization available as “Add Defect” window.
Customization done in this will be reflected when user double clicks on a
defect.

6 Managing the Database

6.1 Taking Backup using script

This backup can be taken when database is up and running. Execute the
attached batch file to take back up. SUSHIL
To take back up, just double click the batch file given in brief pack. It
takes backup of whole database. It keeps the backed up file in specified
location mentioned in batchfile. It shall create .dmp file.

6.2 Taking cold back up

Cold back up is taken when Oracle is shut down. Please Follow the
command below to take cold backup.
1. Go to command prompt
2. Execute sqlplus <user name>/<password>@<Database instance
name>
3. Execute shutdown immediate;
4. Take the back up of all database files (which includes .dbf file as well
as control files .ctl)

7 Report Generation in TD

7.1 Test Director Inbuilt Reports

Test Director provides many inbuilt reports across different module
like “Requirements”, “Test Plan”,” Test Lab”, ”Defects”. These
reports take care of cross-reference between different modules in
TD. To generate these reports, Follow links through “Analysis”
menu on the top left corner of TD.

Reports are available in tabular as well as graphical format.

 7.2 Document Generator
This is one of the good features available in TestDirector. The
TestDirector Document Generator enables you to create a Microsoft
Word document containing a project’s requirements, planning, test
list, test execution, and defect tracking data.
User can customize the document by filtering and selecting the
specifc modules from the available options. Link for Document
Generator is available under “TOOLS” menu at the top right corner
of TestDirector.

7.3 Data Model for TD

User can specify the type of database to be used for the project. It
can be Oracle, MS Access, Sybase or MS SQL. Data model for
TestDirector Entities is described in the table below.

Sl Table Related Entity Description

No.
1 REQ Requirements Contains information
about testing
requirements.
2 REQ_COVER Requirements Matches Testing
Requirements to the tests
and steps that cover
them.
3 Contains list of all the
TEST Tests tests in Test Director.
4 Contains information
about design steps. -
Steps that are part of
DESSTEPS Design Steps planned test.
5 Contains list of all test
CYCLE Test Sets sets in Test Director.
6 Matches Tests to
Testsets. Enable multiple
TESTCYCL Test Sets instances of a single
7 Contains information
RUN Test Execution about the test executions.
8 Contains information
about test step execution
within the test
STEP Test Step Execution executions.
9 Contains information
about all the defects
BUG Defects recorded in the project.
10 Matches defects records
to tokens used to search
BUG_TOKENS Defects for similar defects.
11 Contains tokens used to
enable automated
searching for similar
TOKENS Defects defects.
12 Manages all files and
URLs attached to any
CROS_REF Attachments project entity.
13 Contains record change
information for the
HISTORY History project entities.
14 Contains the test plan
tree with which the tests
are associated. Also has
different role as a system
ALL_LISTS Test Plan tree table.
15 Contains manual
test/runs parameters and
STEP_PARAMS Test Parameters their optional values.
16 Contains automatic
generated alerts for data
objects and user defined
follow ups for data
ALERTS Traceability objects.
17 Contains the test lab tree
with which the test sets
CYCL_FOLD Test Lab Folders are associated.
18 Contains traceability
identification rules and
Customization/ enable a email
RULES Traceability notification.

7.4 Report generation for Projects

Following table lists different queries available for generation of
report and their brief description. All the Queries are attached in
appendix section.
Sl File Name Description
No.
1. Execution Status.txt This Report is used to get
execution status report for the
1 project.
2. Not Completed Test These are the test cases
2 Cases.txt having “Not Completed” status.
3. No Run Test Cases.txt These are the test cases not
3 yet executed.
4. Test cycle Not These shall give all the test
Updated.txt cases which are actually
executed but don’t have test
4 cycle field updated for it.
5. History - Status1- These are generic query used
Status2 Flow.txt to get all the defects whose
status is changed from Status1
5 – Status2.
6. Rejected Bugs till This is generic query used to
date.txt get all the defects which are
6 rejected till date.
7. TCs NA in 2nd iteration & This shall give all the test
Pass-Failed in 1st cases which are Passed/Failed
iteration.txt in 1st iteration and N/A is 2nd
7 iteration.
8. Test Cases Not Mapped This shall give all test cases
to Test set.txt which are not mapped to any
of the test set in Test lab
8 module.
9. Test Cases Failed but No This shall give all such test
defect logged for it.txt cases which are failed but
there is no defect logged in for
9 the same.
10. Individual Tester This shall be used to see how
Status.txt many test cases are executed
10 by an individual.
11. Folder Name in TestLab This query is used to get folder
Module .txt name wrt TD Database and
other details for a for any
folder in Test Lab module. Out
put of this is important for
many queries in different
11 reports.
12. Number of Test Cases This shall give number of test
12 in Test Lab Folder.txt cases in any Test lab folder.
13. Defect Not Mapped to This shall give all the defects
Testcase.txt which are not mapped to test
case. In Other words, these
13 are the defects found out and
directly entered in Defects
module using “Add Defect”
button.
8 Frequently occurring Problems with TD

8.1 User gets Blank page on TD. User

can’t access any module in TD
This problem occurs because of different reasons. One of the
possible reason is listed below.
1. User may not have local admin privileges on the desktop.
2. Another possible cause could be that the security for IE may be
set to high. Please do the following to decrease the security
level:
1. On the client machine bring up Internet Explorer.
2. Go to Tools -> Internet Options.
3. Click on the Security tab.
4. For Internet, decrease the security from High to Medium.
5. For Local intranet, decrease the security to Medium-low.
3. Following list of programs shall not be installed on the client
machines, these are programs that will conflict with the TD
application.
Surf Safari by NetZero
Gator
Go!Zilla
Gator Information Network (GAIN)
GMT.exe (another Gator product)
CME.exe
Norton Internet Security
SnagIt with Internet Explorer add-in
Hotbar
Compuware's DevPartner Studio

8.2 User Changes the execution status in

Test Lab module.
Whenever User Changes the status of any of the test case in
Test Lab module, TD creates an extra run for it with Duration as
“0” seconds. Status of this run may not be same as the status
of test case.

8.3 User gets runtime errors while

accessing TD
User may come across different kinds of problem like getting
Run time error while accessing the login page for TD, or
accessing any particular module inside TD etc. These kinds of
problem are normally occurs because of some changes in Test
Director client side installation. Best way to avoid such defect is
re-installing the TD.

Utility for uninstalling is available in the briefing pack. User shall

follow the instruction mentioned below.
1. Close all the browsers.
2. Execute the un-installation utility for TD.
3. Delete the folder “C:\Program Files\Common Files\Mercury
Interactive\TD2000_80”. If it gives error related to access
violation, ignore it.
 4. Open browser and navigate to http://<TestDirector
Server>/tdbin
5. Click on “Add In Page”
6. Click on “TestDirector Client Side Set up” link and install the
client component.
7. Go to http:// <TestDirector Server>/tdbin/start_a.htm

If still the problem persists, User may have to try option like
restarting machine and again try the steps mentioned above.

8.4 User gets C++ Runtime error while

accessing TestDirector.
Some times when user tries to connect to TestDirector, it
gives C++ run time error and user can’t login to TD. This
error could also happen when user is trying to access “Test
Lab” module. Usually these types of problems get resolved
when you try to fix it in the similar way as mentioned above
for “Getting blank page while accessing TD” problem. If still
problem persists only solution to access TD is using the
utility provided by Mercury Interactive called “TDExplorer”.
In other words, In such scenario’s user can’t access TD
using Internet Explorer, Instead user has to rely on this
utility.

9 FAQs & Best Practices in TD

9.1 What is the prerequisite for installing

TestDirector Server?
TestDirector server runs only on windows operating system.
It used Internet Information Server(IIS) as the web server.
It needs to have MS Access installed if user is intended to
create MS Access TestDirector projects. If TestDirector
project is to be created using Oracle as the back end, Oracle
client must be installed on the TestDirector server. For more
detailed information on installation process and more
detailed specification, refer to Installation guide provided by
Mercury Interactive.

9.2 How do I upgrade the TD project?

After installing TestDirector 8.0, if you want to work with a
TestDirector project created with TestDirector 7.x, you must first
upgrade the project, using the Site Administrator in TestDirector
8.0. If you created a project with TestDirector 6.x, you must first
upgrade the project to TestDirector 7.2, using the Project
Administration utility. You must then upgrade it to TestDirector 8.0.

Before you install TestDirector 8.0, it is recommended that you:

 Back up your TestDirector project. For information on
backing up a TestDirector project, refer to the TestDirector
Administrator’s Guide.
  Uninstall the previous version of TestDirector. To remove
previous versions of TestDirector from your computer, use
the Uninstall utility in the TestDirector program group.

9.3 How do I export the test cases from

TestDirector to MS Excel?
There is no option provided in Test Director where user can
copy the set of test cases at a time. User has to export
individual test case. This can be achieved using “Save As”
option in Test Plan module.

9.4 How do I import the data from MS

excel to TD?
There are few add-ins provided by Mercury interactive which
have to be installed on client machine to import data from
MS excel to TestDirector. User simply matches the
TestDirector column with the MS excel column while using
that excel add-in.

Add-in for importing from MS-word to TD is also available.

9.5 How do I copy the existing Test cases

from a Project to Other?
It is recommended to use “Copy” option while creating
project itself to copy the details from a project to another.
Otherwise User has to just copy the folder from source
project and paste it in destination project in Test Plan
module. While using “Copy” function during creation of
project, it asks for different modules to be copied to
destination project. Select the “Tests” check box for copying
only test cases.

9.6 How do I arrange the test lab module

if two iterations of execution is
planned?
There are two different ways to arrange test lab for two
iterations of Test execution. In both the approaches, it is
difficult to generate report using TestDirector. We need to
have SQL queries prepared to run on project database.

Approach 1: Create two different folders & Test sets in Test

lab module which distinguish between two iterations. It is
easier for user to distinguish the test sets for two iterations.
Approach 2: Add a user defined field in Test director for
Run. This is Test Cycle field which distinguishes between two
iterations.
9.7 How do I migrate from MS access
database to Oracle?
User shall have set up ready as mentioned in “Pre - requisite
for Creating Oracle Project” section above. Once it is done follow
the following steps.
1. Navigate to Site Administrator.
2. Go to “Projects” tab.
3. Click on “Create Project”.
4. Select Oracle project as option.
5. Specify the Server Name and admin user and
password. Click on Next.
6. Select Data space and temporary table space to be
used for the project.
7. Click on “Copy” button. It shall take user to next
window wherein user can select the source project to
copy from and it will list out different modules to be
copied like tests, requirements, run, defects etc.
8. Again Click on “copy” to start the copying process.

9.8 Can I move the Project directory on TD

server to some other location?
Many times user wants to move the directory from default
location to some other because of various reasons like disk
space problem etc. It can be achieved very easily in
TestDirector. Follow the following steps to relocate the
directory.
1. De-activate the project using Site administrator.
2. Copy the existing project directory on TestDirector
server ( By default it will be present at <TD default
drive>\TD_Dir\<domain name>\<project name>)
and paste it to new location. Make sure that new
folder shall have full access given to everybody
(Read as well as Write).
3. Navigate to Site administrator. Select a project and
click on “Restore” project. It shall ask for DBID.ini file
location. Select the new location of this file and click
on “OK”.
4. Now project will point to new location. You can delete
the source folder from default location mentioned in
point 2.

9.9 Can I generate the document on

requirement/Test plans/Defects?
TestDirector provides tool called “Document Generator”
where in MS word document can be prepared which consists
of all the details available in TD like requirements, Test
cases, Test runs, Defects etc. Different customization,
graphs, filter and sort criteria, modules to choose from are
available in Document Generator. Document Generator is
available on each client machine where TD client component
is installed. To access Document Generator follow the below
steps.
1. Login to TD project.
 2. Navigate to TOOLS (present in right top corner of the
page)  Document Generator.
Document Generator usually takes more time and system
me become slow But it is useful in terms of reporting as
many of the option available inside can’t be achieved
through TD reports.

9.10Which is the database recommended

for TestDirector?
Database selection for TestDirector mainly depends on
expected size of project and number of users accessing it.
For small size project (up to 60 MB ) and only 15-20 people
accessing it, user can opt for MS access as backend. But for
bigger project where number of concurrent users is also
high, user shall opt for Oracle as database. It is always
safer to go with Oracle as database for stability and good
performance.

9.11What do I do if MS Access database

size is too large?
Ideally If you have small project and number of concurrent
users are also few, you can use MS Access as database.
Size recommended for MS access database is around 60 MB.
If size of the MS access database is increasing , it will cause
system instability and thereby poor performance. It is
advisable to migrate the project to Oracle at that point. This
can be very easily achieved using Site Administrator. Details
on how to do it is mentioned in “How Do I migrate MS
Access Project to Oracle” above.

9.12How do I rearrange the Test cases in

Test set?
Whenever you map the test cases to Test set, these are
arranged in the order you have added them. Sometimes
user may want to rearrange them. Follow the steps below to
do it.
1. Select the test set where test cases are to be re-
arranged.
2. Right click anywhere in the right pane.
3. Select “Order Tests” option.
4. User can re-arrange the test cases in pop-up window.

9.13What is “unattached” in Test Plan and

Test Lab module?
It is similar to “Recycle bin” in windows. Whenever user
deletes any Test Plan or Test sets, by default it goes in to
“unattached” folder. You can retrieve the items from
unattached folder any time. While deleting any folder, TD
prompts for option about whether user wants to move it to
unattached folder. If user is very sure about deleting these
permanently , it is advisable not to move them to
unattached folder as unnecessary it occupies space. This is
 very important especially when you are using MS access
database.

User can manually delete the items in “unattached” folder,

but it takes lot of time.

9.14Can I take Snapshot of screen while

logging the defect?
Many times user wants to take screen shot while logging the
defect so that it is easier for person who is analysing the
defect to understand it. Test Director has the facility to take
snapshot of the screen while logging the defect. Icon is
provided on the “Add Defect” screen.

9.15Can I maintain History for any of the

attribute of defect/Test Case etc?
By default TestDirector maintains history of few of the
attributes. These can be found out in Project Customization
 Customize Project entities. There is a flag called
“History” which can be set for an attribute.

10. Drawbacks of TestDirector

There are many drawbacks in TestDirector. Though none of them are
listed in TestDirector release notes, these are found after extensive
use of TestDirector. These are listed below.
1. By default TD maintains history of status of the defect.
Whenever Defect is closed it updates “BG_CLOSING_DATE” field
in BUG table as well as “HS_CHANGE_DATE”
field in HISTORY table. Many times these values don’t match.
2. TestDirector doesn’t provide any reports if you are planning for
two iterations of test execution. You can’t get iteration wise
reports. In such case it advisable to create a user defined field
“Test Cycle” for test run. And generate the reports using SQL
queries.
3. If a requirement is mapped to more than one test case, status
of the requirement doesn’t get reflected properly. E.g. if one of
the test case is N/A, then status of the requirement still show
as Not completed.
4. Whenever you create the folders in Test Lab module, it will be
arranged in some random sequence. Though Sort option is
provided by mercury, it doesn’t work.
5. User can’t navigate directly from Defect to corresponding test
set in Test lab module.
6. A defect can’t be associated to more than one test case.
Because of this defect tracking to all relevant test cases is not
possible.
7. In Project customization, one of the option is Setting up the
workflow. Here you can change the look and feel of “Add
Defect” / “Defect Detail” window. Once you change this
workflow and again visit the Set up workflow process, original
changes won’t be reflected there. You will see altogether
different sequence for the fields.
11. Appendix
These are the queries used for report generation.
Please note the following points:
1. Query uses user defined fields added for reporting purpose of
current project. If your project doesn’t have any user defined
field, you can remove corresponding reference from the
queries.
2. User defined field names may change depending on the
sequence of how these are added to the project. E.g. User field
for Test cycle in defect could be BG_USER_01 for one project
while it could be BG_USER_03 for other.
3. All these queries are made based on the reporting requirements
for this project. Click here for new queries which can be
constructed based on the data base structure explained above
(section 7.4).