background image
<< Evaluating Tests | Automated Test Scripts and Rational Robot >>
<< Evaluating Tests | Automated Test Scripts and Rational Robot >>

Projects and the Rational Administrator

TestManager and Other Rational Products
Projects and the Rational Administrator
When you work with TestManager, the information that you create is stored in
Rational projects. You use the Rational® Administrator to create and manage Rational
Rational Projects
A Rational project stores software testing and development information. All Rational
components on your computer update and retrieve data from the same project.
The types of data in a Rational project depend on the Rational software that you
have installed.
The following table describes each part of a Rational project:
A Rational project
consists of:
Rational Test datastore
Stores application testing information such as test plans, test
cases, test logs, reports, and builds.
If there are multiple, concurrent users (more than one user)
of a test datastore, use a SQL Anywhere database engine for the
test datastore. First install the Sybase SQL Anywhere software.
Then create a SQL Anywhere database server before you create a
new SQL Anywhere test datastore or change an existing
Microsoft Access test datastore to a SQL Anywhere test datastore.
For information about installing SQL Anywhere software and
creating a SQL Anywhere database server, see your Rational
installation manual. To manage a Sybase SQL Anywhere
database server, see the Sybase Help. If you distribute tests to test
agent computers, you must use a shared test datastore. For more
information about security and privileges, see the Rational
Administrator Help.
Rational RequisitePro
Stores product or system requirements, software and hardware
requirements, and user requirements. When you associate a
RequisitePro datastore with a project in the Administrator,
TestManager automatically uses the requirements in the
datastore as test inputs.
Rational Rose models
Stores visual models for business processes, software
components, classes and objects, and distribution and
deployment processes. You can use Rose model elements as test
inputs. To use Rose model elements, you must register the source
of the model with TestManager. For information, see Built-In Test
Input Types
on page 29