...
The following tags are supported by default:
- @ASSET
- @PR
- @FR
- @TASK
- @REQ - Can be used in the requirements traceability workflow (see Traceability)
- @TEST - Can be used in the requirements traceability workflow (see Traceability)
...
You can associate tests with development artifacts requirements when checking your test files into your source control system. Include a tag and the artifact ID in the commit comment to associate the test files with the artifact, e.g.:
...
You can customize the tags your team uses to associate a test case with a work item from your ALM, defects, or requirements tracking system (e.g, codeBeamer, Jira, TeamForge, VersionOne, etc.). This allows you to configure the tag to match the language that your organization uses to refer to defects. For instance, some organizations use the term "PR" to refer to a defect. Others use "defect" and would thus prefer to use a custom @defect tag rather than the default @pr tag.
To specify custom tags:By default, @pr is used for associating tests with defects/issues, but you can specify aliases for these tags.
- Choose Parasoft> Preferences.
- Select Parasoft> Issue Tracking Tags.
- Use the available controls to add, modify, or delete tags.
- A tag is followed by one or more values that must be represented by either a single string or a number of strings separated by separator tokens.
- Separator token values can be any permutation of comma-separated lists of strings and white spacewhitespace-separated lists of strings.
...
The tags listed here will be available in SOAtest when you configure the Requirements Tracking options in the test suite editor (when you go to Add a new requirement correlation). See Correlating SOAtest Tests for details.
...