...
Info | ||||
---|---|---|---|---|
| ||||
If you are specifying a URL for the artifact (e.g., as a SOAtest test property), that URL will be available as a hyperlink in HTML reports. If want to create hyperlinks and you are specifying artifact associations using only the artifact ID as specified in Associating Tests with Development Artifacts Indicating Code and Test Correlations, you can use local properties to specify how the ID maps to a URL. For example:
|
...
Setting | Description | |||
---|---|---|---|---|
Add absolute file paths to XML data | 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 (as described in Relocating Tasks During Import: Requirements and Limitations). | |||
Session Tagtag | The default is ${dtp_project}-${timeSession tags are unique identifiers for test runs and are used to distinguish specific runs from similar runs in DTP. The results from each of the team’s regular test runs should have a unique tag. Variables can be used as described in Using Preference Settings for Command-Line Execution. For instance, if your team runs static analysis, unit testing, and code review, you might use the session tags Static , Execution , and Code Review . Or, you might use variables such as session.tag=${config_name} or session.tag=${analysis_type} | Build Id Tag | } | .
From localsettings
See Reporting Settings for details.
...