Project overview

A project is a tree representation that contains nodes.

Within the project tree, each node has its own individual Configuration Settings —inherited from its parent node— and can be individually executed.

Project Nodes

The project is your main work area in Rational® Test RealTime.

A project is materialized as a directory in your file system, which contains everything you need to test and analyze your code:

Source code
Test scripts
Analysis and test result files

In the Rational® Test RealTime graphical user interface, a project is organized as follows:

Project node: this node contains any of the following nodes:
- Group node: Allows you to group together several application or test nodes.
- Application node: contains a complete application.
- - Results node: contains your runtime analysis result files, once the application has been executed. Use this node to control the result files in Rational ClearCase or any other configuration management system.
  - Source node: these are the actual source files under test. They can be instrumented or not instrumented .
- Test node: represents a complete test harness, for Component Testing for C and Ada , C++ , or System Testing . A test node containing.
- - Results node: contains your test result files, once the test has been executed. Use this node to control the result files in Rational ClearCase or any other configuration management system.
  - Test Script node: contains the test driver script for the current test.
  - Source node: these are the actual source files under test. They can be instrumented or not instrumented .
- External Command node: this node allows you to execute a command line anywhere in the project. Use this to launch applications or to communicate with the application under test.

Application and test nodes can be moved around the project to change the order in which they are executed. The order of files inside a Test node cannot be changed; for example the test script must be executed before the source under test.

Projects and sub-projects

Projects can contain one or more sub-projects which are actually links to other project directories. The behaviour of a sub-project is the same as a project. In fact, a sub-project can be opened separately as a stand-alone project.

Note Previous versions of the product used Workspaces instead of sub-projects. Workspaces are automatically converted to sub-projects when loaded into the current version of the product.

Here are several examples of the use of super-projects and sub-projects:

In a team, users work on their own projects to develop and test portions of a larger development project. For testing the whole project, a single master project can be created to integrate, build, and test multiple sub-projects in one go.
A single project may contain different sub-projects for different target platforms.

Results Node

By default, each application and test node contains a Results node.

Once the test or runtime analysis results have been generated, this node contains the report files. Right-click the result node or the report files to bring up the Source Control pop-up menu.

If you are not controlling result files in a configuration management system, you can hide the Results node by setting the appropriate option in the Project Preferences.