You can create a Mock Service by uploading Transactions from a supported file type. You can also create a Mock Service from an existing Service or a Template. Or, you can create a Mock Service using the Blazemeter Proxy Recorder or by using a MAR file from Service Virtualization. If you want to add more Transactions to the Service, you can upload additional Transactions without having to switch tabs. As you create your Mock Service, you can select the specific Transactions that you want to include and then run them to make them available for tests.

• Create a Mock Service by Uploading Transactions
• Create a Mock Service from Existing Transactions
• Create a Mock Service from a Recording
• Create a Mock Service from a MAR File
• Create a Mock Service from a Mock Service Template
• Assign a Template to a Mock Service

When you test against a Mock Service, the Mock Service attempts to match an incoming request against any of its Transactions. The Transactions can be fully formed requests or regular expressions that an incoming request will match against. When a Mock Service receives a request that would be a match with multiple Transactions, the Mock Service matches against the Transaction with the lowest number in the Priority field. For example, if you have an incoming request matching multiple Transactions, the Transaction with a Priority value of 1 is picked up first if it matches that request. If multiple Transactions have the same priority, the Mock Service matches the most recent Transaction (with the highest Transaction ID number).

Consider this matching logic when determining which Transactions to add to a Mock Service, and whether one or more multiple Mock Services are required to meet testing requirements. For example, assume you have a Mock Service for a service that searches by zip code with two transactions: Transaction A matches on a parameter value of 75024, and Transaction B matches any five-digit number. You may want the Transaction with the more specific matching criteria (Transaction A) to have the higher priority value so that it matches first, and the broader matching criteria (Transaction B) is only matched if the specific zip for Transaction A is not entered.

Create a Mock Service by Uploading Transactions

1. Click the Mock Services tab.
   
2. Click Mock Services at the top of the page.
   
3. Click Create a new Mock Service, and select Create from Transactions.
   
   A new row is added to the top of the Mock Services list.
4. Enter a name for your Mock Service in the Mock Service Name field.
5. Click the arrow next to the Mock Service name to expand the details for the Mock Service.
   
6. Enter a description for your Mock Service.
7. Drag your transaction file into the upload area.
   • This file should contain all of the transactions that you want to use for your Mock Service.
   • Note: If you want to upload multiple Swagger files using a zip file, the main file in the zip file must be named index.json or index.yaml for the upload to work.
   • You can also click the Upload area to browse to the file.
     
     The Import Transactions dialog opens.
     
8. Select the Service you want to add these transactions to. The Service is a representation of the underlying live service, and it serves as a container for the Transactions you will upload. If an existing Service contains Transactions that are needed for this Mock Service, select the existing Service.
   To create a new Service:
   1. Click Select Service.
   2. Enter the name for your new Service and click Add Service.
9. If you want to assign one or more tags to these transactions, type the tag name(s) in the Tags field and press Enter.
   • Tags make Transactions easier to identify, especially within a large Service. You can provide tag definitions here to apply the defined tags to all imported Transactions. Or you can define tags at the Transaction level after import.
   • To enter multiple tags, press Enter after each tag name.
10. Click Import.
11. Select the Service you just selected or created from the Select Service drop-down.
12. Select the location that you want to deploy your Mock Service to from the Location drop-down.
    • Unless you plan to run the Mock Service in a private location, select from the available Google Cloud Platform locations (US East or EU West) depending on your location.
13. Select either HTTPS or HTTP from the Endpoint drop-down.
    • The default is HTTPS.
14. Select the check box for each Transaction you want to include in your Mock Service and click the arrow to move them from the Other Transactions in Your Catalog to the Transactions in This Mock Service column.
    
    
    • You can search by tag or text in the Other Transactions in Your Catalog column to find the Transactions you want to include.
    • Click the check box in the header to select all Transactions.
      Note: This check box selects all of the Transactions on the current page. It does not select all Transactions in the service.
15. (Optional) Expand each Transaction in the Mock Service and enter values in the Priority field to control the matching order to follow when a request matches multiple Transactions.
    
    The Transaction with the lowest number matches first. By default, all Transactions have the same Priority value, and a multiple matching scenario matches on the Transaction with the highest ID number.
    Setting a priority for a Transaction only applies to that Transaction within the specific Mock Service. In other Mock Services or templates, the Transaction may have a different priority value.
16. Click the Parameters tab.
17. In the No Matching Requests field, choose the correct logic for when a request against the Mock Services does not match any of the provided transactions. The request can either throw an error or be redirected to the live service.
18. Set the Think Time in milliseconds to control the amount of time spent between when the Mock Service receives a request and returns a response. The default is 0, but you can update the field to simulate delayed responses.
19. Click Save.
    Your Mock Service is saved and added to the list of available Mock Services.
    

The Mock Service is not active until you run it. Click Run Mock Service to run it now, and see Running a Mock Service for next steps.

Create a Mock Service from Existing Transactions

1. Click the Mock Services tab.
   
2. Click Mock Services at the top of the page.
   
3. Click Add new mock service.
   
   A new row is added to the top of the Mock Services list.
4. Enter a name for your Mock Service in the Mock Service Name field.
5. Select the Service that contains the Transactions for your Mock Service.
6. Select the location that you want to deploy your Mock Service to from the Location drop-down.
   • Unless you plan to run the Mock Service in a private location, select from the available Google Cloud Platform locations (US East or EU West) depending on your location.
