The Asset Catalog tab on the Service Virtualization tab contains all imported Transactions that you can use to create a Mock Service.
A Transaction is a request/response pair that is associated with a given Service. For example, in the Swagger Petstore, GET /pet/{petId} and the associated response is a Transaction. A request in a Transaction can be a full, valid request, like the Petstore example, or an expression that can be matched to a broader range of real requests.
Every time you add a Transaction, it is stored in the Transaction Repository. The Transaction Repository keeps a record of all Transactions and supports a variety of formats. When you create a Mock Service, you are simply grouping together Transactions from the repository.
The Transactions tab lists all of the Transactions that are available to you. You can filter the list of Transactions by Service name to make it easier to find the specific Transaction that you’re looking for. You can also search for any tags that you assigned to your Transactions, by the Transaction name, or by the request URL.
Restriction: The BlazeMeter Virtual Service Environment (MAR file support) has reached its end of life (EOL) and is no longer supported. Please reach out to your account team for any questions.
You can add transactions in the following ways:
Preconfigured Transactions
BlazeMeter comes with four preconfigured groups of Transactions to help illustrate how the product works and to get you started with assets for the following common third-party services:
AWS S3: Provides sample Transactions for testing the AWS S3 cloud storage service. Transactions are included for testing object additions, deletions, copies, searches, and negative scenarios.
Facebook Login: Provides sample Transactions for testing the integrated Facebook login functionality in your application. Transactions include a mixture of positive and negative scenarios, identified by tags, that cover the most common outcomes when attempting a Facebook login.
Salesforce Login: Provides sample transactions for testing the integrated Salesforce login functionality in your application. Transactions include a mixture of positive and negative scenarios, identified by tags, that cover the most common outcomes when attempting an integrated Salesforce login:
Open Banking: Provides sample transactions for testing services in your application that use the standard Open Banking APIs. The Open Banking Sample service includes transactions for a variety of operations, such as loan offers, balance inquiries, and account information. Duplicate these transactions to mock testing scenarios for open banking operations:
