Starting stubs

Test Virtualization Control Panel, Test Integrations and APIs, Docker, or IBM Cloud Private can be used to start stubs.

There are some limitations on stubs depending on how they are started. The following table describes those limitations.

If a stub is published to Test Virtualization Control Panel and started by Test Virtualization Control Panel...	If a stub is started by Test Integrations and APIs...	If a stub is published to a Dockerfile and build context and an image built and run by Docker...	If a stub is published to IBM Cloud Private resource files (Kubernetes) and a resource created and run by IBM Cloud Private...
There are no running time limits on the stub.	It will run for only 5 minutes unless the associated test scenario requires it to run for a longer period.	There are no running time limits on the stub.	There are no running time limits on the stub.
There are no transactions per second (TPS) limits on the stub.	There is a limit of 1 TPS on the stub.	There is a limit of 10 TPS on the stub.	There is a limit of 10 TPS on the stub.

The following topics describe how to use Test Virtualization Control Panel, Test Integrations and APIs, Docker, or IBM Cloud Private to start stubs.