HomeSUPPORT QUESTIONS

Need help with StresStimulus? Start here.

Details of Parametrized requests Messages in this topic - RSS

ruchi
ruchi
Posts: 4


4/20/2018
ruchi
ruchi
Posts: 4
I am parametrizing a request using dataset. My dataset has 2 rows of data and I have parametrized it like this :




How can I see the updated requests after parametrization ? and how can I check whether parametrization is actually happening behind or not?



I am using trial version.

0 link
George @StresStimulus
George @StresStimulus
Administrator
Posts: 117


4/20/2018
George @StresStimulus
George @StresStimulus
Administrator
Posts: 117
In order to review how parameterization works you need to run Verify. I created an example somewhat similar to your test case:

1. Recorded a scenario with the value "Laptop".

2. Created a dataset PayloadsWF with a field Payloads and two records: "Desktop" and "Server". Note, that both values are different from the recorded value.



3. Created a parameter in request 276 (last parameter, all others are created by StresStimulus's autocorrelation) similar to the parameter in your test.


4. Ran verify.


5. On verification tree, double-clicked request 276 to open compare session inspector http://support.stresstimulus.com/display/doc48/Verifying+the+Test+Case

6. Search for "laptop" in the recorded request (on the left) and observed a highlighted value "desktop " in the replayed request (on the right).





Successful parameterization with the 1st data set record is confirmed.


Verify multiple dataset records

During Verify, you can change what VU to emulate. If you use a databinding method sensitive to VUs, then you can verify replaying not only
1st but any record in your dataset. Databinding methods are described here http://support.stresstimulus.com/display/doc49/Databinding


In the next example, instead of Iteration-Bound data-binding method in your test, I applied VU-Bound data-binding, as shown below.



This time I ran verify with VU2



After verify is complete, on verification tree, double-click request 276 to open compare session inspector.


Search for "laptop" in the recorded request (on the left) and observe a highlighted value "Server" in the replayed request (on the right)



Successful parameterization with the 2-nd dataset record is confirmed.

-Cheers
0 link
ruchi
ruchi
Posts: 4


4/23/2018
ruchi
ruchi
Posts: 4
Thanks for the reply. I appreciate that.

Your dataset had 2 rows but when you 'Verified' it and compared the sessions, you got only one value parametrized from the dataset (Desktop) . Now my question is how can i see both the values of the dataset in that request using 1 VU only.
In short , I want one VU to reach that request #276 and iterate over all the datarows one by one. How can i see those parametrized requests ?
0 link
George @StresStimulus
George @StresStimulus
Administrator
Posts: 117


4/23/2018
George @StresStimulus
George @StresStimulus
Administrator
Posts: 117
The purpose of Verify is to check that your script works correctly. So it only executes one iteration at a time, and every iteration will consume only one value from the dataset. Because you use Iteration-Request databinding method, Verify will always consume 1st record from the data set. To see the 2nd (or any other) dataset record being used, instead of Verify you need to actually run a test as follows:


1. Select steady load with 1 VU x 2 iterations.
http://support.stresstimulus.com/display/doc48/Load-Pattern and http://support.stresstimulus.com/display/doc48/Number+of+Iterations





2. After test completes open the Query log and in the sessions textbox enter 276 (in your test it will be 54) and click Show Sessions http://support.stresstimulus.com/display/doc48/Querying+the+Test+Log




3. In the Sessions Grid you should see 2 replayed #276 sessions. One for first iteration and one for second.




4. Right click on the second one and select Compare with matching recorded session




5. A similar compare session inspector will appear and you can see the second value.



As you can see, StresStimulus provide full visibility to every request and response executed during a performance test, regardless how large it is. It also provides a quick way to compare replayed session with the recorded one.


-Cheers
0 link






Copyright © 2018 Stimulus Technology