Welcome
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.
Tester Guide - Integrations and API Testing
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. This guide is intended for Integrations and API testers.
Working in non-GUI mode
You can use the tools and executable files that are provided along with the product software. You can use these tools to perform different test actions in a non-GUI mode.
Managing test results
Use HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel) to manage test results with command-line APIs.
Fetching specific results data by using the command line
You can fetch specific results data in an XML format from the results database by using the HCL DevOps Test Integrations and APIs (Test Integrations and APIs) command line.

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 Virtualization (Test Virtualization). 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 Test Virtualization.
Getting Started
This guide provides an overview and describes the tasks to get you started with Test Virtualization.
Administrator Guide
Typically, a user with the administrator role is responsible for certain tasks including installation, configuration, and integration of the product. This guide lists all such topics.
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.
- Tester Guide - Integrations and API Testing
  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. This guide is intended for Integrations and API testers.
  - Integrations and API Testing
    You can use find information about the tasks that you can perform for testing various domains, technologies, or applications.
  - Extending DevOps Test Integrations and APIs functionality by using custom functions
    You can add more calculations and operations to tests by using the HCL DevOps Test Integrations and APIs (Test Integrations and APIs) custom function class. Test Integrations and APIs custom function is a Java™ class that extends the com.ghc.ghTester.expressions function.
  - Working in non-GUI mode
    You can use the tools and executable files that are provided along with the product software. You can use these tools to perform different test actions in a non-GUI mode.
    - Command-line interfaces
      HCL DevOps Test Integrations and APIs (Test Integrations and APIs) command-line client is available in Test Integrations and APIs 8.0.1 or later.
    - Ant tasks
      You can use the supported Ant tasks that is supplied with HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel) to create, update, or manage the environment, scenarios, and stubs.
    - REST services
      Representational state transfer (REST) is a simple stateless architecture that generally runs over HTTP. When used in conjunction with HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel), HTTP methods (such as GET and POST) are mapped to actions on domains, environments, scenarios, stubs and other resource types.
    - Running tests
      Use HCL DevOps Test Integrations and APIs (Test Integrations and APIs) to run tests with command-line and Ant APIs.
    - Managing test results
      Use HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel) to manage test results with command-line APIs.
      - Fetching specific results data by using the command line
        You can fetch specific results data in an XML format from the results database by using the HCL DevOps Test Integrations and APIs (Test Integrations and APIs) command line.
      - Deleting all results by using the command line
        You can delete all results and project data that is stored in the results database and you no longer require the stored results by using the HCL DevOps Test Integrations and APIs (Test Integrations and APIs) command line.
      - Deleting historical test results data by using the command line
        You can delete historical test suite results or the stub results and specify the results that you want to retain by using the HCL DevOps Test Integrations and APIs (Test Integrations and APIs) command line.
      - Renaming Suites or tests in the results database by using the command line
        You can use the command line to verify and rename all Suites and tests that have either moved to a different location or are renamed and which are stored in a results database.
    - Managing domains
      You can create, list, update, and delete domains with the HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel) REST API.
    - Managing environments
      Locking a HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel) environment prevents other users from changing the state of that environment, for example, starting or stopping stubs.
    - Managing scenarios
      Use HCL DevOps Test Virtualization Control Panel (Test Virtualization Control Panel) to manage scenarios with command-line, Ant, and REST APIs.
    - Managing stubs
      You can manage stubs by using the command-line, Ant, and REST APIs.
- Tester Guide - Service Virtualization
  This guide describes the tasks that you can perform for using virtual services or stubs to simulate parts of an environment if the real services are not yet available or because they are difficult or expensive to use. This guide is intended for API Testers.
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.
Security Considerations for DevOps Test Virtualization
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.

Fetching specific results data by using the command line

You can fetch specific results data in an XML format from the results database by using the HCL DevOps Test Integrations and APIs (Test Integrations and APIs) command line.

The syntax to fetch specific results data from the results that are stored in a results database is as follows:

IntegrationTesterCmd <Options> fetch-result <execution_ID>

For example, if the tests or Suites that you ran are in a project, which has the results database configured. The project can be c:\MyProjects\testproject1.ghp. You can find the test execution ID or the scenario execution ID of the specific test or Suite from the Results Gallery tab or the console log in the Test Lab tab. You must then substitute the values in the following commands to get a specific test result data or a Suite result data from the results database:

The sample command to fetch a specific test result data can be as follows:

IntegrationTesterCmd --project c:\MyProjects\testproject1.ghp fetch-result test-execution-data:1234567

Where test-execution-data:1234567 is the test execution ID.

The sample command to fetch a specific Suite result data can be as follows:

IntegrationTesterCmd --project c:\MyProjects\testproject1.ghp fetch-result scenario-execution-data:3456789

Where scenario-execution-data:3456789 is the Suite execution ID.

After you run the command, the fetched results data is displayed in the command line window. You can view the details. If you want to retain a copy of the results fetched, you must copy the contents displayed into a text file and save it as an XML file. You can then use any XML viewer to view the XML contents.