Pipelines in ALM Octane represent the jobs or steps that run on your CI server. ALM Octane incorporates data from your pipelines into your application delivery process, helping you analyze quality, progress, change impact, code coverage and more. In this attached document, we will look into the integration between ALM Octane and Azure DevOps pipelines.
Recently I have been on different engagements, where JMeter Load/Performance Testing were part of a continuous integration (CI) pipeline. On other engagements, JMeter Load/Performance Testing were not part of any continuous Integration pipeline. In both cases, we were successful connected ALM Octane with JMeter (with a CI pipeline and without). In the following, I will explain 2 different approaches on how to integrate JMeter with ALM Octane.
Easiest way to integrate a testing tool into ALM Octane is to use a continuous integration (CI) Integration – basically if the testing tool can talk to the CI (such as Jenkins) through a framework (such as Junit), we can say with high probability that ALM Octane will understand this communication – in some cases the XML provided by the testing tool need to be transformed into the correct format. The first approach would be to integrate the testing tool with the CI. From the CI, ALM Octane will push the test results to its workspaces.
In any case, if the organization is not consuming CI pipelines to deliver performance testing, also for this through a valid Junit XML the results can be pushed to ALM Octane using a test run collection tool.