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.
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.

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.

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.

A change in stub function can be carried out by the stub owner, unless there are specific reasons why another the project might need a different version. In that case, other projects can develop other versions of the stub. However, coordination between projects will be mandatory and the reason for a different stub version must be logged and traceable.

It is likely that other projects that are joining the system under test will want to interact with a stub owned by another project because they might be sharing components that are unavailable.

Consider the following points:

If the same stub version is used, there might be no problem so long as the performance of the stub is satisfactory.
If a different version of the stub is required, the different stub version can be created and maintained by the project that requires it.
Note: Change endpoint parameters, such as queue names, to ensure that they do not clash with the original stub.