Features

SV-as-Code includes the following key features:

Virtualizing single/multiple virtual services for a test case.

Lets you create one or more multiple virtual services for a single test case

Virtualizing services at class and method scope level

Lets you create virtual service with class rules and method rules

Virtual Services from Request/Response pair.

SV-as-Code lets you gather transactions for virtual service created from request/response pairs.

Virtual Services from Virtual service model(.vsm).

After virtualization, a VSM must be deployed to the VSE. The VSM defines how behavior patterns get used and query the service image to determine how to respond. The VSM knows how to navigate the service image. SV-as-Code lets you gather transactions for virtual service deployed from virtual service model file.

Virtual Services from recording session file(.vrs).

SV-as-Code lets you gather transactions for virtual service of non-HTTP mode i.e. VRS files.

Virtual Services from raw traffic file.

SV-as-Code lets you gather transactions for virtual service created from raw traffic files.

Parameterized DevTest Annotated virtual services

Lets you define different parameters for virtual service like port, login information, etc. which refers to parameters in the response file.

Virtualizing both REST and SOAP services.

SV-as-Code supports virtualizing both REST and SOAP services to fully cover your web service virtualization.

Reuse and share virtual assets across teams.

SV-as-Code also allows developers to import and export Request/Response (RR) pairs to reuse and share virtual assets across teams. This saves time by eliminating the need to create new assets from scratch.