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

Release Notes
This document includes information about the new features introduced, features deprecated or removed, defects fixed, and known issues identified in this version of HCL DevOps Test Integrations and APIs (Test Integrations and APIs). You can also find the installation and upgrade instructions along with the contact information of HCL Customer Support.
System requirements
This document includes information about hardware and software requirements for HCL DevOps Test Integrations and APIs (Test Integrations and APIs) 2024.03 (11.0.1).
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.
  - 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).
Administrator Guide
This guide describes how to install HCL DevOps Test Integrations and APIs (Test Integrations and APIs). After you install the software, you can perform administration tasks such as configuration and integration of the product. This guide is intended for administrators.
Tester Guide
This guide describes the tasks that you can perform for testing various domains, technologies, and applications. To enable testing, you must configure and enable the environment for testing.
Test Manager Guide
This guide describes the tasks that you can perform for tracking the quality of the application. This guide is intended for Test Managers.
Troubleshooting
While working with HCL DevOps Test Integrations and APIs (Test Integrations and APIs), you might encounter some problems that you can easily troubleshoot.
Reference Guide
This guide provides the topics to help the API tester use the product by using the user interface, commands or scripts. This guide is intended for API testers.
Security Considerations
You can take certain actions to ensure that your installation is secure, customize your security settings, and set up user access controls.
Notices
This document provides information about copyright, trademarks, terms and conditions for product documentation.

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 early and often: Testing earlier in the lifecycle means that defects are less expensive to resolve. Because integration tests run much faster than normal automated UI tests, you can plan to run regression test cycles as often as is necessary. Test Integrations and APIs is designed to work with most of the popular continuous integration tools, such as Jenkins.
Evolve your tests and stubs as you progress through the lifecycle: You can use Test Integrations and APIs for initial testing and begin by creating very simple tests and stubs. These test assets (test, stubs, and data) can be passed along to teams further down the lifecycle who can enhance the basic tests to ensure that they reflect live environments. This process ensures consistency and efficiency in the automation test cycle. Use test assets to create test suites, templates, and stubs.
Plan for flexibility by stubbing strategically: The virtualization (stubbing) capabilities mean that testers and test managers can think differently about their approaches. They can plan to mitigate the unavailability of interfaces to test against. For example, if the risk of environment unavailability for a particular interface is high, you can plan to stub the interface before the environment becomes unavailable. This means that when the inevitable happens, testing can continue. Efficient planning with stubs promotes test environment agility.

You can find the following information about the testing methodology: