This topic describes how to connect C/C++test to Parasoft Team Server, which supports centralized administration and application of test practices.
Parasoft Team Server is the software that manages the team-wide distribution and sharing of Test Configurations, rules, rule mappings, suppressions, skipped resources, and test results.
Before you proceed with the team deployment, ensure that Team Server is successfully installed and deployed on one of your organization’s machines. If you need information on obtaining, installing, or deploying Team Server, contact your Parasoft representative.
After Team Server is installed and deployed, you need to connect all team machines to that Team Server. If a Parasoft product is not connected to Team Server, Team Server will not provide file/configuration/task sharing and management for that installation.
To connect the team’s Parasoft installations to Team Server, perform the following procedure on every Parasoft product used by the team:
By default, C/C++test waits 60 seconds for a response from Team Server. If a response is not received within this time, it times out.
If you want it to wait longer before timing out, you can extend the timeout as follows:
tcm.timeoutvalue to the registry key
You may occasionally want to export team data. You can copy:
To export team data:
Exporting Team Server data may be especially useful in the following situations.
To ensure that resource data settings and suppressions are still available after renaming a project, you can use the export wizard to copy data with path relocation; for example:
When a new version of project is created in source control (branch), it is recommended that you also create a new Team Server user that will control configurations, rules, suppressions and other data for the given project version.
Initially, the new area on Team Server should be filled from the current project. After creating the Team Server user, you can use the wizard to copy all data from the current user to the new one. This configures Team Server to support two separate areas for two versions of the product.
From this point forward, any changes in configurations, rules, or suppressions in one version will not affect settings in the other version.
For example, assume that your team decides to add artifacts in separate folders: you have all artifacts in /My Project/src/... but you want to have them in /My Project/... To make this move without losing the data on Team Server, you can copy data from /My Project/src to /My Project.