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

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

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.

Test Virtualization Control Panel can schedule the execution of test suites on a single or recurring schedule basis.

Consider the following points:

Stubs are run by an Agent. Make sure that you set up the Library Manager of Test Integrations and APIs Agent to point to the relevant libraries required to run your stubs. For example, for an IBM® WebSphere® MQ stub, Library Manager can reference the WebSphere® MQ client JAR files.
Published stubs are stored on the computer where Test Virtualization Control Panel is installed, so long-term disk space requirements depend on the size and number of published stubs.
Test Virtualization Control Panel contains information about all deployed stubs and whether they are running. This is viewable by all team members, so each team member can deduce enough information about each stub running in Test Virtualization Control Panel. Add descriptive labels and ensure that version numbering of stubs is implemented correctly.

You can find the following information about getting started with Test Virtualization Control Panel: