Prerequisites for running HTTP stubs

You can find information about the tasks that you must complete before you run HTTP stubs on HCL OneTest Server.

Enabling the running of HTTP stubs

Before you run the HTTP stubs from HCL OneTest Server, you must check for the following conditions and perform the actions indicated:
If... Then...

The stubs that you want to run are configured to use an HTTP proxy.

You must set up the HTTP proxy. See Setting up the HTTP proxy.

You are working with HCL OneTest Server V10.1.1 installed on OpenShift.

You can perform any of the following actions:
  • Run the following helm command at the time of server installation:

    --set execution.ingress.type=nodeport

  • Configure the following argument in the Java Arguments field in the Advanced settings panel of the Execute test asset dialog box when you want to start a stub from the Execution page:
    -Dexecution.ingress.type=nodeport

You are working with HCL OneTest Server V10.1.0 installed on OpenShift.

You are working with HCL OneTest Server V10.1.1 installed on Ubuntu by using microk8s.

You must perform the following actions:
  1. Run the ubuntu-init script to update the server installation, if you have not run this at the time of installation.
  2. Install the HTTP proxy V10.1.1.
  3. Configure the host names that are used by the HTTP stub endpoints that must be in the following form:
    in-*.<INGRESS_DOMAIN>

    Where the wildcard * is replaced with the generated value of the host name.

    For example, if you use the following host name:
    <myots>.<ipaddress>.nip.io
    The DNS is resolved to <ipaddress>.
    If you are not using the nip.io, then you must configure the DNS of the client that calls the stub, so that the host name is resolved to the following form:
    in-*.<INGRESS_DOMAIN>

You can proceed to run the HTTP stubs. See Starting a stub.