background image
<< Understanding Projects | Creating an External Command Node >>
<< Understanding Projects | Creating an External Command Node >>

Creating a Group

Graphical User Interface
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 projects and sub-projects:
·
In a team, users work on their own projects to develop and test portions of the
main project. A master project can be used to build and test multiple projects in
one go.
·
A project may contain 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 popup 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.
Creating a Group
The Group node is designed to contain several application nodes. This allows you to
organize workspace by grouping applications together.
This also allows you to build and run a specific group of application nodes without
running the entire workspace.
To create a group node:
1. In
the
Project Explorer, right-click the workspace node or right-click any
application node.
2.
From the pop-up menu, select Add Child and Group.
3. In
the
New Group box, enter the name of the group.
4. Click
OK.
Manually Creating an Application or Test Node
Application nodes and test nodes are the main building blocks of your workspace.
An application node typically contains the source files required to build the
application.
Test nodes contain the source under test, test scripts and any dependency filed
requires for the test.
291