...
| Table of Contents | ||
|---|---|---|
|
Sending Test Data to Codebeamer
The following diagram shows how you could implement an automated infrastructure for integrating Parasoft DTP and Parasoft test execution tools into your Codebeamer ALM environment:
...
| Code Block | ||
|---|---|---|
| ||
{
"createdTestSession": "DTPP-521",
"created": [
"DTPP-519, testName = testBagSumAdd"
],
"updated": [
"DTPP-519, testName = testBagSumAdd",
"DTPP-518, testName = testBagSimpleAdd"
],
"ignored": [
"MAGD-567, testName = testBagNegate",
"QAP-512, testName = testTryThis3",
"QAP-512, testName = testTryThis4",
"MAGD-567, testName = testBagMultiply"
]
} |
Sending Results from a Specific DTP Project
If you are using the Sending Test Data to External System flow to forward unit and functional test results, data will be sent to Codebeamer for all DTP projects by default. As a result, work items will be updated to include the tests collected for any DTP project that contain annotations matching Codebeamer IDs. You can configure the flow, however, to only send data for a specific project.
...
When the flow executes, only test results for the specified DTP project will be sent to Codebeamer.
Viewing Results in Codebeamer
You will be able to view results in Codebeamer after sending the test data. The following image shows a System Requirement Specifications tracker in Codebeamer. The tracker contains several test cases.
...