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.
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.
Creating Web UI tests
See the different ways to record Web UI tests. After the recording stops, the tests are generated automatically.
Recording a Web UI test immediately after the previous playback
When you want to continue the testing after the previous playback, you can choose to record a new Web UI test by using the Allow recording after playback option.

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.
    - Creating Web UI tests
      See the different ways to record Web UI tests. After the recording stops, the tests are generated automatically.
      - Web UI recording
        HCL OneTest™ UI provides multiple ways to create Web UI tests using the UI Test perspective. You can create a Web UI test that captures both functional and HTTP traffic in the same recording. In addition, you can create a Web UI test for a web application that is already running in an instance of the Chrome, Firefox, or Safari browser. You can also initiate a recording from a step of an existing test. You can also play back tests on Microsoft™ Edge browser but they must be recorded on Chrome, Firefox, or Internet Explorer.
      - Prerequisites for creating tests
        Before you can create a test, you must complete the prerequisite tasks.
      - Recording a Web UI test
        You create a Web UI test in the UI Test perspective. HCL OneTest™ UI automatically enables web browsers and configures the test environment before you start recording tests for web applications.
      - Recording a Web UI test by using a running browser instance
        You can create a Web UI test of a web application from the UI Test perspective using a browser that is already running locally. For example, if you have already recorded some part of a web application, you can go back at a later time to resume the recording Support is provided for Chrome and Firefox on Windows and Linux computers and for Safari, Chrome and Firefox on Macintosh computers. Internet Explorer is not supported.
      - Recording steps for an existing Web UI test
        If you already have a test, you can add more steps to it at a desired location by initiating the recording from a step or from the application node. For instance, if the task flow has changed in the new version of the application that you recorded and you want to update the existing test script, start the recording from the step after which the new steps must be added. You can also initiate the recording from the Launch application or In application nodes of the test.
      - Recording a Web UI test immediately after the previous playback
        When you want to continue the testing after the previous playback, you can choose to record a new Web UI test by using the Allow recording after playback option.
      - Recording a test with Google Chrome Device Mode
        You can use the Google Chrome Device Mode feature to emulate tests of web applications on mobile devices.
      - Annotating a test during recording
        You can add comments, add transactions, or change a page name while you record a test. The advantage of adding these elements during (rather than after) recording is that you can place the annotations in the test exactly where you want. In addition, because annotations are part of the recorded test, they are regenerated when you regenerate the test. You can also insert split points into a test during record.
      - Splitting a test during recording
        You can insert split points when you record a test. Split points allow you to generate multiple tests from a single recording that you can replay in a different order with a schedule.
      - Putting test assets under source control
        Use version-control software, such as Rational® Team Concert™, to put the test assets under source control.
    - Editing Web UI tests
      With the test editor, you can view and customize a Web UI test.
  - 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.
  - 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.

Recording a Web UI test immediately after the previous playback

When you want to continue the testing after the previous playback, you can choose to record a new Web UI test by using the Allow recording after playback option.

Before you begin

You must have completed the following tasks:

Read and been familiar with the enabling of browser extensions for tests in a running browser instance. See Enabling Google Chrome for Web UI testing, Enabling Mozilla Firefox for Web UI testing, Enabling the Apple Safari browser to perform Web UI tests on macOS, and Enabling Microsoft Edge for Web UI testing.
Created one or more Web UI tests. See Recording a Web UI test.

About this task

You can keep the browser active after the playback is complete for a Web UI test, and then start to record from the point where the playback stopped.

Procedure

Start HCL OneTest™ UI and perform the following steps:
1. Click Window > Preferences > Test > Test Execution > UI Test Playback > Desktop tab.
2. Select the Allow recording after playback option under Playback options to continue recording in the same browser after the playback.
3. Click Apply and Close.
Open the Web UI test for playback from the Test Navigator pane.

The test is displayed.
Optional: Remove or disable the step if the close browser action is listed in the script.
The close browser action is recorded when you intentionally close the browser during the recording process. However, you can choose to stop a recording and not record the close browser action.
Click the Run Test icon.
Click the UI Test perspective after the test run is complete.
Click New > Test From Recording or click the New Test From Recording icon on the toolbar in the UI Test perspective.
Click Create a test from a new recording, and then select Web UI Test.
Click Next.
Type a name for the test, and then click Next.
Select Running browser instance, and then click Next in the Select Client Application page.
Select the web application that you tested from the list of running browser instances and click Finish.
Record the test from the point where the previous playback had stopped.
Stop the recorder by clicking the Stop icon in the Recording Control view after you finish the user tasks in the browser.
The test is generated from the recording.

Results

You have recorded a Web UI test immediately after the previous playback is complete.