Featured Webinar: Unveiling Parasoft C/C++test CT for Continuous Testing & Compliance Excellence | Watch Now

Image of someone working on laptop

Integrated API Testing

Incorporate API Testing With Parasoft Virtualize

Integrate API testing into Parasoft Virtualize to achieve predictability in your test results

Parasoft Virtualize integrates seamlessly with Parasoft SOAtest to increase test automation by reducing test environment provisioning time and aligning test scenarios with environment instances that preconfigure use of both real and virtual services. This integration enables users to produce just the right type of behavior for any given test scenario.

Screenshot from integrated API and service virtualization video. Graphics from different systems working together with graphic of computer screen to the right.

How does it work?

Virtual services created in Parasoft Virtualize can be utilized and managed by any automated testing solution using CI/CD plugins or Parasoft’s REST API. Virtual services can easily be deployed, updated, and deleted using REST API calls, making it easy for testers to quickly set up dependent virtual services.

When you combine Parasoft Virtualize with Parasoft SOAtest, teams benefit from the efficiencies that enable virtual services and API tests to share message formats, payloads, tools, and settings. Parasoft SOAtest produces test assets that can be dynamically reconfigure, making test cases portable, so you can test the same applications in different environments, regardless of where they are deployed and can be packaged into a complete test environment with full control over everything from behavior to performance to data.

This makes development and testing of new APIs much easier because you can design a prototype of a new API with a virtual service, and then build tests against that virtual service as the actual service is being developed — an easy way to approach TDD for API testing.

SOAtest and Virtualize also share data sources, variables, scripts, and even communicate with each other during test execution to determine and control the flow of test execution. This synergy enables you to immediately test and build regressions against your virtual services, so you can easily identify if it is out of sync with the real system, and use Parasoft’s built-in Change Advisor to update both the API test and the virtual service, when changes occur.

There’s runtime synergy between SOAtest and Virtualize as well. Virtual services monitor and report on transactions that are flowing through the application, so users can inject calls into their application for validating end-to-end functionality. As messages flow through the different interfaces, Virtualize will report back to SOAtest at key interaction points for efficient end-to-end test scenarios.


Benefit from the Parasoft Approach

Easier to create and deploy virtual services

Parasoft Virtualize is deployable locally on individuals desktops or remotely on servers that are hosted on-prem or in the cloud, and any testing solution can leverage its powerful REST API to create and deploy virtual services right in their local environment during testing.This provides users with an easy way to unblock testing without the need for additional tools, frameworks, or cumbersome automated processes.

Simplify orchestration of continuous testing

Parasoft’s intuitive web interface provides a place to manage the coordination and orchestration of tests and virtual services in the context of your existing automation framework (i.e. Jenkins, Team City, Bamboo, and Microsoft Azure DevOps). Parasoft’s Environment Manager is the only product available with a GUI that makes it easy to manage the test cases, virtual services, endpoints, test data sources, performance configurations, and execution details.

Dynamically reconfigure your test environment in seconds

Instead of individually managing each test-environment provisioning activity as an individual build step with a script or plugin, Parasoft’s web interface reduces the time and number of manual configurations needed by providing a visual mechanism to diagram the end-to-end test flow. You can then provision the diagram as a build step to dramatically reduce the effort of integrating end-to-end test automation into the CI/CD pipeline.