Setting Match Style for VS transactions when creating VS with RR pairs

Products

• Service Virtualization

Issue/Introduction

This article will provide information on setting the Match Style for VS transactions when creating VS with RR pairs.

Be design, DevTest will create the Match Style of META transactions as SIGNATURE and SPECIFIC transactions as EXACT. Sometimes, need to configure the different Match Style and it can be done using the Sidecar files. The documentation on Sidecar Files and Match Tolerance through RR Pairs for more information.

Environment

DevTest releases 10.7.2 and later

Resolution

Users can use Sidecar file for requests with matchTolerance=Signature or matchTolerance=Operation or matchTolerance=Exact or matchTolerance=Selctive.

For example: There 3 RR pars like below which has the same requests but argument values are different:

RR1-req.txt

RR1-rsp.txt

 

RR2-req.txt

RR2-rsp.txt

 

RR3-req.txt

RR3-rsp.txt

Use Case 1:

A user needs to set the Match Style for first request RR1 as Signature and set the other 2 requests RR2 & RR3 as Exact. The sidecar file name should be like RR1-req-meta.properties and it should have matchTolerance=Signature.

RR1-req.txt

RR1-rsp.txt
RR1-req-meta.properties

RR1-req.txt
RR1-rsp.txt
RR1-req-meta.properties

RR2-req.txt
RR2-rsp.txt

RR3-req.txt
RR3-rsp.txt

When the VS is created with the above RR pairs, VSI is created with only one Specific Transaction instead of 3 Specific Transactions.  The reason for creating only one specific transaction is because the Transaction's  Signature is same for all transactions and recorder ignoring the other transactions.

Note:The META Transaction Match style is set based on the first specific transaction match style, so it will be set as Signature also. In case if the first specific transaction Match Style is Exact the also META Transaction is created with Signature as it can't be Exact by design.

To record all the other transactions, "Allow duplicate specific transactions" can be checked in the VSE Recorder screen as below:

 

The 3 created specific transactions will have the Match Style recorded as below:

META and First Specific Transaction will have Match Style=Signature because of the Sidecar file

RR1-req.txt
RR1-rsp.txt
RR1-req-meta.properties

The below 2 transactions are created with Match Style=Exact. Recorder uses the default functionality of specific transactions and create the Match Style.

RR2-req.txt
RR2-rsp.txt

RR3-req.txt
RR3-rsp.txt

 

Use Case 2:

A user need to set the Match Style for second request RR2 as Signature and set the other 2 requests RR1 & RR3 as Exact. The sidecar file name should be like RR2-req-meta.properties and it should have matchTolerance=Signature. The RR pairs should look like below.

RR2-req.txt
RR2-rsp.txt

RR3-req.txt
RR3-rsp.txt

RR1-req.txt
RR1-rsp.txt

RR2-req.txt
RR2-rsp.txt
RR2-req-meta.properties

RR3-req.txt
RR3-rsp.txt

When VS is created with "Allow duplicate specific transactions" checked in the VSE Recorder, VSI is created with 3 Specific Transactions. Match Style for the first & third transaction is Exact and for second transaction Signature. The META transaction Match Style is also set to Signature as it can't be Exact from the first specific transaction's Match Style.