Home
Getting Started
This guide provides an overview and describes the tasks to get you started with HCL OneTest™ API.
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
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.
  - HCL OneTest™ API capabilities
    HCL OneTest™ API provides a wide range of features and functionality that give users the ability to test their integration and SOA projects successfully.
  - SOA test strategies
    SOA is more than simple web services that provide interfaces to existing applications. An SOA implementation is likely to involve multiple services and vendors and is considered a complex computing problem. Many companies try implementing automated testing for GUI solutions. Due to the changing nature of GUIs, they find it difficult to achieve ROI. That is not to say that GUI testing cannot be achieved, but it must be done during the project lifecycle by applying automated interface testing. Focusing on programmatic interfaces and services in automated testing offers significant ROI, as the design contracts for these interfaces change less often, changing business processes in a distributed environment is costly. When it comes to SOA, a different approach, skill-set, and mind-set are required for testing.
  - HCL OneTest™ API user profiles
    Users that can use HCL OneTest™ API to test an SOA fall into multiple categories.
  - SOA and HCL OneTest™ API
    HCL OneTest™ API primary intent is to simplify the process by which the user builds tests (that is, schema-driven message creation, test driven development, and so on).
- 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.

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.

HCL OneTest™ API is based on the Service Component Architecture (SCA), which provides a programming model for building applications and systems based on an SOA. For more information about SCA, see Service Component Architecture (SCA)

Based on this concept, the three main components that are used in HCL OneTest™ API SOA design are:

Operations are transactions that represent single, logical units of work. The execution of an operation typically causes one or more persistent data records to be read, written, or modified. An Operation has a structured interface for invocation and response.
Services are granular, self-contained groupings of business operations. The focus on services is different from traditional GUI applications as a service is neither a complete application nor a single subsystem. Instead, a service is designed to maximize reuse and must be stateless. Additionally, a service will be able to accommodate multiple invocation patterns (for example, SOAP over HTTP for synchronous implementations or SOAP over JMS for asynchronous implementations).
A Business Process is long-running set of actions or activities that are performed with specific business goals in mind. Business processes typically encompass multiple service invocations.

You can find the following information about the service-oriented architecture testing: