Home
Getting Started
This guide provides an overview and describes the tasks to get you started with HCL OneTest™ API.
HCL® Quality Server overview
HCL OneTest™ Virtualization stubs designed in HCL OneTest API are published to HCL® Quality Server, which holds them in a repository.
Domains and environments
You can use domains to group and manage test assets. Within a domain, you can have one or more environments, which can use to group test variables and test tags.

Getting Started
This guide provides an overview and describes the tasks to get you started with HCL OneTest™ API.
- HCL OneTest™ API overview
  You can use HCL OneTest™ API to create, modify, and run service tests.
- Testing methodology
  By following four basic guidelines, you can incorporate HCL OneTest™ API into your testing methodology. These guidelines drive efficient and expedient integration testing, and they can be applied to your testing process and infrastructure requirements.
- Service-oriented architecture (SOA) testing
  A SOA consists of business processes that are implemented by linking individual services. The linking can be done programmatically or with tools based on Business Process Execution Language (BPEL). SOA testing can be challenging because there is no GUI; the focus is on testing interfaces and services.
- Getting started with testing
  You can start using HCL OneTest™ API by completing the preliminary tasks such as creating and running a test, creating and running a stub, recording an HTTP proxy, and running a stub in a Docker container.
- HCL® Quality Server overview
  HCL OneTest™ Virtualization stubs designed in HCL OneTest API are published to HCL® Quality Server, which holds them in a repository.
  - Domains and environments
    You can use domains to group and manage test assets. Within a domain, you can have one or more environments, which can use to group test variables and test tags.
  - Deploying stubs
    For the stub to access the correct data source, you must publish each stub to the correct domain and environment that is the one that contains that stubs data source.
  - Publishing several versions of the same stub
    During testing, you might discover that you require several versions of a stub and you might not want to override the previous version.
  - Running stubs
    When several versions of a stub are deployed, it is possible to run all versions of them in the same environment.
  - Sharing and managing stubs
    If the purpose of a particular HCL OneTest™ API project is to develop and test a component that requires virtualization (stubbing), that project must own that stub but it can be shared across other projects that need to use it.
- HCL OneTest™ API accessibility features
  Users who have a physical disability, such as limited vision, can review the available accessibility features to use HCL OneTest™ API.

Domains and environments

You can use domains to group and manage test assets. Within a domain, you can have one or more environments, which can use to group test variables and test tags.

A domain represents a logical grouping of related systems that are part of a real business project. It is the basic unit of management within HCL OneTest™ Virtualization. It is usual for a service or other endpoint to be included in more than one domain because it is reused by different business projects in different contexts. Thus, a domain is used as a means to group and manage assets in the server. For example, unique business groups within an organization might want to manage stubs independently from each other.

A domain can contain one or more environments. An environment enables users to define groups of variables or tags that can be used in both tests and in transport definitions.

Typically, environments are used to create configurations for different parts of a software product development workflow, such as development, quality assurance, and user acceptance testing. Each project might define a domain, for example, billing domain or customer management domain.

Environments are not created directly within HCL® Quality Server. Instead, they are created automatically when stubs are published from HCL OneTest™ API because stubs are published into an environment within a domain. Ensure that you define each environment in HCL OneTest™ API correctly. This environment name is published to HCL® Quality Server and is used by all the users that are publishing to that domain.