Micro Focus ALM Octane

The following provides instructions for triggering Automation test executions from within Micro Focus Application Lifecycle Management (ALM) Octane via a Jenkins CI Server in order to create a host and provide a secure webhook endpoint.

Many Provar customers use Micro Focus ALM and Automation to integrate tests and test results. With this integration, you can store Automation test cases in ALM (with full check out and versioning support) and upload automation results into the ALM Test Lab.

Prerequisites

It’s also worth mentioning that this support article is designed for users with experience setting up Jenkins to run Provar tests under Apache Ant. If you don’t have experience or want to learn more, please refer to Running Provar tests on Jenkins for additional information.

Please feel free to contact us with any feedback or assistance with your setup.

Launch ALM Octane

Step 1: Log in to your Micro Focus account.

Step 2: From the Products tab, select ALM Octane and click the Launch button.

Above: View of the Micro Focus Products tab.

Note: Make a note of the project ID populated within the URL. An example is highlighted in yellow below. You will need to use this later in the process. This is required to connect to the Jenkins server.

Above: View of the project ID.

Generate the Client ID and secret from ALM Octane

Step 3: Go to the Administration console > Spaces.

Step 4: Click the active, default shared space within the left-hand menu and click the API ACCESS tab.

Above: View of the API ACCESS tab.

Step 5: Click the Add API ACCESS button and enter an endpoint name. Jenkins is used in these example screenshots.

Step 6: In Role, select CI/CD Integration. Within the In Workspaces field, select the workspace that you want to connect with Jenkins.

Above: View of the API ACCESS screen.

Step 7: After clicking the Add button, the system will generate the Client ID and the Client Secret. Copy the content and save it in a secure place.

Above: View of the Client ID and Client Secret dialog box.

Set up ALM Octane plug-in in Jenkins

Step 8: Log in to your Jenkins server go to Manage Jenkins > Plugin Manager, and install the Micro Focus Application Automation Tools plugin. A Jenkins server restart is required.

Step 9: Go to Manage Jenkins > Configure system and scroll to ALM Octane CI. This section allows you to configure the plug-in and provide the connection details.

Enter the location of the ALM Octane server. This is the portion of the URL before the project space ID. Enter the Client ID, Secret, and the Jenkins user.

Above: View of the ALM Octane Server Configuration screen.

Step 10: Click the Test Connection button to verify the connectivity.

Add the CI server in the Workspace

Step 11: In ALM Octane, go to the Workspace > DEVOPS tab. Click the Add CI Server button (highlighted in yellow below) and select the CI server from the dropbox. Ensure the connected status displays a green check-mark indicating it was successfully completed. If not, check your connection again in the previous step.

Above: View of the DEVOPS tab within ALM Octane.

Set up a Jenkins job to execute Automation tests

Step 12: Create a new job in Jenkins and set up a build step to execute your Provar build.xml file using Apache Ant.

Above: View of the Jenkins build step.

Step 13: In the Post Build Actions, select the Publish JUnit test result report plug-in and add the JUnit.xml path.

Above: View of the Post-Build Actions screen within Jenkins.

Execute the Jenkins job and check your results

Step 14: Execute your job in Jenkins and check that the operation works correctly when you click the local build option.

Step 15: To execute the job from ALM, go to the ALM Octane console and then Pipelines. Select the Jenkins job you created earlier and click on the Run button.

Above: View of the Pipelines tab within the ALM Octane console.

Step 16: After the execution of the job, the status will be visible in the Overview screen.

Above: View of the Overview screen with job status information.

Step 17: The number of executed tests with status information can be visible within the TESTS tab. Logs can be visible within the LOGS tab.