In this section:
scope.local
This setting enables or disables code authorship computation based on the local user and system files modification time.
Acceptable Values
| true | Default. Authorship will be assigned based on the local user. |
|---|---|
| false | Authorship will not be assigned based on the local user. |
Example Usage
The following configuration disables authorship computation based on the local user:
scope.local=false
Related
scope.scontrol
This setting enables or disables code authorship computation based on data from a supported source control system.
Acceptable Values
| true | Authorship will be assigned based on the source control information. |
|---|---|
| false | Default. Authorship will not be assigned based on the source control information. |
Example Usage
The following configuration enables authorship based on source control data:
scope.scontrol=true
Related
scope.scontrol.files.filter.mode
This setting specifies filters that restrict the scope of analysis to a subset of files. The setting is supported for Git SCM.
This setting overrides time filters configured in your test configuration (see Creating Custom Test Configurations).
Acceptable Values
| all | Default. Checks all files in the scope. |
|---|---|
| local | Checks only locally modified files. |
| branch | Checks only files that are different between the current working branch and the reference branch. By default, the reference branch is the main integration stream, such as "master", "trunk", etc. You can specify a custom branch with scope.scontrol.ref.branch. |
Example Usage
The following configuration narrows down the scope of analysis to locally modified files:
scope.scontrol.files.filter.mode=local
The following configuration narrows down the scope of analysis to files that are different between the current working branch and the main stream of development:
scope.scontrol.files.filter.mode=branch
Te following configuration narrows down the scope of analysis to files that are different between the current working branch and branch "feature_372":
scope.scontrol.files.filter.mode=branch
scope.scontrol.ref.branch=feature_372
Related
scope.scontrol.ref.branch
This setting specifies a custom reference branch with which the current working branch is compared to identify and analyze modified files. It applies when the scope.scontrol.files.filter.mode option is set to branch. The setting is supported for Git SCM.
This setting overrides the reference branch configured in your test configuration (see Creating Custom Test Configurations).
Acceptable Values
| [branch] | The branch name or identifier of the reference branch. |
|---|
Example Usage
The following configuration specifies that the current working branch will be compared with branch "US129":
scope.scontrol.files.filter.mode=branch
scope.scontrol.ref.branch=US129
Related
scope.javadoc
This setting enables or disables code authorship computation based on the Javadoc @author tag.
Acceptable Values
| true | Default. Authorship will be assigned based on the @author tag in Javadoc. |
|---|---|
| false | Authorship will not be assigned based on the @author tag in Javadoc. |
Example Usage
The following configuration disables authorship based on the @author tag:
scope.javadoc=false
Related
scope.xmlmap
This setting enables or disables ask assignment based on an XML mapping file that defines how tasks should be assigned to particular files or sets of files. See Creating Authorship XML Map Files for details.
Acceptable Values
| true | Authorship will be assigned based on on an XML mapping file. |
|---|---|
| false | Default. Authorship will not be assigned based on an XML mapping file. |
Example Usage
The following configuration enables authorship based on an XML mapping file:
scope.scontrol=true
Related
scope.xmlmap.file
This setting specifies the path to an XML mapping file that defines how tasks should be assigned to particular files or sets of files.
Acceptable Values
| [path] | The path to the XML mapping file specifies task assignment to files or sets of files. |
|---|
Example Usage
The following configuration specifies that tasks should be assigned to files or sets of files according to the information included in the mapping.xmlfile.
scope.xmlmap.file=C:\\parasoft\\mapping.xml
Related
authors.ignore.case
This setting specifies if author recognition is case sensitive.
Acceptable Values
| true | The case differences are ignored in author names. |
|---|---|
| false | Default. Author recognition is case sensitive. |
Example Usage
The following configuration specifies that case differences in author names are ignored and, for example, "david", "David" and "DAVID" are be considered the same user.
authors.ignore.case=true
Related
authors.mappings.location
This setting specifies where the file that includes the authorship mapping information is stored. The authorship mapping can be configured with the following settings: authors.user{n} and authors.mapping{n}.
Acceptable Values
| local | Default. The authorship mapping information is obtained from a local .properties file. |
|---|---|
| shared | The authorship mapping information will be stored in a file on DTP; see authors.shared.path. |
Example Usage
The following configuration specifies that the information about authorship mapping will be stored on DTP:
authors.mappings.location=shared
Related
authors.shared.path
This setting specifies the path to the authorship mapping file on DTP. Configure this setting when the authors.mappings.location option is set to shared.
Acceptable Values
| [path] | The path to the mapping file on DTP. |
|---|
Example Usage
The following configuration specifies that the authorship mapping information will be shared in the in the authors_map.xml file stored on DTP:
authors.shared.path=xtest/authors_map.txt
Related
authors.user{n}
This setting specifies the user name, email address and the full name of an author.
Acceptable Values
| [user_name, email_address, full_name] | A comma-separated list that specifies the username, email address and full name of a particular user. |
|---|
Example Usage
The following configuration specifies the user details of two authors:
authors.user1=dan,[email protected],Dan Stowe
authors.user2=jim,[email protected],Jim White
Related
authors.mapping{n}
This setting specifies how authors are mapped.
Acceptable Values
| [user_name1, user_name2] | Two comma-separated user names that map an author's user name (user_name1) to another name (user_name2). |
|---|
Example Usage
The following configuration maps the author names from old_user to new_user, and broken_user to correct_user:
authors.mapping1=old_user,new_userauthors.mapping2=broken_user,correct_user
