DevOps table name that contains the entity linked to the test results (in the test report payload).

Name of the entity specified in the selected table.

For example, the name of the step, pipeline, artifact, or package.

Test File Paths

(Jenkins tests only)

Path to the generated test result file on the Jenkins server.

This is useful so test reports with attributes that don't conform to JUnit or TestNG implementation, such as JMeter for example, can still be leveraged by DevOps.

Separate multiple files by a comma.

Tool that's running the test.

DevOps table that corresponds to the table name in the DevOps Entity Id setting.

To automatically call a custom subflow that transforms the raw payload received by the tool.

Decision inputs:

Create a decision that specifies the custom subflow to call when the raw payload is received.

Set the conditions to contain fields that would be included in the raw payload.

For example, to call Jenkins BZ Performance Test custom subflow:

Answer: FLow: Jenkins BZ Performance Test

To automatically set test types when more than one type of test is configured in a performance test stage.

This is necessary so the results for the second test type get transformed correctly.

For example, when both a Load performance test and a JUnit performance test are mapped in the same DevOps step, the JUnit test results won't get formatted correctly unless a decision is created.

Create a decision for each type of test in the performance test stage to set the test type.

JUnit test:

• Conditions:
  • Step is Perf Tests
  • Test Result Payload does not contain throughput
  • Test Result Payload does not contain concurrency

• Answer: TestType: JUnit