Page History

This topic explains how you can specify localsettings settings to control options for reporting, task assignment, licensing, and more. Localsettings Local settings can be used to share preferences across a team as well as to apply different groups of settings to different projects and test runs.

...

Setting	Purpose
`build.id`	Specifies a build identifier used to label results. It may be unique for each build but may also label more than one test sessions that were executed during a specified build. Default: build-yyyy-MM-dd HH:mm:ss
`report.active_rules=true\|false`	Determines if the reports contain a list of the rules that were enabled for the test. Default: false
`report.archive=true\|false`	Enables the generation of an additional compressed archive (.zip) file in the specified report location. The ZIP file contains all the files generated to build the report. This option can generate an archive for any report format (e.g., HTML, CSV, PDF, etc.). By generating an archive, you can also perform custom transformations of the report because all of the elements are generated to the specified destination folder. Default: false
`report.associations`	Specifies whether the report shows requirements, defects, tasks, and feature requests that are associated with a test. Default: false
`report.authors_details`	Determines whether the report includes an overview of the number and type of tasks assigned to each team member. Default: true
`report.contexts_details`	Determines whether the report includes an overview of the files that were checked or executed during testing. Default: false
`report.custom.extension` `report.custom.xsl.file`	Specifies the location and extension of the XSL file for a custom format. Used with `report.format=custom` For details and examples, see Configuring Reporting Settings.
`report.developer_errors=true\|false`	Determines whether manager reports include details about team member tasks. Default: false
`report.developer_reports=true\|false`	Determines whether the system generates detailed reports for all team members (in addition to a summary report for managers). Default: true
`report.format=html\|pdf\|sate\|xunit\|custom`	Specifies the report format. Default: html
`report.generate_htmls=true\|false`	Determines whether HTML reports are generated and saved on the local file system. XML reports are generated and saved regardless of this setting’s value. Default: true
`report.graph.cs_start_date=[MM/dd/yy]`	Determines the start date for trend graphs that track static analysis tasks over a period of time.
`report.graph.ue_coverage_start_date=[MM/dd/yy]`	Determines the start date for trend graphs that track coverage over a period of time.
`report.graph.ue_start_date=[MM/dd/yy]`	Determines the start date for trend graphs that track test execution results over a period of time.
`report.location_details=true\|false`	Specifies whether absolute file paths are added to XML data. This needs to be enabled on the Server installation if you want to relocate tasks upon import to desktop installations. Default: false
`report.mail.attachments=true\|false`	Determines whether reports are sent as attachments. All components are included as attachments; before you can view an HTML report with images, all attachments must be saved to the disk. Default: false
`report.mail.cc=[email_addresses]`	Specifies where to mail comprehensive manager reports. This setting must be followed by a semicolon-separated list of email addresses. This setting is typically used to send reports to managers or architects. It can also be used to send comprehensive reports to team members if such reports are not sent automatically (for example, because authorship is not being determined by Parasoft Test).
`report.mail.compact=trends\|links`	Specifies that you want to email a compact report or link rather than a complete report. If `trends` is used, the email contains a trend graphs, summary tables, and other compact data; detailed data is not included. If `links` is used, the email contains only a link to a report (which is available on Team Server)
`report.mail.domain=[domain]`	Specifies the mail domain used to send reports.
`report.mail.enabled=true\|false`	Determines whether reports are emailed to team members and to the additional recipients specified with the `cc` setting. Remember that each team member with assigned tasks will automatically be sent a report that contains only the assigned tasks. Default: false
`report.mail.exclude=[email_addresses]`	Specifies any email addresses you do not want to receive reports. This set-ting is used to prevent automated sending of reports to someone that worked on the code, but should not be receiving reports.
`report.mail.exclude.developers=true\|false`	Specifies whether reports should be mailed to any team member whose email is not explicitly listed in the `report.mail.cc` property. This setting is used to prevent reports from being mailed to individual team members. Default: false
`report.mail.format=html\|ascii`	Specifies the email format. Default: html
`report.mail.from=[email_address OR user_name_of_the_same_domain]`	Specifies the "from" line of the emails sent. Default: `<global_user_name>`
`report.mail.include=[email_addresses]`	Specifies the email addresses of team members that you want to receive individual reports. This setting must be followed by a semicolon-separated list of email addresses. This setting is typically used to send individual reports to team members if such reports are not sent automatically (for example, because the team is not using a supported source control system). It overrides team members specified in the 'exclude' list.
`report.mail.on.error.only=true\|false`	Determines whether reports are sent to the manager only if a task is generated or a fatal exception occurs. Team member emails are not affected by this setting; individual emails are sent only to team members who are responsible for reported tasks. Default: false
`report.mail.port=[port]`	Specifies the mail server host’s port number. Default: 25
`report.mail.security=[SL\| STARTTLS\| NONE]`	Specifies the desired security. Available settings are SSL, STARTTLS, NONE. SSL is not available in Visual Studio.
`report.mail.server=[server]`	Specifies the mail server used to send reports.
`report.mail.subject=My New Subject`	Specifies the subject line of the emails sent. The default subject line is ${tool_name} Report - ${config_name}. For example, if you want to change the subject line to "Jtest Report for Project A", you would use `report.mail.subject=jtest Report for Project A` Default: `${tool_name} Report - ${config_name}`
`report.mail.time_delay=[server]`	Specifies a time delay between emailing reports (to avoid bulk email restrictions). Default: 0
`report.mail.unknown=[email_address OR user_name_of_the_same_domain]`	Specifies where to mail reports for errors assigned to "unknown".
`report.mail.username=[username] report.mail.password=[password] report.mail.realm=[realm]`	Specifies the settings for SMTP server authentication. The `realm` value is required only for those servers that authenticate using SASL realm.
`report.metrics_details=true\|false`	Determines whether an XML report with metrics summary information (as well as individual class and method detail data where applicable) is produced. This report will be generated only when a metrics-enabled Test Configuration is run. Metrics details will be shown in HTML and PDF reports. Default: true
`report.setup.problems=top\|bottom\|hidden`	Determines whether reports include a section about setup problems. `top` - Adds a "Setup Problems" section to the top of the report. This is the default. `hidden` - Prevents a "Setup Problems" section from being added. `bottom` - Adds a "Setup Problems" section to the bottom of the report. Default: bottom
`report.suppressed_msgs=true\|false`	Determines whether reports include suppressed messages. Default: false
`report.test_params=true\|false`	Determines whether reports include test parameter details. Default: false report.test_suites_only=true\| false Determines whether the Test Suite Summary report section only lists the .tst files (with this option enabled) or displays a tree-like view of the individual tests in each .tst file (with this option disabled). SOAtest only Default: true
`report.ue_coverage_details_htmls=[coverage_type]`	Determines whether a test's HTML report links to another report that includes source code annotated with line-by-line coverage details. The following values can be used for [coverage_type]: LC - for line coverage SC - for statement coverage (C/C++test only) BCC - for block coverage (C/C++test only) DC - for decision coverage (C/C++test, Jtest only) SCC - for simple condition coverage (C/C++test only) MCDC - for MC/DC coverage (C/C++test only)
`session.tag=[name]`	Specifies a session tag used to label these results. This value is used for uploading summary results to Team Server. The tag is an identifier of the module checked during the analysis process. Reports for different modules should be marked with different tags. Default: `${config_name}`
tasks.source.control.details=true\|false	This setting specifies if additional information from source control, such as revisions and comments, is included in the report.

Parasoft DTP / Project Center Settings

Setting	Purpose
`dtp.autoconfig=true\|false`	Enables autoconfiguration with Parasoft Test settings stored on the DTP server. Default: false
`dtp.enabled=true\|false`	Determines whether the current C++testt is connected to DTP. Default: false
`dtp.user=[username]`	Specifies the username for DTP user authentication.
`dtp.password=[password]`	Specifies the password for DTP user authentication.
`concerto.reporting=true\|false`	Determines whether the current Parasoft Test product C/C++test is connected to Parasoft Project Center. Default: false
`dtp.server=[server]`	Specifies the host name of the Parasoft DTP server.
`concerto.data.port=[port]`	Specifies the Parasoft Project Center port. Default: 32323
`dtp.port=[port]`	Specifies the Parasoft DTP server port. Default: 80
`dtp.user_defined_attributes=[attributes]`	Specifies the user-defined attributes for Parasoft Project Center. Use the format `key1:value1; key2:value2` For more details on attributes, see Connecting to Project Center.
`concerto.log_as_nightly=true\|false`	Determines whether the results sent to Parasoft Project Center are marked as being from a nightly build. Default: false
`concerto.use_resource_attributes=true\|false`	Determines whether Parasoft Project Center attributes specified in the GUI at the project level should be used. This allows you to disable project-level Parasoft Project Center attributes. Default: true
`dtp.project=[project_name]`	Specifies the name of the DTP project that you want these results linked to. For more details on general projects, see Connecting to Project Center. Default: Default Project

