Home
Getting Started
This guide provides an overview and describes the tasks to get you started with HCL DevOps Test Integrations and APIs (Test Integrations and APIs).
Testing methodology
By following four basic guidelines, you can incorporate HCL DevOps Test Integrations and APIs (Test Integrations and APIs) into your testing methodology. These guidelines drive efficient and expedient integration testing, and they can be applied to your testing process and infrastructure requirements.
Building tests
HCL DevOps Test Integrations and APIs (Test Integrations and APIs) 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.

Getting Started
This guide provides an overview and describes the tasks to get you started with HCL DevOps Test Integrations and APIs (Test Integrations and APIs).
- Overview of DevOps Test Integrations and APIs
  You can use HCL DevOps Test Integrations and APIs (Test Integrations and APIs) to create, modify, and run service tests.
- Testing methodology
  By following four basic guidelines, you can incorporate HCL DevOps Test Integrations and APIs (Test Integrations and APIs) 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 DevOps Test Workbench (Test Workbench) 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 DevOps Test Integrations and APIs (Test Integrations and APIs) 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 Test Integrations and APIs to do service unit testing.
  - Building tests
    HCL DevOps Test Integrations and APIs (Test Integrations and APIs) 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.
    - Options for creating test resources
      HCL DevOps Test Integrations and APIs (Test Integrations and APIs) includes a number of options for automated resource creation, including topology discovery, synchronization, and recording.
    - Building system models by using synchronization
      When design-time assets are available, building by using synchronization is the preferred technique. Synchronization builds the system under test for you, which simplifies your testing work.
    - Building a system model manually
      Manual system modeling can be done where synchronization or recording is not possible or there are no service components when synchronized.
    - Test asset creation and recording
      HCL DevOps Test Integrations and APIs (Test Integrations and APIs) enables you to record events in the system under test and recorded messages can be used to create tests and stubs more quickly and accurately. This can act as base message and test data for creating ongoing test assets.
    - Test execution
      In HCL DevOps Test Integrations and APIs (Test Integrations and APIs), tests generally consist of one or more inputs into the systems under test (SUT), and then validation of results and side effects. Data from one step of a test can be used to feed the next step. Test Integrations and APIs is built for testing, so every test step can be validated without scripting.
  - Project structure
    When an HCL DevOps Test Integrations and APIs (Test Integrations and APIs) 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 in DevOps Test Integrations and APIs
  You can start using HCL DevOps Test Integrations and APIs (Test Integrations and APIs) 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.
- DevOps Test Virtualization Control Panel overview
  HCL DevOps Test Virtualization (Test Virtualization) stubs that are designed in HCL DevOps Test Integrations and APIs (Test Integrations and APIs) are published to HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel), which holds them in a repository.
- DevOps Test Integrations and APIs accessibility features
  Users who have a physical disability, such as limited vision, can review the available accessibility features to use HCL DevOps Test Integrations and APIs (Test Integrations and APIs).

Building tests

HCL DevOps Test Integrations and APIs (Test Integrations and APIs) 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.

Test assets such as test cases, test suites, and stubs can be created by any of these methods:

By recording the transaction between the components (recording)
By using the design-time assets with Message Exchange Pattern (MEP)
Manually

These created test assets are used in different test phases such as unit, integration, system, and system integration..

This diagram describes the different activities and associated assets that are used and created by using Test Integrations and APIs. Test Integrations and APIs assets