Versions Compared

Old Version 1

changes.mady.by.user Chieko Sugizaki

Saved on

compared with

New Version 2

changes.mady.by.user Robert Andelin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space DTPDEVEL and version 2022.1

...

  1. Choose Report Center Settings from the settings (gear icon) drop-down menu.
  2. Choose External System and External System, click Edit Settings, and choose codeBeamer from the System type drop-down menu.
  3. Enable the Enabled option.
  4. Enter a name for your instance of codeBeamer ALM in the Name field. The name is required but does not affect the connection settings or render in any other interfaces.
  5. Enter the URL for the codeBeamer server in the Application URL field. The URL should include the protocol, host, and port number. Do not include paths or parameters.
  6. The Display URL field defines the URL which is displayed in Parasoft DTP pages when links to your codeBeamer system are presented in a web browser. Typically, this should be the same as the above Application URL field. However, it might be different, for example, when you work in a reverse proxy environment and links to codeBeamer from the user's local web browser with Parasoft DTP are different than from the Parasoft DTP server. 
  7. Enter login credentials in the Username and Password/API token fields. The login must have sufficient privileges to create issues in the codeBeamer projects specified in the Project Associations section.
  8. Click Test Connection to to verify your settings and click Saveclick Confirm.

Associating Parasoft Projects with CodeBeamer ALM Projects

...

  1. Choose Extension Designer from the settings menu (gear icon).
    Image RemovedImage Added
  2. Click the Configuration tab to open Artifact Manager.
  3. Click Upload Artifact and browse for the traceability-pack-<version>.zip archive (also see Downloading and Installing Artifacts).
  4. Click Install and a collection of assets and configuration files for enabling traceability will be installed.

...

.test
codeBeamer.import.chunkSize

Specifies the maximum number of test case results sent to codeBeamer in a single run.

Default:

codeBeamer.import.chunkSize=1000 

codeBeamer.tracker.requirements

Specifies the name of a tracker in codeBeamer that contain requirements. This enables you to associate a custom requirements tracker you may have configured in codeBeamer with test results in DTP. The configured tracker also determines which requirements are presented on Traceability report.

Default:

codeBeamer.tracker.requirements=System Requirement Specifications 

"Information" and "Folder" requirement types are ignored in DTP reports. 

Note: This setting is global by default, but it can be used for specific codeBeamer projects by appending the codeBeamer project key to the end of the setting. For example:

codeBeamer.tracker

.requirements.Project-A=System Requirement Specifications

Where "Project-A" is the codeBeamer project key, this setting would only apply to that codeBeamer project. Multiple project-specific versions of this setting can be defined using different keys. Project-specific settings take precedence over global settings.

codeBeamer.tracker.tests

Specifies the name of trackers in codeBeamer that contain test cases which you would like to associate with test results in Parasoft DTP. Separate multiple test trackers with a semi-colon ( ; ).

Specifies the name of a tracker in codeBeamer that contain test cases. This enables you to associate custom test case trackers you may have configured in codeBeamer with test results in DTP. 

Default:

codeBeamer.tracker.tests=Test Cases Parasoft creates a Verifies relationship between a test case and requirement in codeBeamer, so make sure that the Verifies option is enabled for the specific test case and requirements trackers in your codeBeamer configuration. 

Example:

codeBeamer.tracker.tests=Test Cases;Integration Tests

This setting is used to search for test cases in codeBeamer by the following Parasoft DTP functionality :

    • Sending test results from DTP to codeBeamer using /syncTestCases API.
      • Searches for existing test definitions in codeBeamer are based on @test T_ID defined in Parasoft tools. When T_ID is not found, it is ignored.
      • Searches for existing test definitions are related to requirements (found by Parasoft @req) in codeBeamer.
        • Note: When /syncTestCases API does not find a specific Parasoft test definition (corresponding to Parasoft test annotated with @req) in codeBeamer, it creates a new test definition in codeBeamer. It will create this test definition in the first test tracker defined in the codeBeamer.tracker.tests list.
    • Providing requirements and tests hierarchy to be presented in “Requirements View” in C/C++test.