Team Server Settings

Setting	Purpose
`tcm.server.enabled=true\|false`	Determines whether the current Para-soft Test product C/C++test is connected to the Parasoft Team Server. Default: false
`tcm.server.name=[name]`	Specifies the machine name or IP address of the machine running Team Server.
`tcm.server.port=[port]`	Specifies the Team Server port number. Default: 18888
`tcm.server.accountLogin=true\|false` `tcm.server.username=[username]` `tcm.server.password=[password]`	Determines whether username and password are submitted to connect to Team Server. Usernames/passwords are not always needed; it depends on your team’s setup. If the first setting is `true`, the second and third settings specify the username and password. Note that Team Server must have the username and password setting already enabled before these settings can be used. tcm.server.accountLogin default: false

...

See Manually Adding the License to localsetttings for additional notes and examples.

Setting	Purpose
`[product]cpptest.license. use_network=true\|false`	Determines whether the current Parasoft Test product C/C++test retrieves its license from LicenseServer. Be sure to replace `[product]` with the name for the appropriate Parasoft Test product (for example, `jtest, cpptest, dottest, soatest`). Example: jtestExample: `cpptest.license.use_network=true` Default: true
`[product]cpptest.license. network.host=[host]`	Specifies the machine name or IP address of the machine running LicenseServer License Server Configuration Manager. Example: `cpptest.license.network.host=10.9.1.63`
`[product]cpptest.license. network.port=[port]`	Specifies the LicenseServer License Server port number. Example: `soatestcpptest.license.network.port=2222` Default: 2002
`[product]cpptest.license.` `network.edition=[edition_name]`	Specifies the type of license that you want this Parasoft Test product C/C++test to retrieve from LicenseServerLicense Server. `[edition_name]` can be `serverautomation_edition`. To use a custom edition, do not set anything after the `"=";` simply leaving the value empty. Example: `dottestcpptest.license.network.edition=desktop_edition` `dottestcpptest.license.network.edition=serverautomation_edition` Default: custom_edition
`[product]cpptest.license. autoconf.timeout=[seconds]`	Specifies the maximum number of seconds the Parasoft Test product C/C++test will wait for the license to be automatically configured from LicenseServerLicense Server. Default: 20
`[product]cpptest.license.` `local.expiration=[expiration]`	Specifies the local license that you want this Parasoft Test product C/C++test to use. Default: 0
`[product]cpptest.license. local.password=[password]`	Specifies the local password that you want this Parasoft Test product to C/C++test to use.
`[product]cpptest.license.wait.for.tokens.time=[time in minutes]`	Specifies the time that this Parasoft Test product C/C++test will wait for a license if a license is not currently available. For example to make C++test wait 3 minutes for license tokens, use `cpptest.wait.for.tokens.time=3.` Default: 0

...

Setting	Purpose
`authors.mappings.location=team\|local\|shared`	Specifies where the authorship mapping file is stored. This setting defaults to `team` unless `local` or `shared` is specified. If set to `local` (recommended), authorship mappings can be set directly in localsettings. See `authors.mapping` and `authors.user{n}` for details. If set to `shared`, you can store map-pings in a local file using the `authors.mappings.file` option. The `team` and `shared` options are deprecated. Files specified by these options should be in the previously-used format of: `#author to author` `user1=user3` `user2=user3` `#author to email` `[email protected]` Default: team
`authors.mapping{n}=[from_user, to_user]`	Specifies a specific author mapping for `authors.mappings.location=local`, as described above. For example: `authors.mappings.location=local` `authors.mapping1=baduser,gooduser` `authors.mapping2=brokenuser,fixeduser` `authors.mapping3=olduser,newuser`
`authors.user{n}=[username, email, full_name]`	Specifies a specific author name and email for `authors.mappings.location=local`. For example: `authors.user1=dan,[email protected],Dan Stowe` `authors.user2=jim,[email protected],Jim White`
`authors.mappings.file=[path]`	Specifies the location of a "shared" file as described in `authors.mappings.location` above. For example: `authors.mappings.file=/home/user/dev/temp/author_mapping1.txt`
`authors.ignore.case=true\|false`	Determines whether author names are case sensitive. If true, David and david will be considered the same user. If false, David and david will be considered two separate users. Default: false
`scope.sourcecontrol=true\|false`	Determines whether code authorship is computed based on a data from a supported source control system. Default: false
`scope.author=true\|false`	Determines whether code authorship is computed based on Javadoc @author tags. Jtest only Default: true	`scope.local=true\|false`	Determines whether code authorship is computed based on the local user. Default: true
`scope.recommended.computation=first\|random`	Determines how Parasoft Test C/C++test selects the Recommended Tasks for each team member—it can choose n tasks at random (the default) or select the first n tasks reported (n is the maximum number of tasks that Parasoft Test C/C++test is configured to show each team member per day)
`scope.xmlmap=true\|false`	Determines whether task assignment is computed based on XML files that define how you want tasks assigned for particular files or sets of files (these mappings can be specified in the GUI then saved in an XML file). Default: true
`scope.xmlmap.file=[file]`	Specifies the name of the XML file that defines how you want tasks assigned for particular files or sets of files.

...

Info

icon	false
title	Defining multiple repositories of the same type

Indexes (numbered from 1 to n) must be added to the prefix if you want to define more than one repository of the same type. For example:

scontrol.rep1.type=ccase
scontrol.rep1.ccase.vob=/vobs/myvob1

scontrol.rep2.type=ccase
scontrol.rep2.ccase.vob=/vobs/myvob2

If you are defining only one repository, you do not need to use an index. For example:

scontrol.rep.type=ccase scontrol.rep.ccase.vob=/vobs/myvob1

...

AccuRev Repository Definition Properties

...

Property	Description
`scontrol.rep.type=serena`	Serena Dimensions repository type identifier.
`scontrol.serena.dmroot=`	Path to the Serena Dimensions executable (e.g., `scontrol.serena.dmroot=C\:\\Program Files (x86)\\Serena\\Dimensions 2009 R2\\CM\\`)
`scontrol.rep.serena.login=`	Login name.
`scontrol.rep.serena.password=`	Password.
`scontrol.rep.serena.host=`	Serena Dimensions server host name.
`scontrol.rep.serena.dbname=`	Name of the database for the product you are working with.C/C++test
`scontrol.rep.serena.dbconn=`	Connection string for that database.
`scontrol.rep.serena.locale=`	The language used (e.g., `scontrol.rep.serena.locale=en_US`).
`scontrol.rep.serena.mapping=`	If the project has been downloaded/moved to a location other than default work area, use this option to specify a mapping between the project (or stream) with the Serena repository and the local project. If you are working in the default work area, you do not need to define mappings.

...

, dottest, soatest).

