Usage

To use the HCL DevOps Test plug-in, the plug-in must be loaded and an instance created. Load the plug-in into the HCL DevOps Velocity container if necessary.

To install the plug-in, perform the following steps:

1. From the home page, click Settings > Integrations > Available.
2. In the Action column for the HCL DevOps Test plug-in, click Install.

Integration type

The HCL DevOps Test plug-in is a parser type plug-in, and it parses data from the following test tools:

Integration steps

To install the plug-in, perform the following steps:

1. From the home page, click Settings > Integrations > Available.
2. In the Action column for the HCL DevOps Test plug-in, click Install.
   The plug-in is now listed in the Installed tab and available for invoking.

Invoking the plug-in

To invoke the HCL DevOps Test plug-in send an HTTP Post request with the data to parse. Whenever there is a hit to the endpoint, the data is parsed and displayed as metrics in HCL DevOps Velocity. You can use various methods such as Postman, REST calls, CURL, and CI/CD tools like Jenkins to invoke the plug-in endpoints.

Invoke using Jenkins

Install the Jenkin’s UrbanCode Velocity plug-in into your Jenkins server. In your freestyle job or pipeline use the UCV-Upload Metrics File to UrbanCode Velocity step and provide the required fields. This step allows your build job to upload generated coverage results files to HCL DevOps Velocity

pipeline {
   agent any
   stages {
      stage('oneTestMetrics') {
         steps {
            step([$class: 'UploadMetricsFile',  appName: 'My DevOps Test', dataFormat: 'onetestFTJSON', filePath: '<location of the DevOps Test report>', name: 'my-onetest-test', pluginType: 'onetest', tenantId: '<tenant Id>', testSetName: 'onetest', metricsRecordUrl: "${env.BUILD_URL}"])
         }
      }
   }
}

Invoke using a Rest call

When using a REST call to invoke the HCL DevOps Test plug-in, it must be a POST method and include the location of the HCL DevOps Velocity quality data endpoint.

The following request sample shows a REST call that you can copy and update as necessary. Key points about the snippet:

• The URL points to the HCL DevOps Velocity quality data endpoint. Update with the server location for your installation of HCL DevOps Velocity.
• The BODY of the call is a multipart/form data. It includes information about the payload.

METHOD: POST 
URL: https://<url_devopsvelocity_server>/reporting-consumer/metrics
BODY (multipart/form-data):
 {
  payload: <json_object_string> // See below for schema format
 testArtifact: <HCL_DevOps_Test_JSON_file>
 }

The following shows the schema for the payload. Replace the angle brackets with your values for the parameters.

{
  "tenant_id": "<tenant_id>",    // required Tenant ID
  "metricName": "<metric_name>", // optional: name for recurring test set
  "application": {
    "name": "<application_name>"  //Name of application
  },
  "record": {
    "recordName": "<record_name>", // optional: Name for this record
    "executionDate": 1547983466015, // optional: UNIX Epoch
    "pluginType": "onetest",
    "dataFormat": "<data_type>",  // onetestFTJSON or onetestPTJSON or onetestUIJSON
    "metricsRecordUrl": "<Jenkins_build_url>" // optional: To link the Jenkins build with test results
 },
  "build": {  // Optional: One of the following fields must be included 
    "buildId": "<build_id>",
    "jobExternalId": "<external_job_id>",
    "url": "<build_url>",
  },
  "commitId": "<commit_id>",  // optional
  "pullRequestId": "<pullrequest_id>", // optional
  "environment": "<environment_name>" // optional
}

Data format details

• onetestFTJSON is for Functional test results
• onetestPTJSON is for Performance test results &
• onetestUIJSON is for Web UI test results

Invoke using Curl

curl –request POST \
–url https:///reporting-consumer/metrics \
–form ‘payload={
“tenant_id”: “5ade13625558f2c6688d15ce”,
“application”: {
“name”: “My Application”
},
“record”: {
“pluginType”: “onetest”,
“dataFormat”: “onetestFTJSON”
}
}
‘ \
–form testArtifact=@test-result/oneTest.json