Note: This setting is global by default, but it can be used for specific codeBeamer projects by appending the codeBeamer project key to the end of the setting. For example:

codeBeamer.tracker.tests.Project-A=<TCT1>;<TCT2>;<TCT3>

Where "Project-A" is the codeBeamer project key, this setting would only apply to that codeBeamer project. Multiple project-specific versions of this setting can be defined using different keys. Project-specific settings take precedence over global settings.

Note about codeBeamer configuration:

When a Parasoft test is annotated with @req, it creates an equivalent test case in codeBeamer and a Verifies relationship between test case and requirement is created. To ensure it works correctly, make sure that the "Verifies" option is enabled for the test cases and requirements trackers in your codeBeamer configuration.

codeBeamer.tracker.testRuns

Specifies the name of test run trackers in codeBeamer where DTP should create test runs when sending test results to codeBeamer. This setting is used when sending test results from DTP to codeBeamer using the /syncTestCases API.

Typical use case: Single Test Run Tracker

In most cases, there is only one test run tracker in codeBeamer and you can leave this setting is empty. This is the default. When this setting is empty, DTP creates test runs in the first (and in this case, the only) test run tracker in codeBeamer.

Advanced use case: Multiple Test Run Trackers

If your codeBeamer projects contains multiple test run trackers into which you want to insert test runs from DTP, you can define them in this setting. Separate multiple test run trackers with a semi-colon ( ; ).

Example:

codeBeamer.tracker.testRuns=<TRT1>;<TRT2>;<TRT3>

When you define multiple test run trackers, it is possible to specify a mapping between codeBeamer test case trackers (see codeBeamer.tracker.tests above) and test run trackers in a given project and control where the test runs will be created. For example, let's say you configure the following settings:

codeBeamer.tracker.tests=<TCT1>;<TCT2>;<TCT3>;<TCT4>

codeBeamer.tracker.testRuns=<TRT1>;<TRT2>;<TRT3>

In that situation, when DTP executes the /sendTestCases API and for a specific test case in DTP it finds a test case in codeBeamer (for example, TCT1), its test run will be created in the corresponding test run tracker (in this case, TRT1). The mapping is based on the respective position of the settings, so in our example TCT2 would map to TRT2 and TCT3 would map to TRT3.

If DTP were to find a test case in codeBeamer defined in TCT4, since there is no TRT4 tracker configured in DTP (or if it is configured in DTP, but TRT4 does not exist in codeBeamer), the test run will be created in TRT1 (since it's the first item in the configured test run tracker list).

Note: This setting is global by default, but it can be used for specific codeBeamer projects by appending the codeBeamer project key to the end of the setting. For example:

codeBeamer.tracker.testRuns.Project-A=<TRT1>;<TRT2>;<TRT3>

Where "Project-A" is the codeBeamer project key, this setting would only apply to that codeBeamer project. Multiple project-specific versions of this setting can be defined using different keys. Project-specific settings take precedence over global settings.

codeBeamer.workItemType.bug.status

Specifies the status of bugs that are created in codeBeamer when creating work items in the DTP Violations Explorer and Test Explorer views.

Default: Open 

codeBeamer.workItemType.bug

Specifies the type of work item to create in codeBeamer when creating new bugs from the DTP Violation Explorer and Test Explorer. This enables you to associate custom bug trackers you may have configured in codeBeamer with work items created from DTP. 

By default, the property is not set. As a result, bug work items created in DTP are associated with bug work items in codeBeamer.

codeBeamer.workItemType.task.status

Specifies the status of tasks that are created in codeBeamer when creating work items in the DTP Violations Explorer and Test Explorer views.

Default: Open 

codeBeamer.workItemType.taskSpecifies the type of work item to create in codeBeamer 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 codeBeamer 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 codeBeamer.

codeBeamerIssueUrl

Specifies the URL template for linking work items created in the DTP Violation Explorer and Test Explorer to work items in codeBeamer.

Default:

codeBeamerIssueUrl=<CODEBEAMER_URL>/cb/issue/<ID> 

...