Release notes for HCL OneTest UI V10.1.0

This document contains information about new features, system requirements, and known limitations in HCL OneTest™ UI.

Contents

Description

HCL OneTest UI is a GUI test automation tool that is used to accelerate the functional and regression testing. It provides a flexible environment to test the desktop and web applications very efficiently. It is used to test a wide range of applications such as HTML5-based web applications built on modern frameworks which include Angular, React and Vue.js in the latest versions of the world’s popular browsers, both on the desktop and mobile devices. HCL OneTest UI is available in two integrated development environments (IDE): Eclipse and Microsoft Visual Studio .NET. The Eclipse integration supports both Java and simplified (non-programming) method of scripting while the Microsoft Visual Studio .NET integration supports Microsoft Visual Basic .NET scripting language. See Product overview.

Some of the older versions of software supported by HCL OneTest UI are deprecated. To view the list of deprecated software, see http://www.testworkbench-community.com/blogs/technology-currency-updates-for-functional-tester-v1001.

What's new

  • Unified Report

    The experimental unified report for Web UI tests is replaced by the new and enhanced unified report. This report has a live reporting feature and is available to Functional, Web UI and Compound tests, and Accelerated Functional Test (AFT) suites. The report provides a detailed overview of your test results and has an extensive user interface to analyse and filter your test result details. You can also a generate a unified report for SAP tests that are run by using the HCL OneTest Performance SAP extension. See Unified reports.

  • Microsoft Azure DevOps integration

    You can now integrate HCL OneTest UI with Azure DevOps by using the HCL OneTest Studio extension to run tests as tasks in Azure DevOps pipelines. See Integration with Azure DevOps.

  • Enhancement to image validation

    Now, you can define the image property as an identifier while recording the Web UI tests or while playing back the Web UI tests. The image identifier validates the images and user interface elements in the application under test. You can also enable the guided healing feature for the Web UI tests that are identified by using the image property. See Validating images and user interface elements by using the image property.

  • Support to extend application URL with substitutions in a Web UI test

    Now, you can substitute your application URL in a Web UI test by using data sources and then extend the application URL to other Web UI tests. See Extension of application URL in Web UI tests.

  • Enhancements to restrict test scripts with start application
  • Support for SAP test

    The SAP extension is available for 32-bit HCL OneTest UI. For more information about recording SAP tests, see Recording SAP tests.

  • Updates to Dataset CSV Editor

    The browser-based CSV Editor provides additional options that include Find and Replace, Undo, and Redo to organize your data in the dataset in a better way. See Editing datasets.

  • Enhancements to browsers for playback
    • You can use Microsoft Edge (based on Chromium) and Opera browsers to play back your Web UI tests on Mac operating system.
    • You can play back Functional HTML test scripts in multiple windows of Google Chrome and Mozilla Firefox browsers. See Enabling multi-window support to test Functional HTML tests.
  • Enhancement to mobile recording and playback

    You can use this technical preview feature to record actions that you perform on native and hybrid applications in Android mobile devices. You can connect your emulators and mobile devices to your computer and then record the user interface actions such as tap, swipe and so on and hardware actions such screen lock, back button and so on. The actions are performed by using a virtual client of your mobile device. See Automating UI testing of android applications.

System requirements

For information about hardware and software compatibility, see the system requirements document.

Installing the product

For installation instructions, see Installing software.

Notes:
  • You cannot upgrade to the latest version of the product. You must uninstall the existing version of the product before installing the latest version of the product.
  • After installing V10.1.0, at any point of time if you want to use the previous version of the product, you cannot roll back to the previous version. If you want to use the previous version of the product, you must uninstall the existing version, and then install the required version of the product.

Known issues

Known issues are documented in the download document and in the form of individual tech notes in the Support Knowledge Base. See IBM Support Knowledge Base. The knowledge base is continually updated as issues are discovered and resolved. By searching the knowledge base, you can quickly find workarounds or solutions to issues.
Note: The product user interface (UI) help displays the HCL OneTest UI V10.0.2 documentation instead of V10.1.0 product documentation. You can access the V10.1.0 documentation from the V10.0.2 product welcome page. For more information, refer https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0080731.
Product Download document Knowledge base

HCL OneTest UI

Release document

HCL support

Contacting HCL support

  • For technical assistance, contact HCL Customer Support.
  • Before you contact HCL support, gather the background information that you will need to describe your problem. When describing a problem to HCL support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:
    • What software versions were you running when the problem occurred?
    • Do you have logs, traces, or messages that are related to the problem?
    • Can you reproduce the problem? If so, what steps do you take to reproduce it?
    • Is there a workaround for the problem? If so, be prepared to describe the workaround.