Running a Mock Service

Running a Mock Service makes it available for you to test against. Running a Mock Service is a simple two step process:

Run the Mock Service
Connect your application to the running Mock Service

Run a Transaction-based Mock Service

Find your Mock Service on the Service Virtualization tab and click Run.

The Status changes to Running, and the endpoint for the running Mock Service appears.
Copy the endpoint for the Mock Service and redirect your application to point to the Mock Service instead of the real Service.
Do not refer to a Kubernetes-based Mock Service by its plain IP address.
You implement the redirect configuration in your application, not within BlazeMeter. How you do it depends on your application. It's often as simple as changing a value in an application properties file from the live service address to the Mock Service endpoint.
After you redirect your application to the Mock Service, an application restart may be required.

The user and date when the Mock Service was Created and Updated are indicated here for your reference. After you have run a Mock Service at least once, no matter with which status (running, failed, stopped, configuring), the details view also indicates the Version of the image.

Tip: If you are not updating images automatically and you are reporting an issue, and BlazeMeter Support asks you for the Mock Service image version where you are seeing the issue, look up the version number here.

Filter Mock Services by Status

In the Mock Services tab, you can filter the transactions based on their status. The filer helps in cases where there are many Mock Services defined. By using this filter option, it is easy to display a subset of Mock Services based on a certain status. For example, you can display only Mock Services that are running or stopped.

Bulk Run Mock Services

You can bulk run Mock Services from the Service Virtualization tab or from the Asset Catalog.

Click the Service Virtualization tab.
Click Mock Services at the top of the page.
Find your Mock Services on the Service Virtualization tab.
Select the checkbox next to each Mock Service that you want to run.
Select the Run Mock Services button next to the Mock Service.

If one of the services is already running when you apply the bulk action, the Run Mock Services button is disabled. The converse is true, if one of the services is in the stopped state, bulk stop is disabled. Additionally, you can also delete Mock Services in bulk.

Bulk actions are limited to deploying 25 Mock Services at a time.

Configure SSL Connection to Mock Service

BlazeMeter can configure HTTPS connections to Mock Services over TLS/SSL. When you run a Mock Service over HTTPS, verify that your application can connect to the Mock Service. You can connect your application using the SSL certificate that we provide.

Cloud Deployment

When you deploy a Mock Service to a Cloud location, it uses a certificate signed by the Let's Encrypt certificate authority.

If the application or browser you're using to access a Service Mock does not trust certificates issued by Let's Encrypt, then you will need to configure it to trust the following certificates:

Let’s Encrypt Authority X3 intermediate certificate
DST Root CA X3 root certificate, which is used to cross-sign at the previous certificate

Refer to your application, language, or operating system documentation for details on how to import these certificates.

Private Location Deployment

When you deploy a Mock Service to a Private Location, the HTTPS endpoint is based on the IP address of the agent that deployed the Mock Service. No FDQN resolution occurs by default.

Use the following self-signed certificate to connect to a Mock Service deployed to a private location:

If you want to generate a hostname for the HTTPS endpoint, add an entry to your operating system's host file that lists the IP address followed by a host name that ends with mock.blazemeter.net.

Example:

10.1.1.100 testmock.mock.blazemeter.net