As part of your system-wide load test, you will need to test all of the services that partake in your business process. Some business processes contain services that are not available. For example, your business process might include a service that is still in development or incurs a cost, such as processing a credit card through a third-party vendor.
To facilitate load testing these business processes, LoadRunner Controller integrates with HP Service Virtualization. This integration enables LoadRunner users to define services that will be virtualized during test execution so that the tested business process is performed as required.
By using a virtual service, you can load test and replace actual services with virtual services that mirror both the data model Definition of the data that is sent by the service to the server and the expected response. You can define several data models for one service. and the performance modelDefinition of the expected performance, such as reponse time, of the service..
To learn more about Service Virtualization or to download it, see the HP Service Virtualization site. After you install Service Virtualization, refer to the HP Service Virtualization User Guide for setup information.
The workflow below explains how Service Virtualization integrates with LoadRunner processes:
Virtual Service Locks
When your scenario contains virtualized services, these services are automatically locked and cannot be used by other users while the scenario is running. Virtualized services may locked by you or other users for editing, simulation, or deployment.
- If your scenario includes a service that has been locked by another user, the run will fail and the scenario will send an error message to the Output pane.
- If your scenario is running and you update the scenario to include a service that has been locked by another user, the scenario continues running and sends a warning message to the Output window.
Virtual Service Modes
The following modes apply to the virtual services.
- Learning mode. The virtual service works as a proxy to record and learn the behavior of a real service. The virtual service forwards the real communication between a client and a service. In this mode, any communication through the virtual service is added to the virtual service's simulation models.
- Standby mode. The virtual service redirects requests to the real service, and redirects responses from the real service back to the client. The virtual service is not learning, and not simulating.
- Simulating mode. The virtual service responds to client requests according to learned behavior. This is the main use of the virtual service, and the mode you use for testing purposes.