Setting	Purpose
`report.rules=[url_path_to_rules_directory]`	Specifies the directory for rules html files (generated by clicking the `Printable Docs` button in the Test Configuration’s Static Analysis tab). For example: `report.rules=file:///C:/Temp/Burt/parasoft/xtest/gendoc/report.rules=../gendoc/` Default: none
`tasks.clear=true\|false`	Clears existing tasks upon startup in cli mode. This prevents excessive time being spent "loading existing results." Default: true
`console.verbosity.level=low\|normal\|high`	Specifies the verbosity level for the Console view. Available settings are: `low`: Configures the Console view to show errors and basic information about the current step’s name and status (done, failed, up-to-date). `normal`: Also shows command lines and issues reported during test and analysis. `high`: Also shows warnings. Default: low
`[product]cpptest.custom.rules.dir=[directory]`	Indicates where user-defined rules are saved.Be sure to replace `[product]` with the name for the appropriate Parasoft Test product (for example, jtest,
`cpptest`	`[product].custom.configs.dir=[directory]`	Indicates where user-defined Test Configurations are saved. Be sure to replace `[product]` with the name for the appropriate Parasoft Test product (for example, `jtest, cpptest, dottest, soatest`).
`custom.compilers.dir=[directory]`	Overrides the custom compiler directory settings (found in Parasoft> Configurations> Custom compilers) and uses the defined directory to search for custom compilers. C/C++test only.
`exec.env=[env1; env2; ...]`	Specifies a list of tags that describe the environment where a test session was executed. Tags could describe an operating system (e.g. Windows, Linux), an architecture (e.g. x86, x86_64), a compiler, a browser, etc. These tags describe a complete test session; more environment details could be also added at the test suite, test, or test case levels via the services API.
`issue.tracking.tags=[value]`	Specifies custom issue tracking tags. Multiple tags can be separated by a comma. For example: `[email protected],@pr ,@fr` For more details, see Indicating Code and Test Correlations.
`parallel.mode=Manual\|Auto\|Disabled`	Determines which of the following modes is active: Auto: Allows Parasoft Test C/C++test to control parallel processing settings. Manual: Allows you to manually configure parallel processing settings to suit your specific needs. Disabled: Configures Parasoft Test to C/C++test to use only one of the available CPUs. For more details on this and other parallel processing options, see Configuring Parallel Processing. Default: Auto
`parallel.max_threads=<number>`	Specifies the maximum number of parallel threads that can be executed simultaneously. The actual number of parallel threads is determined based on the number of CPUs, available memory, and license settings. Default: [available_processors]
`parallel.free_memory_limit=<percentage>`	Specifies the amount of memory that should be kept free in low memory conditions (expressed as a percentage of the total memory available for the application). This is used to ensure that free memory is available for other processes. Default: 25
`parallel.no_memory_limit=true\|false`	Indicates that you do not want to place any restrictions (beyond existing system limitations) on the memory available to Parasoft Test. Default: false

...

datasources.jdbc.classpath=[path1];[path2];[path3] ...

...

Specifies the location of JDBC driver jar files and class folders.

Special characters (spaces, slashes, colons, etc.) must be escaped; for instance:

%20 = SPACE
%3A = :
%5C = \
%7B = {
%7D = }
%24 = $

If listing multiple jars, use \n as a delimiter.

For example, C:\temp\withspace\${example}\jar.jar

becomes

C%3A%5Ctemp%5Cwith%20space%5C$2 4%7Bexample%7D%5Cjar.jar\n

...

system.properties.classpath=[path1];[path2];[path3] ...

...

Specifies which jar files and class folders are in the classpath. For example:

system.properties.classpath=C\:\\myjars\\myLib1.jar;C\:\\myjar s\\myLib2.jar

...

browsertest-
ing.asynchronous_request_timeout=[seconds]

...

Specifies the default length of delay (in seconds) after which SOAtest should stop waiting for traffic to complete loading and consider it to be
"timed out."

...

browsertest-
ing.allowable_binary_extensions=[extensions]

...

browsertest-
ing.allowable_binary_mimetypes=[mime_types]

...

Additional Options for Virtualize Only

Note that options covered in Additional Options for SOAtest and Virtualize also apply to Virtualize.

...

Exclusions are specified in the format:

traffic.wizard.xpath.ignores=[element name 1]:[value pattern 1];[element name 2]:[value pattern 2];[element name 3]:[value pattern 3]

For example,

traffic.wizard.xpath.ignores=*:[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0- 9]{2}:[0-9]{2}([.][0-9]{1,3})?(([+-][0-9]{2}:[0- 9]{2})|Z)?;uuid:[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}

Note that when the backslash character (\) is used in the regular expression, it needs to be escaped. For example, the regex [\d], which represents a single digit, would be entered as [\\d].

Additional Options for Environment Manager

...

Specifies location of the Environment Manager server. Required

Example: env.manager.server=http://em_hostname:8080/

...

Specifies the name that will be used to label this server on Environment Manager.You can use whatever value will help you identify this server. Optional

Example: env.manager.server.name=MyVirtServerLabel

...

Determines whether the Virtualize server notifies Parasoft Environment Manager when virtual assets are deployed. Optional

Example: env.manager.notify=true

...

Specifies the username for logging into Environment Manager. Optional

Example: env.manager.username=me

...

Specifies the password for logging into Environment Manager. Optional

Example: env.manager.password=12345

Additional Options for Jtest

...

Specifies classpath variables.

For example:

classpath.ECLIPSE_HOME=$(ECLIPSE_HOME)
classpath.ECLIPSE_LIB=$(HOME)/dv/ThirdParty/eclipse/2.1.3/$(PS_ARCH)
classpath.ECLIPSE3_LIB=$(HOME)/dv/ThirdParty/eclipse/3.0.0/$(PS_ARCH)
classpath.THIRD_PARTY=$(HOME)/dv/ThirdParty
classpath.JTEST_CLASSES=$(HOME)/dv/plugins/com.parasoft.eclipse.api.$(os)/jtest/bin/
classpath.JUNIT_JAR=$(HOME)/dv/ThirdParty/junit.jar
classpath.JTEST_ZIP=$(HOME)/dv/plugins/com.parasoft.eclipse.jtestplugin/resources/jtest.jar
classpath.JUNIT_HOME=$(HOME)/dv/ThirdParty

...

com.parasoft.xtest.generation.file.pre= [command]

com.parasoft.xtest.generation.file.post= [command]

com.parasoft.xtest.generation.project.pre= [command]

com.parasoft.xtest.generation.project.post= [command to be run]

...

Specifies commands to be run before or after test generation.

Pre refers to actions performed before test case generation. Post refers to actions performed after test case generation.

File refers to actions performed at the file level. Project refers to actions performed at the project level.

The values for these preferences must be a command that can be passed to Runtime.exec.

Also accepted in this command are the following variables that will be substituted with their values:

${testfile.name}
${testfile.absolutepath}
${testfile.workspacepath}
${testproject.name}
${testfile.exists}

Additional Options for dotTEST

Setting	Purpose
`dottest.aspnet.merge.custom.path.enabled=true\|false`	Enables custom path to aspnet_merge.exe.
`dottest.aspnet.merge.path=[path]`	Specifies a custom path to the aspnet_merge.exe (e.g.: C\:\\Program Files\\Microsoft SDKs\\Windows\\v6.1\\Bin\\aspnet_merge.exe)
`dottest.fxcop.custom.dir.enabled=true\|false`	Enables custom path of FxCop.
`dottest.fxcop.custom.dir=[dir]`	Specifies a custom path to the directory of FxCop, (e.g.: D\:\\Program Files\\Microsoft FxCop 1.36e manag). memory is available for other processes. Default: 25
`parallel.no_memory_limit=true\|false`	Indicates that you do not want to place any restrictions (beyond existing system limitations) on the memory available to Parasoft Test. Default: false

Additional Options for C/C++test

...

Option	Description
`bdf.import.location=[WORKSPACE\|BDF_LOC\|<path>]`	You can specify an external location, or use the keyword WORKSPACE. If WORKSPACE is used, projects will be created in subdirectories within the workspace directory. If BDF_LOC is used and one project will be created, then it will be created in the exact location as the bdf file. If more then one project will be created, then the projects will be created in subdirectories within the bdf file location. Those subdirectories will be named with corresponding projects names. If an external path is specified, then the project will be created in the specified location. WORKSPACE is the default.
`bdf.import.pathvar.enabled=[true\|false]`	Specifies if Path Variables should be used in linked folders that will be created in the new projects. The default is false.
`bdf.import.pathvar.name=<name>`	Specifies the name of the Path Variable (if Path Variables are used, per the bdf.import.pathvar.enabled property). The default Path Variable name is DEVEL_ROOT_DIR.
`bdf.import.pathvar.value=<path>`	Specifies the value of the Path Variable (if Path Variables are used, per the bdf.import.pathvar.enabled property). The default value is the most common root directory for all linked folders.
`bdf.import.compiler.family=<compiler_family>`	Specifies what compiler family will be used (for example, `vc_6_0, vc_7_0, vc_7_1, vc_8_0, gcc_2_9, gcc_3_2, gcc_3_3, gcc_3_4, ghs_4_0`). For a custom compiler, you need to use the custom compiler family identifier, which is the name of the directory containing gui.properties, c.psrc and cpp.psrc files). If this property is not specified, the default values will be used.
`bdf.import.c.compiler.exec=<exec>`	Specifies the executable of the C compiler that will be used in the created project.
`bdf.import.cpp.compiler.exec=<exec>`	Specifies the executable of the C/C++ compiler that will be used in the created project.
`bdf.import.linker.exec=<exec>`	Specifies the executable of the linker that will be used in the created project.
`bdf.import.project.<proj_name>=dir1;dir2;dir3`	Specifies the set of folders to link for the project prj_name. Folders should be specified as a value list of folder paths, separated with semicolons.

