Home
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 - 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.
Troubleshooting: HCL OneTest™ Virtualization
You can use workarounds to common problems that you might encounter when you use HCL OneTest™ Virtualization.
Troubleshooting the HTTP/TCP proxy
While using the HTTP/TCP proxy, you might encounter some problems that you can troubleshoot.
Viewing diagnostic output on a proxy connection failure
When the HTTP proxy fails to open a connection to a live system or stub, it dumps the exception message and output from the netstat command (open connections and used ports) to a file on your computer.

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.
- API 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. This guide is intended for API testers.
- 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.
  - HCL OneTest™ Virtualization overview
    HCL OneTest™ Virtualization is software that is used for creating, maintaining, publishing, and running message-based stubs and database stubs.
  - Task flow: Working with the HCL® Quality Server Environments dashboard
    You can use the HCL® Quality Server Environments dashboard to perform various tasks such as starting, stopping stubs and scenarios, and modifying stub configurations after you have published stubs to HCL Quality Server. You can also lock the environment that contain the published stubs.
  - Virtualizing HTTP
    You can simulate an HTTP connection with a virtual service, also known as a stub.
  - Virtualizing HTTPS
    You can simulate an HTTPS connection with a virtual service, also known as a stub.
  - Virtualizing TCP
    You can simulate a TCP connection with a virtual service, also known as a stub.
  - Virtualizing a REST API without recording or synchronization
    You can virtualize REST APIs by using the Recording Studio, or by synchronizing WADL, Swagger, or RAML documents. When none of these options is available, you can still manually virtualize REST APIs that use path parameters.
  - Creating message-based stubs
    In HCL OneTest™ API, there are several methods that you can use to create a message-based stub.
  - Modifying message-based stubs
    You can use either the Test Editor or the Stub Editor to create, modify, and enhance any legacy or new stubs created by HCL OneTest™ API.
  - Creating and modifying database stubs
    You can create and modify database stubs in HCL OneTest™ API.
  - Configuring stubs to connect to HCL® Quality Server and the HTTP proxy
    A stub running on its own may not be sufficient in some cases, because it might have dependencies on services such as HCL® Quality Server or the HTTP proxy. If the stub is running on the public cloud and the services are running in the enterprise, you must configure the stub to connect to these services.
  - Publishing and running stubs
    You can publish stubs that are created in HCL OneTest™ API to HCL® Quality Server, Dockerfile and build context, Kubernetes, or Istio, if the stub is based on a supported transport.
  - Viewing results in HCL® Quality Server
    You can use HCL® Quality Server to display the results of tests that you run in both HCL OneTest™ API and HCL Quality Server.
  - Viewing usage statistics of virtual services in HCL® Quality Server
    HCL® Quality Server collects and stores usage metric data. The metric data might include the number and types of actions that are used, the features that are used in the workbench, details about Operating System or languages set while running, and so forth. You cannot view the metric data on the HCL Quality Server user interface, but it is available from the underlying implementation. Storage is either managed by H2 or optionally Apache Cassandra.
  - Viewing reports in HCL OneTest™ Server
    All the project stakeholders can view test reports for multiple testing products from the Results page on HCL OneTest™ Server. You can access the Results page from a web browser. Therefore, there is no need to install the desktop client.
  - Troubleshooting: HCL OneTest™ Virtualization
    You can use workarounds to common problems that you might encounter when you use HCL OneTest™ Virtualization.
    - Handling many RunTests instances
      When you start a number of stubs with HCL OneTest™ Virtualization, you see that many RunTests instances are running and the amount of available system memory is reduced.
    - Troubleshooting stubs
      You can troubleshoot common problems that you might encounter while you use stubs.
    - Troubleshooting the HTTP/TCP proxy
      While using the HTTP/TCP proxy, you might encounter some problems that you can troubleshoot.
      - Sample log files for the HTTP/TCP proxy
        The sample log files show common messages that you can use to troubleshoot the HTTP/TCP proxy.
      - Viewing diagnostic output on a proxy connection failure
        When the HTTP proxy fails to open a connection to a live system or stub, it dumps the exception message and output from the netstat command (open connections and used ports) to a file on your computer.

Viewing diagnostic output on a proxy connection failure

When the HTTP proxy fails to open a connection to a live system or stub, it dumps the exception message and output from the netstat command (open connections and used ports) to a file on your computer.

You can find the file in the home directory of the user account that is running the proxy, and the filename is in the following format ritproxy-netstat-timestamp.txt. By default, the proxy writes one dump file every ten minutes.

To turn the dump collection on or off, set the following JVM argument to true or false respectively: -Dcom.ibm.rational.rit.netstatdump. The default value is true.
To configure the file path, update the following JVM system property: com.ibm.rational.rit.netstatdump.dir.
To configure the rate at which the proxy writes to a file, update the following system property: com.ibm.rational.rit.netstatdump.mininterval. For example, -Dcom.ibm.rational.rit.netstatdump.mininterval=1 means that the proxy creates a dump file every one minute. To avoid imposing any such limits, set the value to zero. When you try to recreate an issue, use a small value.
To include refused connection exceptions in the file dump, update the value of the following JVM argument to true: –Dcom.ibm.rational.rit.netstatdumpconnectionrefused. The default value is false.

Table 1. Adding JVM arguments
If you are running the proxy as a process...	If you are running the proxy as a Windows service...
Open the startup file of the HTTP/TCP proxy (startup.bat on Windows computers and startup.sh on non-Windows computers) in a text editor. Add the desired JVM arguments to the active `%_RUNJAVA%` line. Save and close the file. For the changes to take effect, stop the HTTP/TCP proxy and start it again. For instructions, see Starting and stopping the HTTP/TCP proxy.	Run editProxyService.bat from an Administrator command prompt. Add the desired JVM arguments on the Java page. Click Apply and close the properties dialog. For the changes to take effect, stop the HTTP/TCP proxy and start it again. For instructions, see Starting and stopping the HTTP/TCP proxy.