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.
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.
Verification points
Verification points verify whether an expected behavior occurred during a test playback, or they verify whether there is a change in the state of a control or an object. When you create a verification point, you capture information about a control or an object in the application to establish this information as a baseline for comparison during the playback.

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.
  - Preparing the functional test environment
    This section describes the tasks you must perform to configure the functional test environment.
  - Functional test assets
    This section describes the different types of functional test assets that are available in HCL DevOps Test UI (Test UI).
  - Functional test projects
    A functional test project stores application test assets such as scripts, object maps, verification point baseline files, and script templates. You must create a functional test project before you can record scripts.
  - Working with functional test scripts (Windows-only)
    This section describes the process of creating functional test scripts to test your applications.
  - Verification points
    Verification points verify whether an expected behavior occurred during a test playback, or they verify whether there is a change in the state of a control or an object. When you create a verification point, you capture information about a control or an object in the application to establish this information as a baseline for comparison during the playback.
    - Creating properties verification point
      Use a Properties verification point to test properties of an object in your application. When you record the verification point, a baseline of the data is created. Then every time you play back the script, the data will be compared to see whether any changes have occurred, either intentionally or unintentionally. This is useful for identifying possible defects. You can create a verification point while recording a script or you can insert a verification point anytime in the script.
    - Creating a data verification point
      Use a data verification point to test data that is displayed in your application. When you record the verification point, a baseline of the data is created. Then every time you play back the script, the data is compared to see whether any changes have occurred, either intentionally or unintentionally. This is useful for identifying possible defects. You can create a verification point while recording a script or you can insert a verification point anytime in the script.
    - Editing verification point data
      You can edit verification point data while creating or inserting a verification point in the Verification Point Data page wizard. After you create the verification point, you can edit the data in the Verification Point Editor.
    - Selecting objects and data value options for data verification points
    - Creating an image verification point
      You can use an image verification point to test images in your application. When you record the verification point, a baseline image file is created. Every time you play back the script, the image is compared to see whether any changes have occurred, either intentionally or unintentionally.
    - Verification Point Editor
      The Verification Point Editor lets you view and edit verification point data. You can open the Editor by double-clicking a verification point in the Script Explorer window. The Editor banner displays the name of your verification point.
    - Verification point comparator
      You can use comparators to compare verification point data after you play back a script with a verification point and to update the baseline file. If the verification point fails, the comparator shows both expected and actual values so that you can analyze the differences. You can then load the baseline file and edit or update it with the values from the actual file.
    - Comparing and updating verification point data using the Comparator
      Use the Verification Point Comparator to compare verification point data after you play back a script with a verification point and to update the baseline file. If the verification point failed, the Comparator shows both the expected and actual values, so you can analyze the differences. You can then load the baseline file and update it with the values from the actual file.
    - Inserting verification points into the script using the application visuals
      While working with the simplified test scripts, you can insert verification point using the application visuals.
  - Functional tests with external data
    You can use external data to data-drive functional tests. When you data-drive a test, the script uses variables for key application input fields and programs instead of literal values so that you can use external data as you data-drive the application you are testing.
  - Testing terminal-based applications
    Use the HCL DevOps Test UI (Test UI) Terminal-based Applications feature to create test scripts and automate your host-application test cases. You can test host attributes, host field attributes, and screen-flow through a host application. It uses terminal verification points and properties, as well as synchronization code to identify the readiness of terminal for user input.
- 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.
- 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.

Verification points

Verification points verify whether an expected behavior occurred during a test playback, or they verify whether there is a change in the state of a control or an object. When you create a verification point, you capture information about a control or an object in the application to establish this information as a baseline for comparison during the playback.

You can use verification points to identify possible defects when you upgrade an application to the next version. HCL DevOps Test UI (Test UI) reports an error if the expected behavior does not occur during the playback.

The following links provide more information: