Capture a Value that is Generated During Execution Time and Create a Filter
search cancel

Capture a Value that is Generated During Execution Time and Create a Filter

book

Article ID: 14958

calendar_today

Updated On:

Products

CA Application Test CA Continuous Application Insight (PathFinder) Service Virtualization

Issue/Introduction

 

To capture a property value that is generated from the execution result, you can run the test in the ITR and export the properties.

How to capture a value that is generated during execution time and create a filter?

Environment

 

All supported releases and platforms of DevTest.

Cause

 

N/A

Resolution

 

Below are the steps to capture a property value that is generated during execution time:

1. Execute the test case or the VSM in the ITR.

2. Send some requests to it and stop the ITR execution by using the stop button or Cancel option.


3. Select the step under Execution History, and go to the Properties tab:



In this case the property we are looking for is the "lisa.vse.request" which contains the request payload.

4. Still in the Properties tab, at the bottom of the ITR, scroll to the right to find the arrow icon "Export the value of these properties from runtime to design time" and select it.



The "Select Properties" window will open:

 

5. Select "Select All" option and "Export".

6. The message "This will save the selected properties into the design time. Do you also want ".rsp" selected properties to be saved as the step responses?" Select "Yes".

7. Minimize the ITR and go to the step where the filter will be added. In this case the Listener Step is being used.

8. The filter added was "Created Properties Based on Surrounding Values". In this example the "lisa.vse.request" is the property being used:

The filter uses a "paint the screen" technique.

"Paint the screen" gives you great flexibility to define what in the HTML you want to parse as properties. Mark the text in one of the following ways:
Text that must appear in the response exactly as shown: a Must block.
Text that is not required to appear in the response, or can change: an Any block.
Text that is stored in a property: a Property block.
The text is marked using the icons at the bottom of the editor.

The property {{request_User}} is now the property that can be used during the VSM or test case execution.

 

Additional Information

 

If your test case is using subprocess and you want to filter a value coming from the subprocess test execution, you need to create the filter in the subprocess test case itself and then select the property in the 'Result Properties' that will return from the subprocess to the main test case.

For more information regarding the "Created Properties Based on Surrounding Values" filter, you can check our documentation and refer to section Create Property Based on Surround Values.

Attachments

1558700680601000014958_sktwi1f5rjvs16k8c.png get_app
1558700678607000014958_sktwi1f5rjvs16k8b.png get_app
1558700676669000014958_sktwi1f5rjvs16k8a.png get_app
1558700674794000014958_sktwi1f5rjvs16k89.png get_app
1558700673013000014958_sktwi1f5rjvs16k88.png get_app
1558700670627000014958_sktwi1f5rjvs16k87.png get_app
1558700668440000014958_sktwi1f5rjvs16k86.png get_app