Welcome
Tester Guide
This guide describes the tasks that you can perform for testing various domains, technologies, and applications. To enable testing, you must configure and enable the environment for testing.
API Tester Reference
This guide provides the topics to help the API tester use the product by using the user interface, commands or scripts. This guide is intended for API testers.
Working in non-GUI mode
Many test actions can be completed in non-GUI mode by using the command line, Ant, or REST interfaces.
Managing test results
Use HCL Quality Server to manage test results with command-line APIs.
Deleting old test results by using the command line
You can delete old test suite results by using the HCL OneTest™ API command line.

Release Notes
This document contains information about What's new, installation, known issues, known limitations, and contact information of HCL support.
System Requirements
This document includes information about hardware and software requirements for HCL OneTest™ API.
Getting Started
This guide provides an overview and describes the tasks to get you started with HCL OneTest™ API.
Administrator Guide
This guide describes how to install HCL OneTest™ API. After you install the software, you can perform administration tasks such as configuration and integration of the product. This guide is intended for administrators.
Tester Guide
This guide describes the tasks that you can perform for testing various domains, technologies, and applications. To enable testing, you must configure and enable the environment for testing.
- API Tester Reference
  This guide provides the topics to help the API tester use the product by using the user interface, commands or scripts. This guide is intended for API testers.
  - API Tester Guide
    This guide describes the tasks that you can perform for testing various domains, technologies, and applications. To enable testing, you must configure and enable the environment for testing. This guide is intended for API testers.
  - Extending HCL OneTest™ API functionality by using custom functions
    You can add more calculations and operations to tests by using the HCL OneTest™ API custom function class. HCL OneTest API custom function is a Java™ class that extends the com.ghc.ghTester.expressions function.
  - Working in non-GUI mode
    Many test actions can be completed in non-GUI mode by using the command line, Ant, or REST interfaces.
    - Command-line interfaces
      HCL OneTest™ API command-line client is available in HCL OneTest API 8.0.1 or later.
    - Ant tasks
      Support for the environment, scenario and stub Ant tasks is supplied with HCL Quality Server.
    - REST services
      Representational state transfer (REST) is a simple stateless architecture that generally runs over HTTP. When used in conjunction with HCL Quality Server, HTTP methods (such as GET and POST) are mapped to actions on domains, environments, scenarios, stubs and other resource types.
    - Running tests
      Use HCL OneTest™ API to run tests with command-line and Ant APIs.
    - Managing test results
      Use HCL Quality Server to manage test results with command-line APIs.
      - Deleting all test results by using the command line
        You can delete all test results and project data in the results database that you no longer need by using the HCL OneTest™ API command line.
      - Deleting old test results by using the command line
        You can delete old test suite results by using the HCL OneTest™ API command line.
    - Managing domains
      You can create, list, update, and delete domains with the HCL Quality Server REST API.
    - Managing environments
      Locking a HCL Quality Server environment prevents other users from changing the state of that environment, for example, starting or stopping stubs.
    - Managing scenarios
      Use HCL Quality Server to manage scenarios with command-line, Ant, and REST APIs.
    - Managing stubs
      You can manage stubs by using the command-line, Ant, and REST APIs.
- API Tester Guide (Service Virtualization)
  This guide describes the tasks that you can perform for using virtual services or stubs to simulate parts of an environment if the real services are not yet available or because they are difficult or expensive to use. This guide is intended for API Testers.
Test Manager Guide
This guide describes the tasks that you can perform for tracking the quality of the application. This guide is intended for Test Managers.
Troubleshooting HCL OneTest™ API
While working with HCL OneTest™ API, you might encounter some problems that you can easily troubleshoot.
HCL OneTest™ API reference
HCL OneTest™ API is a scripting-free environment for developing tests for service-oriented architecture (SOA) messaging and business process integration projects. Tests can be built by recording existing system behaviors or from requirements, by entering the data to send and the data that is expected in return.
Security Considerations
You can take certain actions 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 product documentation.

Deleting old test results by using the command line

You can delete old test suite results by using the HCL OneTest™ API command line.

The syntax to use is as follows:

IntegrationTesterCmd Options delete-all-results-keeping  Arguments

Here are some examples:

To delete all test suite results that are more than 6 months old, use the following command:

IntegrationTesterCmd --databaseURL jdbc:db2://localhost:50000/resultdb 
            --dbuser jkelly --password hayling delete-all-results-keeping P6M

To delete all project Proj1 test suite results that are more than 7 days old use the following command:

IntegrationTesterCmd --project "C:\Users\jkelly\MyProjects\Proj1\Proj1.ghp" delete-all-results-keeping P7D

Warning: After you delete all test results and project data in the results database, you must restart any HCL OneTest™ API workbench instances or HCL OneTest™ API Agent instances that were using that results database.

The following table lists the options that you can use with the IntegrationTesterCmd command for deleting test results older than a specified period.

Table 1. List of available options
Options	Description
--project/-p	Path to project file (optional). Used to limit the deletion to test suite results to a specific project. If not specified then `databaseUrl`, `dbuser`, and `password` are required options.
--databaseUrl/-b	Results database URL (optional). For more information on the specification of database URLs when using IP literal addresses, see IP literal address.
--dbuser/-g	Results database user name (optional)
--password/-h	Results database password (optional)
--ignorePolicy/-y	If present, the archive policy is ignored (flag).
--stubResults/-z	If present, stub results are deleted (flag).

Table 2. List of available arguments
Arguments	Description
duration	A representation of a time period of the form PnYnMnDTnHnMnS, using the World Wide Web Consortium (W3C) timeDuration specification. For example, to delete all results older than 6 months use P6M

Note: Results that are associated with a test cycle will be deleted only if the test cycle is closed.