Home
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.
Tester Guide - API Testing
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.
Working in non-GUI mode
You can use the tools and executable files that are provided along with the product software. You can use these tools to perform different test actions in a non-GUI mode.
Managing scenarios
Use HCL® Quality Server to manage scenarios with command-line, Ant, and REST APIs.

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.
- Tester Guide - API Testing
  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.
  - API Testing
    You can use find information about the tasks that you can perform for testing various domains, technologies, or applications.
  - 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
    You can use the tools and executable files that are provided along with the product software. You can use these tools to perform different test actions in a non-GUI mode.
    - Command-line interfaces
      HCL OneTest™ API command-line client is available in HCL OneTest API 8.0.1 or later.
    - Ant tasks
      You can use the supported Ant tasks that is supplied with HCL® Quality Server to create, update, or manage the environment, scenarios, and stubs.
    - 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.
    - 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.
      - Start a scenario by using the command line
        You can start a scenario by using the HCL OneTest™ API command line. This option is useful in situations where Ant is not available.
      - Stop a scenario by using the command line
        You can stop a scenario by using the HCL OneTest™ API command line, optionally waiting for the scenario to stop before exiting. This option is useful in situations where Ant is not available.
      - Start a scenario by using an Ant task
        You can start a scenario by using the HCL® Quality Server Ant tasks.
      - Stop a scenario by using an Ant task
        You can stop a scenario by using the HCL® Quality Server Ant tasks.
      - 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.
    - Managing stubs
      You can manage stubs by using the command-line, Ant, and REST APIs.
- 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.

Managing scenarios

Use HCL® Quality Server to manage scenarios with command-line, Ant, and REST APIs.

Scenario selection

Use HCL® Quality Server API to manage scenarios.

When selecting scenarios, the domain, environment, name and owner options must uniquely identify the scenario to start.

If there is only one scenario in an environment, only domain and environment are required.
If a user has only one scenario in an environment, domain, environment, and owner can be specified to uniquely identify that scenario. Otherwise domain, environment, and name are required to uniquely identify the scenario.
If the command is being used in an automated script, the name must always be used even if, at the time of writing the script, one of the preceding alternatives would be sufficient. This is because using the name creates resilience against future changes in the environment's list of scenarios.
It is possible to specify domain, environment, name, and owner, which would have the effect of uniquely identifying the scenario and verifying that it was created by a specific user.