...
The configuration is performed by the Parasoft administrator and only needs to be set up once. Developers, testers, and other DTP end users should review the Usage section for instructions on how to use Parasoft with TeamForge.
| Anchor | ||||
|---|---|---|---|---|
|
- Choose Report Center Settings from the settings (gear icon) drop-down menu.
- Choose External Application from the Administration sidebar and choose TeamForge from the Application Type drop-down menu.
- Enable the Enabled option.
- Enter a name for your instance of TeamForge in the Name field. The name is required, but it does not affect the connection settings or render in any other interfaces.
- Enter the TeamForge URL in the Application URL field.
- The Display URL field is rendered in DTP interfaces when links to your TeamForge system are created.
- Enter login credentials in the Username and Password/API Tokens fields. The login must have sufficient privileges to create issues in the TeamForge projects specified in the Project Associations section.
- Click Test Connection to verify your settings and click Save.
| Anchor | ||||
|---|---|---|---|---|
|
Create links between Parasoft and TeamForge projects so that defects created in the Violations or Test Explorer view are created in the correct project in TeamForge. The association is also important when using the the Sending Test Data to External Application flow.
...
You can associate multiple projects in DTP with a project in TeamForge, but you cannot associate the same DTP project with more than one TeamForge project.
| Anchor | ||||
|---|---|---|---|---|
|
You can configure DTP to generate widgets and reports that help you demonstrate traceability between the work items stored in TeamForge and the test, static analysis, and build review data sent to DTP from Parasoft tools (C/C++test, dotTEST, Jtest, SOAtest).
...
Use DTP Extension Designer to deploy the External Application Traceability Report and the Sending Test Data to External Application flow to your environment. Verify that DTP is connected to TeamForge as described in the Connecting DTP to TeamForge Server section before deploying the artifact.
| Anchor | ||||
|---|---|---|---|---|
|
The first step is to install the Traceability Pack. The artifact is a collection of configuration files and assets that enable traceability.
- Choose Extension Designer from the settings menu (gear icon).
- Click the Configuration tab to open Artifact Manager.
- Click Upload Artifact and browse for the external-app-traceability-report-<version>.zip archive (also see Downloading and Installing Artifacts).
- Click Install and a collection of assets and configuration files for enabling traceability will be installed.
| Anchor | ||||
|---|---|---|---|---|
|
Deploy the External Application Traceability Report after installing the Traceability Pack.
...
Deploying the External Application Traceability Report adds new widgets to Report Center, as well as a drill-down report. See Viewing the Traceability Report for instructions on adding the widgets and viewing the report.
| Anchor | ||||
|---|---|---|---|---|
|
This artifact sends test data to TeamForge when DTP Data Collector retrieves test results from a Parasoft tool. This artifact ships with the Traceability Pack, which must be installed as described in Installing the Traceability Pack before deploying the flow.
...
| teamForge.defect.status | Specifies the status of defects that are created in TeamForge when creating work items in the DTP Violations Explorer and Test Explorer views. Default: |
|---|---|
| teamForge.tasks.status | Specifies the status of tasks that are created in TeamForge when creating work items in the DTP Violations Explorer and Test Explorer views. Default: |
| teamForge.workItemType.defect | Specifies the type of work item to create in TeamForge when creating new defects from the DTP Violation Explorer and Test Explorer. This enables you to associate custom defect trackers you may have configured in TeamForge with work items created from DTP. By default, the property is not set. As a result, defect work items created in DTP are associated with task work items in TeamForge. |
| teamForge.workItemType.task | Specifies the type of work item to create in TeamForge when creating new tasks from the DTP Violation Explorer and Test Explorer. This enables you to associate custom task trackers you may have configured in TeamForge with work items created from DTP. By default, the property is not set. As a result, task work items created in DTP are associated with task work items in TeamForge. |
| teamforgeIssueUrl | Specifies the URL template for linking work items created in the DTP Violation Explorer and Test Explorer to work items in TeamForge. Default:
|
| teamForge.trackerType.requirement.name | Specifies the name of TeamForge work item types that should take the role of requirements in Parasoft. The work items are also used in the Traceability Report. Default: |
| teamForge.trackerType.test.name | Specifies the name of TeamForge work item types that should take the role of tests in Parasoft. The work items are also used in the Traceability Report. Default: |
| teamForge.trackerType.test.status.pass | Specifies the test run status name in TeamForge to assign to passing test results sent from DTP. This enables you to set custom statuses you may have configured in TeamForge for test results in DTP. Default: |
| teamForge.trackerType.test.status.fail | Specifies the test run status name in TeamForge to assign to passing test results sent from DTP. This enables you to set custom statuses you may have configured in TeamForge for test results in DTP. Default: |
| Anchor | ||||
|---|---|---|---|---|
|
After configuring the integration with TeamForge, developers, testers, and other users can leverage the functionality enabled by the integration.functionality enabled by the integration.
Anchor Manually Creating Defects and Tasks in TeamForge Manually Creating Defects and Tasks in TeamForge
Manually Creating Defects and Tasks in TeamForge
| Manually Creating Defects and Tasks in TeamForge | |
| Manually Creating Defects and Tasks in TeamForge |
The Test Explorer and Violations Explorer views enable you to create defects and tasks for any test and violation, respectively, regardless of status. Refer to the following sections for details on creating TeamForge assets in explorer views:
- See Creating an Issue in a Third-party System for instructions on how to manually create defects and tasks in TeamForge from the Violations Explorer view.
- See Creating an Issue in a Third-party System for instructions on how to manually create defects and tasks in TeamForge from the Test Explorer view.
Anchor Sending Test Data to TeamForge Sending Test Data to TeamForge
Sending Test Data to TeamForge
| Sending Test Data to TeamForge | |
| Sending Test Data to TeamForge |
TeamForge work items are assets that represent a story, defect, or set of tests. Annotate the test code executed by your Parasoft tool with the TeamForge work item ID using @test or @req annotation. By default, the @test annotation will associate Parasoft tests with TeamForge tests and the @req annotation will associate Parasoft tests with TeamForge stories (see Advanced Configuration for instructions on how to change these settings). Refer to your Parasoft tool documentation for details on adding associations and the TeamForge documentation for information about getting work item IDs. The following diagram shows how you could implement an automated infrastructure for integrating Parasoft into your TeamForge environment:
...
| Code Block | ||
|---|---|---|
| ||
{
"createdTestSession":"DTPP-521",
"created" : [
"DTPP-519, testName = testBagSumAdd"
],
"updated" : [
"Test:1545 for AT-01053, testName = test_quoteGhsLine_Exp_Act_3",
"Test:1546 for AT-01054, testName = test_quoteGhsLine",
"Test:1554 for AT-01056, testName = test_quoteGhsLine_Exp_Act_10",
"Test:7177 for S-01045, testName = test_quoteGhsLine_moreThanOne"
],
"ignored" : [
"MAGD-567, testName = testBagNegate",
"QAP-512, testName = testTryThis3",
"QAP-512, testName = testTryThis4",
"MAGD-567, testName = testBagMultiply"
]
} |
| Anchor | ||||
|---|---|---|---|---|
|
After successfully sending the test data to from DTP, you will be able to view results TeamForge assets
...
Refer to the TeamForge documentation for details on using TeamForge interfaces.
| Anchor | ||||
|---|---|---|---|---|
|
If the External Application Traceability Report has been deployed to your system (see Enabling the Traceability Report), you can add widgets to your dashboard to monitor traceability from work items to tests, static analysis, code reviews for your project. The widgets also drill down to a report that includes additional details.
...
Clicking on a section of the Pie widget opens a version of the report that includes only the quality activity type selected in the widget. You can use the drop-down menus to switch type and status.
| Anchor | ||||
|---|---|---|---|---|
|
The Requirement Details report provides additional information about the files, static analysis findings, and tests associated with a specific TeamForge work item. Stories marked as Dead will not appear in the Traceability Report. The Traceability Report shows information about the following TeamForge work items:
...