Micro Focus ALM Octane
The following provides instructions for triggering Provar 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 Provar together to integrate tests and test results. With this integration, you can store Provar test cases in ALM (with full check out and versioning support) and upload automation results into the ALM Test Lab. (For more information, you can refer to our Micro Focus (HP) ALM support article.)
It’s also worth mentioning that this support article is designed for users that already have experience setting up Jenkins to run Provar tests under Apache Ant. If you don’t have experience, or would like to learn more, please refer to Running Provar tests on Jenkins for additional information.
Please feel free to contact us if you have any feedback or need assistance with your setup.
Launch ALM Octane
Step 1: Log in to your Micro Focus account.
Above: View of the Micro Focus login screen.
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 that is 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 on 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 and 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 down 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. Make sure the connected status displays a green check-mark indicating that it was successfully completed. If not, go back and check your connection again in the previous step.
Above: View of the DEVOPS tab within ALM Octane.
Set up a Jenkins job to execute Provar 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 is working 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.
Above: View of the TESTS tab within the ALM Octane console.
Above: View of the LOGS tab within the ALM Octane console.
- General information
- Licensing Provar
- Provar trial guide and extensions
- Using Provar
- API testing
- Behavior-driven development
- Creating and importing projects
- Creating test cases
- Custom table mapping
- Debugging tests
- Defining a namespace prefix on a connection
- Defining proxy settings
- Environment management
- Exporting test cases into a PDF
- Exporting test projects
- Managing test steps
- Namespace org testing
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- Reload Org Cache
- Running tests
- Searching Provar with find usages
- Secrets management and encryption
- Setup and teardown test cases
- Tags and Service Level Agreements (SLAs)
- Test cycles
- Test plans
- Testing browser options
- Tooltip testing
- Using the Test Palette
- Test Palette introduction
- Control test steps
- List compare
- Read test step
- String test steps
- UI Test Steps
- Using custom APIs
- Callable tests
- Data-driven testing
- Page objects
- Block locator strategies
- Introduction to XPaths
- Creating an XPath
- Label locator strategies
- Maintaining page objects
- Mapping non-Salesforce fields
- Page object operations
- Refresh and reselect field locators in Test Builder
- Using Java method annotations for custom objects
- Applications testing
- Database testing
- Document testing
- Email testing
- Mobile testing
- OrchestraCMS Testing
- Salesforce CPQ testing
- ServiceMax testing
- Skuid testing
- Vlocity testing
- Webservices testing
- Introduction to test scheduling
- Apache Ant
- Configuration for sending emails via the Provar Command Line Interface (CLI)
- Continuous integration
- Azure DevOps
- Running a Provar CI task in Azure DevOps
- Configuring the Provar secrets password in Microsoft Azure Pipelines
- Parallel execution in Microsoft Azure Pipelines using multiple build.xml files
- Parallel execution in Microsoft Azure Pipelines using targets
- Parallel execution in Microsoft Azure Pipelines using Test Plans
- Bitbucket Pipelines
- Circle CI
- GitHub Actions
- Running a Provar CI task in GitHub Actions
- Remote Trigger in GitHub Actions
- Parameterization using Environment Variables in GitHub Actions
- Parallel Execution in GitHub Actions using multiple build.xml files
- Parallel Execution in GitHub Actions using Targets
- Parallel Execution in GitHub Actions using Test Plan
- Parallel Execution in GitHub Actions using Job Matrix
- GitLab CI
- Travis CI
- Parallel Execution
- Running Provar on Linux
- Salesforce DX
- Team foundation server
- Version control
- Zephyr Cloud and Server
- Salesforce testing
- Adding a Salesforce connection
- Assert Page Error Messages on Add/Edit Product
- Dynamic Forms
- Internationalization support
- List and table testing
- Salesforce Release Updates
- Salesforce Lightning Testing
- Salesforce Lightning Web Component (LWC) locator support
- Salesforce console testing
- Visualforce Testing
- Testing best practices
- Configurations and permissions
- Error messages
- Licensing, installation and firewalls
- Test Builder and test cases
- Release notes