Home
Test Author Guide
This guide describes how to create test scripts and enhances them by applying different test elements such as dataset, variables, and verification points.
Extending the Functional Test perspective
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.
DevOps Test UI proxy SDK
Extend automated functional testing support for your application's user interface controls.
DevOps Test UI architecture
HCL DevOps Test UI (Test UI) can be extended to perform additional functions for which it needs to communicate with the application under test (AUT). To do that Test UI first establishes a communication channel to the AUT which is called enablement.
Process Model
There are two types of HCL DevOps Test UI (Test UI) processes. The application under Test (AUT) processes are known as Test UI server side processes. The recorder, playback, objects inspector, and the IDE (Eclipse or Visual Studio .Net) processes are known as Test UI client side processes.

Test Author Guide
This guide describes how to create test scripts and enhances them by applying different test elements such as dataset, variables, and verification points.
- Tests in the UI 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.
- Tests in the Functional Test perspective
  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.
- Extending the UI Test perspective with custom Java™ code
  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.
- Extending the Functional Test perspective
  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.
  - DevOps Test UI proxy SDK
    Extend automated functional testing support for your application's user interface controls.
    - Introduction to proxy SDK
      With HCL DevOps Test UI (Test UI) proxy software development kit (SDK) you can extend automated functional testing support for your application's user interface controls (GUI test objects), beyond what is provided by Test UI by default. The proxy SDK provides detailed documentation, API references and ready-to-use samples and tutorials on how to extend Test UI to add support for testing new controls. It also helps you to extend already supported controls from the existing domains. You can develop proxies manually or by using the proxy wizards driven approach.
    - DevOps Test UI architecture
      HCL DevOps Test UI (Test UI) can be extended to perform additional functions for which it needs to communicate with the application under test (AUT). To do that Test UI first establishes a communication channel to the AUT which is called enablement.
      - Process Model
        There are two types of HCL DevOps Test UI (Test UI) processes. The application under Test (AUT) processes are known as Test UI server side processes. The recorder, playback, objects inspector, and the IDE (Eclipse or Visual Studio .Net) processes are known as Test UI client side processes.
      - High level interactions
        HCL DevOps Test UI (Test UI) client processes interact with the application under test (AUT) and gather relevant information to perform operations such as recording, playback, and object inspections. This section provides an overview of the interactions between the client processes and the AUT processes. Test UI communicates with the AUT through a shared memory inter process communication (IPC) layer.
      - Proxy model
        HCL DevOps Test UI (Test UI) interacts with application-under-test (AUT) controls through two elements: Proxy objects and Test objects.
      - Application under test interactions
        There are several levels of requests in the test process. In each level there are various interactions between HCL DevOps Test UI (Test UI) and the application under test (AUT).
    - Proxy development
      A challenge in functional testing is the variety of user interface (UI) frameworks that are available (for example, Java™ and HTML) and controls (for example, button and table) that testing must support. UI frameworks differ in architecture and programming models and the controls differ in their inheritance hierarchy, methods, properties data, and user actions.
    - TestObjects
      TestObjects are the script-side interfaces for proxies and application under test (AUT) controls. A TestObject is a connection point between the test script and a ProxyObject that connects to the real object in the AUT. During recording, statements are recorded and objects are added to the Object Map. The script uses the information from the Object Map to construct and find TestObjects.
    - ProxyObject hierarchy
      While developing new proxies by extending existing proxies for any domain, it is important to understand the existing proxies and the hierarchies, so that you extend the right proxy.
    - TestObject class diagram and canonical names
      HCL DevOps Test UI (Test UI) has a predefined set of TestObjects that are hierarchically grouped and each TestObject has a set of predefined methods.
    - SubItems
      SubItems are part of TestObjects. The ObjectMap does not contain the SubItems, because they are not mapped.
    - Value classes and value managers
      The following code examples show several value classes and value managers.
    - TestData types
      The HCL DevOps Test UI (Test UI) framework calls the getTestDataTypes() and getTestData(String) proxy methods for extracting data from controls for verification and reference. These methods are used during the creation and play back of data verification points. You can override the getTestDataTypes() method to add more specific data types for a control.
    - Proxy exceptions
      HCL DevOps Test UI (Test UI) has a set of predefined exceptions that covers wide ranges of errors that are usually expected while functional testing. These exceptions are available for both the Java™ and .NET proxy development frameworks.
    - Proxy development best practices
      Following best practices while you develop proxies can help make your work more efficient and effective. Consider these methods to enhance your development efforts.
  - Customizing a script template
    HCL DevOps Test UI (Test UI) uses its default script templates to format and provide basic information when you create a script. You can customize the information and format by customizing the script templates.
  - Using the API to edit functional test scripts
    These topics describe how you can take advantage of the HCL DevOps Test UI (Test UI) application programming interface (API) or the scripting framework to make changes to functional test scripts. As a general rule, the modifications that you make with the scripting SDK, should emulate as closely as possible, the user interactions to test with the application-under-test.
- Extending the functionality in the Visual Studio IDE
  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.
- Experimental features
  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.

Process Model

There are two types of HCL DevOps Test UI (Test UI) processes. The application under Test (AUT) processes are known as Test UI server side processes. The recorder, playback, objects inspector, and the IDE (Eclipse or Visual Studio .Net) processes are known as Test UI client side processes.

A shared memory inter process communication (IPC) layer complements the high-level components of the Test UI process model.