You can find information about the features introduced, enhancements, or other changes made in HCL DevOps Test UI (Test UI). You can also find the features that were introduced in previous versions of Test UI. DevOps Test UI is the new name of HCL OneTest™ UI from 11.0.0 onwards.

You can find the defects that are fixed in this version of HCL DevOps Test UI (Test UI). You can also find the defects that were fixed in the earlier versions of Test UI. DevOps Test UI is the new name of HCL OneTest™ UI from 11.0.0 onwards.

You can find the known issues that are identified, if any, in this version of HCL DevOps Test UI (Test UI). You can also find the known issues identified in the earlier versions of Test UI.DevOps Test UI is the new name of HCL OneTest™ UI from 11.0.0 onwards.

HCL DevOps Test UI (Test UI) is an object-oriented automated testing tool that tests a wide range of desktop, Web, and mobile applications. Test UI provides automated testing capabilities for functional, regression, GUI, and data-driven testing.

The diagram in this topic shows the task flow for setting up HCL DevOps Test UI (Test UI).

The tests that you create, and the assets associated with the tests, reside in a project on your desktop. You can create the project separately, or you can simply record a test, which automatically creates a project named testproj.

With the UI Test perspective, you can find information and task flows to create and run functional tests for web applications.

To get started in functional testing, familiarize yourself with some basic concepts and use cases. You can consider several approaches before you start creating the functional test scripts to effectively automate test cases.

You can run integration tests in HCL DevOps Test UI (Test UI) by using Test UI Extension for HCL DevOps Test Integrations and APIs (Test Integrations and APIs). In Test UI, you can create a compound test to run the integration tests by using agents.

You can use the tutorials to get started with testing in the UI Test perspective in HCL DevOps Test UI (Test UI).

You can use the tutorials to get started with testing in the Functional Test perspective in HCL DevOps Test UI (Test UI).

HCL DevOps Test UI (Test UI) tutorials contain educational materials to help you learn the technologies and concepts behind products.

The sample functional test project is created using the first few lessons of the "Create a functional test" tutorial . You can look at the test assets while you do the tutorial or after you complete it.

This is a sample functional test project that contains various functional test scripts for testing an HTML application. In this sample project, the IBM® Rational® Team Concert™ web client is used as an application under test.

Functional testing proxy SDK samples are simple examples of proxy source code and applications under test (AUT).

HCL DevOps Test UI (Test UI) ships with some example code you can use in your own scripts. You can open these examples from within the sample project shipped with Test UI. The sample project was created using the Test UI tutorial. For reference, you can look at the script and other test assets while you do the tutorial, or after you complete the tutorial, if you want to compare the script and test assets to your files or actually play back the script.

HCL DevOps Test UI (Test UI) ships with some example proxy code you can use to learn about proxy SDK. You can open these examples from within the sample projects shipped with Test UI.

You can find information about the installation of HCL DevOps Test UI (Test UI).

Licensing for HCL DevOps Test UI (Test 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.

You can start HCL DevOps Test UI (Test UI) from the desktop environment or a command-line interface.

You can integrateHCL DevOps Test UI (Test UI) with the software configuration management systems to maintain an auditable and repeatable history of your organization's test assets.

In this section, you will learn about the supported integrations for the Web UI Test perspective.

In this section, you will learn about the supported integrations for the Functional Test perspective.

When you develop web applications, Windows-based applications, or mobile applications, you can use HCL DevOps Test UI (Test UI) to create functional tests for these applications. You must first record the tests and then use Test UI to run the tests before you can view the test results.

When you develop Java, HTML, or Terminal-based applications, you can use HCL DevOps Test UI (Test UI) to create traditional functional tests for these applications. You must first record the tests and then use Test UI to run the tests before you can view the test results.

You can use custom code to extend the default Web UI testing capabilities. You can write custom Java™ code and call the code from the test. You can also specify that results from the tests that are affected by your custom code to be included in reports.

You can use custom code to extend the default functional testing capabilities. You can write custom code and call the code from the test. You can also specify that results from the tests that are affected by your custom code to be included in reports.

These topics describe various ways that you can customize HCL DevOps Test UI (Test UI) or use the application programming interface (API) to extend Test UI functionality.

HCL DevOps Test UI (Test UI) contains a set of pre-releases that enable you to test various experimental features. These experimental features, while still in progress, are introduced early in the release to seek your feedback on its overall functionality and performance. You can play around with these capabilities before they are made available and supported as a general feature in an upcoming release.

When you create Web UI, mobile, or Windows tests, you must configure the play back of the recorded tests as test runs from the UI Test perspective before you can view their test results.

When you created functional tests, you must configure the run of the recorded functional tests from the Functional Test perspective before you can view the test results.

The test result indicate the quality of the application under test. There could be different stakeholders to the application who do not have the product installed but want to check the quality of application. You, as the user of the product, can publish the test result to HCL DevOps Test Hub (Test Hub) so that others can view it from the web browser.

If you have a single test result or multiple test results that are not published to HCL DevOps Test Hub (Test Hub), you can publish a single or all of them simultaneously.

Unified reports in HCL DevOps Test UI (Test UI) provide a detailed overview of the test results.

In this section, you will learn how to analyze test results in the Web UI Test perspective.

In this section, you will learn how to analyze test results in the Functional Test perspective.

You can find information about the issues or problems that you might encounter while working with HCL DevOps Test UI (Test UI) in the UI Test perspective. Details about issues, their causes and the resolutions that you can apply to fix the issues are described in this section.

In this section, you will learn how to troubleshoot the tests in the Functional Test perspective.

In this section, you will learn all the reference or additional information about the UI Test perspective.

In this section, you will learn all the reference or additional information about the Functional Test perspective.

You can find the links to view the following API reference guides of HCL DevOps Test UI:

This document describes the actions that you can take to ensure that your installation is secure, customize your security settings, and set up user access controls.