See Service Virtualization Details
Teams testing today's distributed applications commonly find testing efforts delayed or shortchanged as a result of constraints related to:
- Access: Functional and performance testing of the application under test typically involves transactions that pass through multiple dependent systems, which are commonly unavailable, evolving, or difficult-to-access for testing. When these systems are available for testing, it is commonly restricted to limited and/or inconvenient times.
- Costs: Transaction and bandwidth fees involved in accessing third-party systems, third-party services, or shared testing environments can quickly escalate—especially for large-scale, high-throughput load or stress tests.
- Performance: Teams need to test and tune the application under test against the realistic performance expectations of the interconnected system components—yet realistic performance of each of the dependent systems is often difficult to achieve in a test environment.
Service virtualization is designed to alleviate these challenges. It provides QA and development teams access to dependent system components that are needed to exercise an application under test (AUT), but are unavailable or difficult-to-access for development and testing purposes. With the behavior of the dependent components "virtualized," testing and development can proceed without accessing the actual live components.
For details on how Parasoft's service virtualization helps organizations test earlier, faster, more thoroughly, and more accurately—significantly reducing
the risk of application failure—see our service virtualization page.