Home
Getting Started
This guide provides an overview and describes the tasks to get you started with HCL OneTest™ API.
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.
Test phases
Apart from being used for driving early test plans, HCL OneTest™ API can be used to shift testing earlier in the software development lifecycle (SDLC) than is traditionally possible with standard test tools that test at the UI level. Soon after you have a local build, you can use HCL OneTest API to do service unit testing.
Unit testing
You can do unit testing to validate individual components.

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.
  - Test approach
    The HCL OneTest™ Studio product suite fits easily into a V-Model approach. The classic V-Model demonstrates each phase in predevelopment and its associated phase in test planning. For example, when the system design is delivered, begin planning for system testing. Testing activities such as design, analysis, planning and execution must happen throughout the entire project life cycle.
  - Test phases
    Apart from being used for driving early test plans, HCL OneTest™ API can be used to shift testing earlier in the software development lifecycle (SDLC) than is traditionally possible with standard test tools that test at the UI level. Soon after you have a local build, you can use HCL OneTest API to do service unit testing.
    - Compliance testing before running tests
      You can implement compliance testing when necessary in the project lifecycle to ensure that industry standards such as W3C and policies such as WS-I are enforced correctly.
    - Unit testing
      You can do unit testing to validate individual components.
    - Integration testing
      You can do integration testing to validate the integration interfaces or points between individual functions or components.
    - System testing
      You can do system testing to determine that services are able to produce the required functions when they are integrated to create a business process within a system.
    - System integration testing
      You can do system integration testing (SIT) to verify services functions when integrated to create an end-to-end business process that spans across multiple systems.
  - Building tests
    HCL OneTest™ API separates the task of learning about the system from the tasks of creating test resources, designing (building models), creating and recording test assets, and running tests.
  - Project structure
    When an HCL OneTest™ API project is created for the first time, the project folder structure is created on a disk.
- 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.
- 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.

Unit testing

You can do unit testing to validate individual components.

Consider the following points:

Create simple, individual tests for the relevant component with any interfaces virtualized with simple stubs. These initial tests can be created either by synchronizing with design-time assets (such as WSDL documents), by using run-time assets (such as recorded messages) or manually with design documents.
Create an execution environment that represents the projects development test environment. This environment within HCL OneTest™ API references the physical development test environment and references the actual physical locations and characteristics of components within that environment.
Use simple test data. This allows for a wider coverage of functionality rather than worrying about whether the tests reflect live environments. The tests created in this phase will form the basis for successive testing phases when the tests will be enhanced to reflect live environments. All of these should be grouped into a test suite, which can then be used to execute the tests sequentially or in parallel.
Generate a report for this phase, even if the testing is minimal.