Parasoft Team Server manages the team-wide distribution and sharing of SOAtest test configurations, rules, rule mappings, suppressions, skipped resources, code review tasks, and test results. All team Parasoft 9.x tools should be connected to Team Server to enable centralized administration and application of test practices.
In this section:
Prerequisites
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.
Connecting to Team Server
Perform the following procedure on every instance of SOAtest used by the team:
- Choose Parasoft> Preferences to open the Preferences dialog.
- Select the Parasoft> Team Server category in the left pane.
- Enable the Enable Team Server option and enter the following settings:
- Enter your Team Server’s host (either a name or an IP address) in the Host name field.
- Enter your port in the Port number field.
- If your team requires users to log in to Team Server, enable the Enable account login option and then enter your Team Server username and password in the appropriate fields. Depending on how your Team Server was configured, each team member might have a unique Team Server username and password, or all developers might share a single "generic" account.
- Click Test Connection to verify the connection to Team Server.
- If you want to minimize the number of operations on Team Server by reusing cached data, check Enable cache mode.
- This can improve performance, but there is a small risk that outdated rules or Test Configurations could be distributed (if the file was updated since the caching, which is set to occur every 8 hours by default). If a file has been updated since the caching, users can force a refresh by clicking Refresh.
- Click Apply to apply your settings.
- Click OK to set and save your settings.
Extending the Team Server Timeout Period
By default, Parasoft 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:
- For the standalone: Start the tool using the argument
-J-Dparasoft.tcm.timeout=[timeout_in_seconds] For the plugin: Start the tool using the argument
-vmargs -Dparasoft.tcm.timeout=[timeout_in_seconds]
Exporting Team Data
You may occasionally want to export team data. You can copy:
- All data from one Team Server account to another (with or without transforming the paths to use a new location).
- Suppressions and resource data from one location to another within the same Team Server account.
To export team data:
- Open the Team Server page in the Preferences panel.
- Click Export Team Data.
- Use the available controls to specify what data you want exported, where you want it exported, and whether you want paths to be transformed during export.
Export Use Cases
Exporting Team Server data may be especially useful in the following situations.
Renaming IDE projects
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:
Creating a new version of the general project connected to a new Team Server user
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.
Modifying the project/solution layout
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
.
