In this section:
This setting enables or disables code authorship computation based on the local user and system files modification time.
| true | Default. Authorship will be assigned based on the local user. |
|---|---|
| false | Authorship will not be assigned based on the local user. |
The following configuration disables authorship computation based on the local user:
scope.local=false
This setting enables or disables code authorship computation based on data from a supported source control system.
| true | Authorship will be assigned based on the source control information. |
|---|---|
| false | Default. Authorship will not be assigned based on the source control information. |
The following configuration enables authorship based on source control data:
scope.scontrol=true
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.
| 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. |
The following configuration enables authorship based on an XML mapping file:
scope.scontrol=true
This setting specifies the path to an XML mapping file that defines how tasks should be assigned to particular files or sets of files.
| [path] | The path to the XML mapping file specifies task assignment to files or sets of files. |
|---|
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
This setting enables or disables excluding files that are automatically generated by Visual Studio, such as code-behind files for .resx or .settings files, from the testing scope. Code-behind files that are not automatically generated by Visual Studio will not be excluded
| true | Enables excluding automatically generated files. |
|---|---|
| false | Default. Automatically generated files will not be excluded. |
This setting specifies if author recognition is case sensitive.
| true | The case differences are ignored in author names. |
|---|---|
| false | Default. Author recognition is case sensitive. |
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
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}.
| 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. |
The following configuration specifies that the information about authorship mapping will be stored on DTP:
authors.mappings.location=shared
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.
| [path] | The path to the mapping file on DTP. |
|---|
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
This setting specifies the user name, email address and the full name of an author.
| [user_name, email_address, full_name] | A comma-separated list that specifies the username, email address and full name of a particular user. |
|---|
The following configuration specifies the user details of two authors:
authors.user1=dan,[email protected],Dan Stowe
authors.user2=jim,[email protected],Jim White
This setting specifies how authors are mapped.
| [user_name1, user_name2] | Two comma-separated user names that map an author's user name (user_name1) to another name (user_name2). |
|---|
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