...

Setting	Purpose
`gpj.import.location=WORKSPACE\|ORIG\|<path>`	Specifies the location of the imported projects. If WORKSPACE is used, then the project will be created in workspace. If ORIG is used, then the project will be created in the .gpj project location. If an external path is specified, then the project will be created in the specified location. The default value is WORKSPACE.
`gpj.import.linked=true\|false`	Specifies whether the .gpj project source folders are linked into the created Eclipse project. The default value is true.
`gpj.import.subdirs=true\|false`	Applicable when `gpj.import.location=<path>` Specifies whether the project(s) are imported into subdirectories or directly into the specified location. If you want the project(s) imported into subdirectories created in the specified external location, use true. If you are importing only one project and you want it imported directly into the specified external location, use false. The default value is true (subfolders are created for each project imported into in external location).
`gpj.import.pathvar.enabled=true\|false`	Specifies if path variables should be used when creating linked directories (if the above option is set to true). The default value is false.
`gpj.import.pathvar.name=<name>`	Specifies the path variable name. The default value will be used unless you specify a path variable name that points to a different location (for instance, DEVEL_ROOT_DIR). If a project with the specified name is already defined in the Eclipse workspace and it points to a different location than the value passed in the `gpj.import.pathvar.location` property, then Path Variable will not be used; full paths will be used instead. Also the default value of `gpjimport.pathvar.name` will always be DEVEL_ROOT_DIR if the `gpjimport.pathvar.name` property is not specified. If this property is specified with some `<name>`, then that `<name>` will be used as the Path Variable name. The default value is DEVEL_ROOT_DIR.
`gpj.import.pathvar.value=<path>`	Specifies the path variable value. By default, C/C++test calculates the common root for all linked folders.
`gpj.import.compiler.family=name`	Specifies the compiler family (compiler ID)
`gpj.import.c.compiler.exec=name`	Specifies the C compiler executable
`gpj.import.cpp.compiler.exec=name`	Specifies the C++ compiler executable
`gpj.import.linker.exec=name`	Specifies the linker executable

...

Code Block

# REPORTS
 
#Determines whether reports are emailed to developers and to the additional recipients specified with the cc setting.
#Remember that if the team is using CVS for source control and each developer's email address matches his or her CVS username + the mail domain, each developer that worked on project code will automatically be sent a report that contains only the errors/results related to his or her work.

report.mail.enabled=true
 
#Exclude developers emails (true/false) 
report.mail.exclude.developers=false
 
# Append developers errors to manager emails (true/false) 
report.developer_errors=true
 
# Send reports to developers (true|false) 
report.developer_reports=true
 
# Append suppressed messages (true|false) 
report.suppressed_msgs=false
 
#Determines where to mail complete test reports.
#This setting is typically used to send reports to managers or architects.
#It can also be used to send reports to developers if developer reports
#are not sent automatically (for example, because the team is not using CVS). 
[email protected]; ${env_var:USERNAME} @domain.com
 
# mail target for unknown developer errors 
[email protected]
 
#Specifies the mail server used to send reports. 
report.mail.server=mail_server.domain.com
 
#Specifies the mail domain used to send reports. 
report.mail.domain=domain.com
 
#Specify mali from 
report.mail.from=nightly
 
#Specifies any email addresses you do not want to receive reports.
#This setting is used to prevent from automatically sending reports to someone that worked on the code, but should not be receiving reports. This setting is only applicable if the team is using CVS for source control and developer reports are being sent automatically.
report.mail.exclude=developer1;developer2
 