7. Select either HTTPS or HTTP from the Endpoint drop-down.
   • The default is HTTPS.
8. Click the arrow next to the Mock Service name to expand the details for the Mock Service.
   
9. (Optional) Enter a description for your Mock Service.
10. Select the check box for each Transaction you want to include in your Mock Service and click the arrow to move them from the Other Transactions in Your Catalog to column and add them to the Transactions in This Mock Service.
    
    
    • You can search by tag or text in the Other Transactions in Your Catalogs column to find the Transactions you want to include.
    • Click the check box in the header to select all Transactions.
      Note: This check box selects all of the Transactions on the current page. It does not select all Transactions in the Service.
11. (Optional) Expand each Transaction in the Mock Service and enter values in the Priority field to control the matching order to follow when a request matches multiple Transactions.
    
    The Transaction with the lowest number matches first. By default, all Transactions have the same Priority value, and a multiple matching scenario matches on the Transaction with the highest ID number.
    Setting a priority for a Transaction only applies to that Transaction within the specific Mock Service. In other Mock Services or templates, the Transaction may have a different priority value.
12. Click the Parameters tab.
13. In the No Matching Requests field, choose the correct logic for when a request against the Mock Services does not match any of the provided transactions. The request can either throw an error or be redirected to the live service.
14. Set the Think Time in milliseconds to control the amount of time spent between when the Mock Service receives a request and returns a response. The default is 0, but you can update the field to simulate delayed responses.
15. Click Save.
    Your Mock Service is saved and added to the list of available Mock Services.

The Mock Service is not active until you run it. Click Run Mock Service to run it now, and see Running a Mock Service for next steps.

Create a Mock Services from a Recording

You can record a series of interactions from your browser, capture those interactions as transactions, and create a mock service based on those transactions. You use the Blazemeter Proxy Recorder to record the interactions.

1. Click the Mock Services tab.
   
2. Click Mock Services at the top of the page.
   
3. Click Create a new Mock Service, and select Create from Recording.
   
   The Blazemeter Recorder page appears in a separate tab.
4. Follow the steps (starting with Step 3) in Creating the Proxy Recorder to create your proxy for recording.
5. Follow the steps for setting up recording based on your operating system:
   
   • Recording Using Android Devices
   • Recording Using Apple Devices
   • Recording Using Firefox 
   • Recording Using Chrome
6. Click the Record button, and record the necessary interactions within your application.
7. Click Pause when finished.
8. Click Mock Service to export the recording to a Mock Service.
   This creates a Mock Service under the selected Service with all of the recorded Transactions assigned to it.
9. Disable any proxy settings you had to enable to create the recording.

Create a Mock Service from a MAR File

When you create a Mock Service from a MAR file, you are simply allowing Blazemeter to deploy the underlying virtual service to a Service Virtualization VSE. The virtual service runs on the VSE and can be edited in Service Virtualization using the DevTest Portal or Workstation.

1. Click the Mock Services tab.
   
2. Click Mock Services at the top of the page.
   
3. Click Create a new Mock Service, and select Create from MAR File.
   
   A new row is added to the top of the Mock Services list.
4. Enter a name for your Mock Service in the Mock Service Name field.
5. Select the Service that contains the MAR file for your Mock Service.
6. Select the VSE that you want to deploy your Mock Service to from the Select VSE drop-down.
   If you don't see the VSE you need, contact your administrator or configure the Service Virtualization integration to add the Enterprise Dashboard on which your VSE is managed.
7. Select the MAR file for the Mock Service. 
   Note: You can also upload a MAR file directly during Mock Service creation using the upload box. This procedure assumes you have already uploaded the MAR file to the Asset Catalog. For more information, see Adding MAR Files.
   A Mock Service can only accept a single MAR file.
   
   You can view helpful information about the MAR file, such as transport protocol, virtual service name, and number of transactions. Expand the MAR file entry to see when it was stored in Blazemeter. You can view more detailed information about the MAR file in the Asset Catalog. For more information, see Adding MAR Files.
8. Click the Parameters tab.
   
   The parameters on this tab control the behavior of the virtual service when it is deployed to a Service Virtualization VSE:
   Think Time Scale: Controls how long the virtual service waits before acting on a received request. This is similar to the Think Time setting within a Transaction-based Mock Service. Within Service Virtualization, this is a percentage that derives a realistic think time based on recorded data and accounting for any overhead processing time.
   

   Concurrent Capacity: Controls the number of processing threads allocated to handle requests to the virtual service within Service Virtualization. This value typically only applies to virtual services deployed to a VSE in Performance mode.

   Group Tag: Enter any group tag values to display in Service Virtualization. The group tag is a value that lets you build groups of virtual services in Service Virtualization.
9. Click Save.
   Your Mock Service is saved and added to the list of available Mock Services.

The Mock Service is not active until you run it. Click Run Mock Service to run it now, and see Running a Mock Service for next steps.

Create a Mock Service from a Mock Service Template

At any time after saving the Template, click Create Mock Service to the right of the Template name to dynamically provision a Mock Service that includes the transactions in the Template.

Assign a Template to a Mock Service

You can assign a Template to a new or existing Mock Service at any time. To assign a Template to a Mock Service:

1. Expand the Mock Service and click the following icon:
   
2. Select the Template to assign and click Apply.

The Template is assigned to the Mock Service. If the Mock Service already contained Transactions, they are overwritten by the Transactions in the Template.