Manage Your Test Environment With Virtualize

Parasoft represents test environments as visual diagrams that enable organizationally and geographically separated teams to align on which components are required for test execution. From there, a unified test execution strategy can be developed that includes virtualization services to fill in gaps where components are unavailable, unstable, or constantly evolving.

Knowing when the test environment is ready for testing can save a tremendous amount of time while eliminating environment-based test failures. With Parasoft Virtualize, you can identify which components in the test environment are misbehaving or out of sync, so they can be dynamically replaced with virtual services. Each of these components can be monitored in real-time to understand the flow of information through the system, and preemptively validate component health prior to test execution. By capturing real system transactions, Parasoft enables more realistic virtual services to be created.

Parasoft Virtualize users can create lightweight virtual services both through the feature-rich desktop and the  intuitive web interface that enables even novice users to build simulations from service definitions, recorded traffic, or even prototype services that do not exist. These services can then be added into an environment where they can be provisioned and consumed by non-virtualization experts.

The performance characteristics of virtual services can be controlled as well. To support earlier-stage performance testing, users can build virtual services with realistic (or unexpected) performance profiles, augmenting existing test environments with proxies to redirect the flow of traffic dynamically and enabling rapid switching between real and simulated versions of your dependencies without having to redeploy the application.

Parasoft monitors (i.e. “proxies”) sit in between the application and its dependencies and will dynamically switch into failover mode if the real system ever goes off-line. In failover mode, all service traffic is routed to a virtual service to keep your environment stable.

Users can bundle groups of virtual services together into an environment instance that provides specific behavior to support a specific testing initiative (e.g. positive behavior when QA is testing the happy path, negative behavior when development needs to reproduce something, fast or slow performance to support load testing, etc.). These instances can then be selected and provisioned in a self-service method by testers, to ensure their environments behave exactly the way they need, whenever they need them.

Users can leverage environmental presets to configure test environments prior to nightly (or continuous) automated test execution, and don’t have to worry about the environment causing test cases to fail. By connecting Virtualize to the CI infrastructure, users can dynamically deploy-and-destroy disposable test environments as a part of the Continuous Delivery pipeline.

Host commonly used virtual services in your own internal marketplace to not only promotes greater sharing of virtual services but also help users understand what virtual services exist in the library and allow for rapid deployment to either a shared server or local environment.

Clone entire environments for use in testing and deploy all of the artifacts test cases test and test data either to your local environment or to a containerized environment for rapid testing.

Leverage parasoft test data repository to get access to valuable data in your virtual services. Users can collaborate on a team level by sharing a repository or an individual can host their own private repository that contains just the data that they need.