# Specifies the subject line of the emails sent.
report.mail.subject= ${tool_name} Report - ${config_name}
 
# Report test params include (true|false) 
report.test_params=true
 
# Team Server
 
#Determines whether the current installation is connected to the Team Server. 
tcm.server.enabled=true
 
#Specifies the machine name or IP address of the machine running Team Server. 
tcm.server.name=team_server.domain.com
 
#Specifies the Team Server port number. 
tcm.server.port=18888
 
tcm.server.accountLogin=true 
tcm.server.username=user 
tcm.server.password=password 
session.tag= ${config_name}
 
# Parasoft Project Center
 
#Determines the current installation is connected to Parasoft Project Center. 
concerto.reporting=true
 
#Specifies the host name of the Parasoft Project Center server. 
dtp.server=grs_server.domain.com
 
# Specifies the port number of the Parasoft Project Center report collector. 
concerto.data.port=32323
 
# Specifies user-defined attributes for Parasoft Project Center.
#Use the format key1:value1; key2:value2
#Attributes help you mark results in ways that are meaningful to your organization.
#They also determine how results are grouped in Parasoft Project Center and how you can filter results in Parasoft Project Center.
#For example, you might want to label results by project name and/or by project component name. #Each attribute contains two components: a general attribute category name
#and a specific identification value. For example, assume your organization wants to classify results by project.
#You might then use the attribute project:projname1. For the next project, you could use a different
#localsettings file that specified an attribute such as project:projname2.
dtp.user_defined_attributes=Type:Nightly;Project:Project1
 
# Determines whether the results sent to Parasoft Project Center are marked as being from a nightly build.
DTP.log_as_nightly=true
 
# SCOPE
 
#code authorship based on CVS 
scope.sourcecontrol=true
 
#code authorship based on author tag 
scope.author=false
 
#code authorship based on local user 
scope.local=false
 
# LICENSE
 
#override license settings
#jtest#cpptest.license.autoconf.timeout=40
jtestcpptest.license.use_network=true
jtestcpptest.license.network.host=license_server.domain.com 
jtestcpptest.license.network.port=2222
jtestcpptest.license.network.edition=serverautomation_edition
 
# SOURCE CONTROL
 
scontrol.rep1.type=cvs
scontrol.rep1.cvs.root=:pserver:[email protected]_server.domain.com:/home/cvs/scontrol.rep1.cvs.pass=mypassword

Page tree

Versions Compared

Old Version 15

New Version Current

Key