Home
Administrator Guide
This guide describes how to install HCL OneTest™ UI software. After you install the software, you can perform administration tasks such as license configuration and integration with other products. This guide is intended for administrators.
Integrations in UI Test perspective
In this section, you will learn about the supported integrations for the Web UI Test perspective.
Testing with EGit
You can store your test assets in the remote Git repository and use EGit for version control operations. EGit is an Eclipse plugin for the Git version control system.
Techniques for troubleshooting issues in EGit
You might encounter issues while working with EGit in HCL OneTest™ UI. You can find the information about certain issues and how to resolve them.
Conflict management: errors in assets.xml
In a collaborative work environment, the merge conflicts in assets.xml arise despite best efforts when you pull the changes from the remote upstream.

Administrator Guide
This guide describes how to install HCL OneTest™ UI software. After you install the software, you can perform administration tasks such as license configuration and integration with other products. This guide is intended for administrators.
- Installation
  You can find information about the installation of HCL OneTest™ UI.
- License management
  Licensing for HCL OneTest™ UI is administered through HCL Software License & Download portal. This portal is a FlexNet-based web application that helps to manage software entitlements and licenses.
- Starting HCL OneTest™ UI from the command line
  You can start HCL OneTest™ UI from the desktop environment or a command-line interface.
- Software configuration management
  You can integrateHCL OneTest™ UI with the software configuration management systems to maintain an auditable and repeatable history of your organization's test assets.
- Integrations in UI Test perspective
  In this section, you will learn about the supported integrations for the Web UI Test perspective.
  - Integration plugin compatibility matrix
    You can find information about the versions of the integration plugins that are required to integrate Jenkins, Ant, HCL® Launch, and UrbanCode™ Deploy with HCL OneTest™ UI.
  - Testing with Ant
    You can use Ant to run compound tests and Web UI tests from the command-line interface.
  - Testing with Azure DevOps for UI tests
    When you use Azure DevOps for continuous integration and continuous deployment of your application, you can create tests for your application in HCL OneTest™ UI and run those tests in Azure DevOps pipelines. You can integrate Azure DevOps with HCL OneTest UI by using the HCL OneTest Studio extension that is available in the Visual Studio Marketplace portal.
  - Testing with EGit
    You can store your test assets in the remote Git repository and use EGit for version control operations. EGit is an Eclipse plugin for the Git version control system.
    - Importing test assets from the remote Git repository
      You can import the test assets from the remote Git repository to HCL OneTest™ UI and run it to test the performance of the application.
    - Pulling the changes from the remote Git repository
      You must make your local repository up-to-date by pulling the latest changes in the remote Git repository before you committ and push your updated test assets to the Git repository.
    - Publishing test assets to the remote Git repository
      When you create or update any test assets in HCL OneTest™ UI, you can publish your changes to the remote Git repository. Therefore, when you publish test assets, other members in the project can use your test assets in their test run, if required.
    - Techniques for troubleshooting issues in EGit
      You might encounter issues while working with EGit in HCL OneTest™ UI. You can find the information about certain issues and how to resolve them.
      - Error: Missing library files in the project
        After you pull a project in the Git perspective, Project is missing the required Library error is displayed in the Verify Problems tab. This error occurs due to the .classpath file which is specific to a workspace or system. The .classpath file needs to be pointed to the newly imported location.
      - Git merge conflicts
        Web UI test projects contain certain metafiles and test assets in binary form. When you work in a collaborative test creation environment, you might encounter Git merge conflicts while you commit test assets to the remote Git repository.
      - Conflict management: errors in assets.xml
        In a collaborative work environment, the merge conflicts in assets.xml arise despite best efforts when you pull the changes from the remote upstream.
      - Conflict management: errors in test assets
        When multiple users edit and commit the same set of test assets, then while you pull or push changes to the remote Git repository, a merge conflict occurs.
  - Configuration of test runs as a GitHub Actions Workflow
    You can configure test runs of test resources that are in a project repository of HCL OneTest™ UI in a GitHub Actions Workflow. You can choose to run test resources that are in the project in the GitHub Workflow when you want to run the test resources without opening the HCL OneTest UI.
  - Testing with IBM® Engineering Workflow Management
    You can manage test assets with Jazz™ source control management by integrating the test workbench with IBM® Engineering Workflow Management (formerly known as Rational® Team Concert™) Eclipse client.
  - Testing with Engineering Test Management
    You can integrate IBM® Engineering Test Management (formerly known as IBM Rational® Quality Manager) with HCL OneTest™ UI to initiate test runs from Engineering Test Management.
  - Testing with Jenkins
    You can use the HCL OneTest™ UI - UI Test Jenkins plugin to run tests on a Jenkins server.
  - Testing with Maven
    Starting from 9.2.0, you can use the Maven plug-in that is provided with the testing product to run tests as part of your Maven build. Apache Maven is a software build tool based on the concept of a project object model (POM).
  - Testing with Micro Focus ALM
    You can integrate HCL OneTest™ UI with Micro Focus Application Lifecycle Management (ALM) to run test assets from Micro Focus ALM.
  - Testing with HCL OneTest™ API
    You can use HCL OneTest™ API extension to run API tests from HCL OneTest UI. You can either import the projects from HCL OneTest API or manage them from HCL OneTest UI by establishing the connection between the products. You can also create a compound test to run the tests by using the Agents.
  - Testing with HCL® Launch
    You can integrate HCL OneTest™ UI with HCL® Launch to run tests as a Process from HCL Launch.
  - Testing with UrbanCode Deploy
    With the HCL OneTest™ UI plugin for UrbanCode™ Deploy, you can automate the execution of tests and compound tests.
- Integrations in Functional Test perspective
  In this section, you will learn about the supported integrations for the Functional Test perspective.

Conflict management: errors in assets.xml

In a collaborative work environment, the merge conflicts in assets.xml arise despite best efforts when you pull the changes from the remote upstream.

The project includes a metafile called assets.xml that contains a list of all test asset files in a project along with their dependencies in an XML format. The assets.xml file is automatically generated by HCL OneTest™ UI from the contents of the project. The assets.xml file is refreshed each time you modify the files in the project. These changes in the assets.xml file are the most common source of merge conflicts.

The following image displays the merge conflicts when you attempt to perform a pull request on the local Git repository by using the Git perspective:

merge_conflict

You can perform the following steps to resolve the merge conflicts in the assets.xml file:

Click Close to dismiss the merge conflict result dialog box.
Click Window > Show View > Other.
Expand Git, and then select Git Staging.
Click Open.

The conflicting files are displayed in the Unstaged Changes pane.
Right-click the project from the Test Navigator pane, and then click Refresh.

When you refresh the project, the assets.xml file is updated to include the local files in the project and also files that were pulled down from the remote upstream.
Go to the Git Staging view, and then move the files from Unstaged Changes to Staged Changes by using the Add selected files to the index or icon.
Enter a message in the Commit Message pane, and then click Commit and Push.

The Push Result dialog box is displayed with the status of the commit to the remote Git repository.