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 UI Test perspective
When you develop web applications, Windows-based applications, or mobile applications, you can use HCL OneTest™ UI to create functional tests for these applications. You must first record the tests and then use HCL OneTest UI to run the tests before you can view the test results.
SAP tests
When you record a test, the test creation wizard records your interactions with the SAP server, generates a test from the recording, and opens the test for editing. You can record tests from the SAP GUI. You can also record SAP batch input tests that can be used to produce a heavy load on the server while minimizing the processing requirements for virtual testers.
SAP test editor reference
In SAP testing, the test editor information is divided into nine categories. This section describes the fields in each category that can be edited manually.
SAP test details
In the test editor, the test element is the first element in the test suite. These settings apply to the entire test.

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 OneTest™ UI to create functional tests for these applications. You must first record the tests and then use HCL OneTest UI to run the tests before you can view the test results.
  - Web UI tests
    You can test web applications in HCL OneTest™ UI by using the industry-standard browsers such as Google Chrome, Apple Safari, Mozilla Firefox, and Microsoft Edge. You can record Web UI tests and then play back the tests to evaluate the test results. You can also test the web applications on dual monitors when you extend the display of your computer to a secondary monitor.
  - Mobile tests
    You can test the Android or iOS mobile applications by recording and playing back mobile tests on Android devices or emulators, iOS mobile devices or simulators by using HCL OneTest™ UI.
  - Windows tests
    You can configure the Windows applications to record and play back tests on the Windows desktop applications. You can also test the Windows applications on dual monitors when you extend the display of your computer to a secondary monitor.
  - SAP tests
    When you record a test, the test creation wizard records your interactions with the SAP server, generates a test from the recording, and opens the test for editing. You can record tests from the SAP GUI. You can also record SAP batch input tests that can be used to produce a heavy load on the server while minimizing the processing requirements for virtual testers.
    - SAP testing guidelines
      Before you test the SAP applications, you must set up your test environment and incorporate these guidelines to produce reliable SAP tests.
    - Recording an SAP test
      You can record your interaction with the SAP GUI client to generate an SAP test. When you record, the recording wizard opens the SAP GUI client and records all the interactions that occur between the client and the server.
    - Inserting a new recording into a SAP test
      You can insert a new recording into a test. Use this feature to add or replace a part of a recorded session.
    - Recording a SAP batch input test
      You can record certain SAP transaction sessions from SAP GUI with SAP batch input tests recording wizard. When you record a session, the recording wizard automatically starts a SAP GUI interface and records the transaction that you specified. After you finish the recording, the wizard generates a SAP batch input test in HCL OneTest™ UI.
    - Changing SAP test generation preferences
      You can change preferences for SAP tests to control the generation of SAP tests. You can also modify the setting for the verification points, data correlation, and the display of SAP GUI during the test run.
    - SAP test editor reference
      In SAP testing, the test editor information is divided into nine categories. This section describes the fields in each category that can be edited manually.
      - SAP test details
        In the test editor, the test element is the first element in the test suite. These settings apply to the entire test.
      - SAP connection details
        In the test editor, SAP connection elements are at the top of the test site and describe the connection to the SAP server. These settings apply to the entire test.
      - SAP screen details
        In the test editor, SAP screen elements are located in transactions and are the basic performance measurement unit for the test. These settings apply to the selected get event.
      - SAP set details
        In the test editor, SAP sets are located in SAP screen elements and describe a user input action in the SAP GUI client. These settings apply to the selected SAP set.
      - SAP get details
        In the test editor, SAP get events are located in SAP screen elements and provide a way to retrieve data from a SAP GUI object to implement verification points. These settings apply to the selected get event.
      - SAP call details
        In the test editor, SAP call elements are located in SAP screen elements and describe various recorded interactions with the SAP server. These settings apply to the selected SAP event.
      - SAP server request details
        In the test editor, server request elements are located at the end of every SAP screen and provide information that the server returns for the selected screen.
      - SAP batch connection details
        In SAP batch input tests, SAP batch connections contain the basic connection information for a batch input test to connect to the SAP server without a SAP GUI. In most cases, these details are the same as those used when you connect manually to SAP with the SAP GUI.
      - SAP batch input transaction details
        In the SAP batch input tests, SAP batch input transactions are located in transactions and are recorded transactions that are to be run at a low level, without a SAP GUI, in order to produce a load on the SAP server.
  - Selenium or Appium tests
    You can manage your Selenium or Appium Java™ tests from the UI Test perspective, where you can import and modify the tests, add them to compound tests, and run them. You can also create new Appium Java tests from the Perfecto perspective on Windows™ and Mac OS, add the tests to compound tests, and run them. Perfecto is not currently supported on Linux®.
  - Compound tests
    You can create compound tests to help you organize smaller tests into scenarios that can then be run end-to-end. You can combine tests from different extensions to achieve end-to-end flow.
  - Accelerated Functional Tests
    When you create Web UI, mobile, or Windows tests, you can use the Accelerated Functional Test (AFT) feature in HCL OneTest™ UI to distribute test effort during the play back of the recorded tests.
  - Keywords
    In HCL OneTest™ UI, you can record and then associate Test Workbench tests with the keywords that are created in IBM® Rational® Quality Manager. The keywords are used in manual tests in Rational Quality Manager. When you run a manual test that contains a keyword associated with a HCL OneTest Studio test, the Test Workbench test is run on the workstation where the adapter has been started.
- Tests in the Functional Test perspective
  When you develop Java, HTML, or Terminal-based applications, you can use HCL OneTest™ UI to create traditional functional tests for these applications. You must first record the tests and then use HCL OneTest 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.
- Extending the functionality in the Visual Studio IDE
  These topics describe various ways that you can customize HCL OneTest™ UI or use the application programming interface (API) to extend HCL OneTest UI functionality.
- Experimental Features
  HCL OneTest™ 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.

SAP test details

In the test editor, the test element is the first element in the test suite. These settings apply to the entire test.

SAP options

Display SAP GUI on execution

During test execution, it might not be desirable to display the SAP GUI. This setting specifies the behavior for the current test suite. However, you can change the default setting for generated tests in the SAP Test Generation preferences.

Hide: When selected, all instances of the SAP GUI are hidden. In some cases, modal dialog boxes from the SAP GUI can flash briefly on the screen. This is the default setting.
Show: When selected, the SAP GUI is displayed for users.

Common options

Datasets: Lists details about each dataset used by the test: the name of the dataset, the columns that are used, and the location in the test where the dataset column is referenced. Click the location to navigate there.
Add dataset: Adds a reference to a dataset that you want a test to use. Clicking this option is the same as clicking Add > Dataset with the test selected.
Remove: Removes the selected dataset. This option is not available if the dataset is in use.