Another way to find missing parameters is to re-record the same scenario and compare the two recordings to identify dynamic values. It consists of the following steps:
1. After running verify, in the Verification tree, right-click on the error/warning session in the original test case and select Compare Recorded option.
2. In the Select a Session to Compare window, click Record New... (a) to re-record the identical test scenario for comparison. The recording wizard will appear to take you through the steps of re-recording. That will create a test case that can be deleted after the correlation process is complete. Therefore you don't need to annotate transactions. The recording wizard will automatically give a suggested test case name
<Current Test Case> - Compare. The default mix weight for this test case will be set to 0, so it will not be executed during the test run. Once the recording is complete, the verify tree should still be open, go back to Step 1 of the process above, and then proceed to Step 3.
3. If the test case was already recorded twice, then StresStimulus will automatically find a matching test case and matching session. The matching test case will be selected in the Test Case drop-down as
<Current Test Case> - Compare (b). The corresponding session (c) will also be selected. While test cases recorded twice are similar, they are not identical. Therefore the session number will not necessarily match, but the session content will. If the session is not selected, select it manually using the information provided in the grid columns. The columns are as follows:
- Url column is the URL of the request.
- Request column is the size of the request in bytes.
- Response column is the size of the response in bytes.
- % column is the percent match to the original session. The closest to 100%, the more likely this is the corresponding session. This column is sortable.
Once the corresponding session is selected, click OK (d).
4. The Compare Session inspector will open in a separate tab. The original session will be on the left; the secondary session will be on the right. Compare the two recorded requests, and pay attention to the differences. Usually, these differences point out the dynamic parameters that need to be created. To quickly traverse through the differences, repeatedly click Highlight the Next Difference (e) on the toolbar. In the example shown in the screenshot above, the first value of the parameter openFormIds was recorded as 40F (f). The second time the same value was recorded as A59 (g). This is an indication that this parameter is dynamic. There are three possibilities:
- the dynamic value should be correlated
- the dynamic value is already auto-correlated
- the dynamic value should be parameterized unless you've already parameterized it.
5. Select the green text on the left and click the Find the highlighted text in the previous responses button (h). Alternatively, right-click and select the same item on the context menu. The responses that contain the selected value should be highlighted in the test case tree. If no responses are highlighted, then the dynamic value was originated on the client and should be parameterized. Otherwise, create the appropriate extractor for the highlighted value (i) (if one doesn't already exist). Right-click and select Create Response Extractor (j).
6. Create an Extractor dialog that will appear with the dynamic value highlighted (k). Continue creating the extractor, as described in the Extractors section.
7. To create the parameter, go back to the Compare Session inspector, select the dynamic value (f) and click the Parameterize the selected value button (l) on the toolbar. A Create Parameter dialog with the pre-selected value (m) will open. Right-click, and from the Variable Picker, select the extractor (n) created in step 6.
- No labels