Welcome
Getting Started Guide
This guide provides an overview of HCL OneTest™ Server. You can find the task flows to get you started with HCL OneTest Server. This guide is intended for new users.
Server overview
HCL OneTest™ Server brings together test data, test environments, and test runs and reports into a single, web-based browser for testers and non-testers.
Suites and tests supported
You can find information about the types of Test Suites and tests that you can configure for a run in a project on HCL OneTest™ Server.

Release Notes
This document includes information about What’s new, installation and upgrade instructions, known issues, and contact information of HCL Customer Support.
System Requirements
This document includes information about hardware and software requirements for HCL OneTest™ Server.
Getting Started Guide
This guide provides an overview of HCL OneTest™ Server. You can find the task flows to get you started with HCL OneTest Server. This guide is intended for new users.
- Server overview
  HCL OneTest™ Server brings together test data, test environments, and test runs and reports into a single, web-based browser for testers and non-testers.
  - Supported versions of assets and resources
    You can find information about the versions of assets, resources, agents and Dockers that are supported in HCL OneTest™ Server. You can also find information about the versions of the desktop clients that are supported.
  - Suites and tests supported
    You can find information about the types of Test Suites and tests that you can configure for a run in a project on HCL OneTest™ Server.
  - Virtual services supported
    You can find information about the virtual services that are supported on HCL OneTest™ Server.
  - HCL OneTest Data overview
    HCL® OneTest™ Data is an automated and customizable tool to generate the test data. HCL OneTest Data is one of the components of HCL OneTest Server and can be accessed as Data Fabrication in the HCL OneTest Server GUI.
- Task flow: Test runs and results
  You can use the task flow diagram to get started with HCL OneTest™ Server. After you install the software, you can complete the tasks in sequence to run test assets in HCL OneTest Server and view and analyze the test results.
- Accessibility features
  Accessibility features help users who have physical disabilities, such as visual and, hearing impairment, or limited mobility, to use the software products successfully.
Administrator Guide
This guide describes how to install the HCL OneTest™ Server software.
Test Author Guide
This guide describes how to create test assets in HCL OneTest™ Server and publish test assets to the Git repository that you have configured. You can also edit existing test assets that are in the repository added to your project. This guide is intended for testers and test managers.
Test Execution Specialist Guide
This guide describes tasks that you must complete before you can configure and run tests in HCL OneTest™ Server. You can find information about configuring runs for the different test types that are supported. You can also find information about other tasks that you can perform on the Resource Monitoring Service, Virtualization, and Integrations with third-party applications. This guide is intended for testers or test execution specialists.
Test Manager Guide
This guide describes how to manage and track your overall test effort. This guide is intended for test managers.
Reference Guide
This guide describes conceptual information about data design environment components when you want to use the data fabrication feature in HCL OneTest™ Server.
Troubleshooting
This guide describes how to analyze and resolve some of the common problems that you might encounter while you work with HCL OneTest™ Server.
All Guides (PDF)
You can find the link to view or download the content of the release notes, system requirements, and persona guides of HCL OneTest™ Server as a PDF file.
Security Considerations
This document describes the actions that you can take to ensure that your installation is secure, customize your security settings, and set up user access controls.
Notices
This document provides information about copyright, trademarks, terms and conditions for the product documentation.

Suites and tests that are supported on HCL OneTest™ Server

You can find information about the types of Test Suites and tests that you can configure for a run in a project on HCL OneTest™ Server.

The following table lists the Test Suites and test types that are supported and those tests that are not supported to run on HCL OneTest™ Server:


Supported Suites	Supported tests	Unsupported tests
Accelerated Functional Testing (AFT) Suites Compound Tests that contain any of the following types of tests: Web UI tests HTML tests Mobile tests	Functional Web UI tests Functional Windows tests Functional Mobile tests	Traditional HTML tests Traditional non-HTML tests
API Suites that include the following Test Suites: Test Suites that contain scenarios with references to local stubs. Test Suites that contain stubs that virtualize services run in any Kubernetes cluster or in the Kubernetes cluster that hosts HCL OneTest™ Server. Stubs	API tests	Suites or tests with subscribe actions that operate in the watch mode.
Compound Tests that contain performance tests Rate Schedules VU Schedules	Performance tests	A single test script of any test extension. Tests that belong to 32-bit test extensions and SOA Quality included in VU Schedule, Rate Schedule, and Compound Test. Citrix, SAP, or Siebel as an individual test or as part of a Compound Test.
Postman resources
JMeter tests
JUnit tests
Selenium tests

Note: You must create compound tests for the same type of tests. For example, you can create a compound test that has different mobile tests that use different mobile testing platforms.

Restriction: You cannot merge folders that contain different test projects in the same project directory. For example, you cannot create a project directory that contains a Performance test project and an API Suite project. You must create separate project directories for each test type. For example, you must create the Performance test in the project directory as /MyPerfProject/ and the API Suite in the project directory as /MyAPIProject, before you commit the projects to the remote repository.