Features

SV-as-Code includes the following key features:

Version 1.4.0

Following features are supported with annotations DevTestVirtualServiceV3 and DevTestVirtualServicesV3 and Java API wrapped on Service Virtualization API v3

Virtualizing single or 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 services created from request/response pairs or zip of multiple request/response pairs.

Virtual Services from Swagger file/url

SV-as-Code lets you gather transactions for virtual services created from Swagger file or url.

Virtual Services from Rail file/url

SV-as-Code lets you gather transactions for virtual services created from Rail file or url.

Virtual Services from Wadl file/url

SV-as-Code lets you gather transactions for virtual services created from Wall file or url.

Virtual Services from VSM/VSI file

SV-as-Code lets you create and deploy Virtual Service from existing VSM/VSI files and change the port and documents.

Update data and active config file while creating or updating virtual service

SV-as-Code lets you create and update Virtual Service and update data and active and config.

Undeploy existing Virtual Service before deploying Virtual Service

SV-as-Code lets you undeploy existing service and control the behaviour using property devtest.undeploy.ifexist defined in local-svascode.property file.

Encrypt password properties defined in property file

SV-as-Code encrypts the devtest.password and devtest.keystorePassword properties defined in local-svascode.property file.

Connect to DevTest configured in SSL mode

SV-as-Code lets you connect to the DevTest configure in SSL mode by defining devtest.protocol, devtest.keystore and devtest.keystorePassword properties defined in local-svascode.property file or the parameters defined in DevTestVirtualServer annotation.

Version 1.3.2

Following features are supported with annotations DevTestVirtualService, DevTestVirtualServices, DevTestVirtualServiceFromVrs and DevTestVirtualServicesFromVrs and Java API wrapped on DevTest Rest Invoke API

Virtualizing single or 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 services 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 as how behavior patterns are 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, that is, 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, and so on, 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 completely 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 process saves time by eliminating the need to create new assets from scratch.