After Verify is completed, the tree in the Extractor Verification tab will show extractors' values. There is a status image showing whether an exception in handling the extractor was encountered next to every extractor. One of 4 statuses can be assigned to an extractor:
a. The extractor is OK.
b. The extractor is not found in the response.
c. The recorded and replayed token extractors are the same.
d. The recorded and replayed extractors are the same.
The status (e) is displayed when mouse-over the extractor.
The autocorrelation process creates extractors and parameters to avoid test execution errors. However, some of these parameters may be unnecessary. If the test machine is overloaded, you can reduce performance overhead by deleting unnecessary parameters. The extractors with statuses b, c, and d are automatically selected for easy removal. To remove them, click Delete (f) on the toolbar.
To search the Extractor Verification tree, use search control (g).
The value returned by a selected extractor is displayed in the property grid (h).
If the value is a long string, notice the replayed and recorded value length (i). If the lengths are really different, then the extracted value may not be accurate.
If recorded and replayed token extractors are the same, it may indicate an incomplete token correlation.
The autocorrelation engine works on built-in patterns that, in some rare occasions, may malfunction by creating an extractor that is shorter than necessary. In such situations, you will receive script errors.
StresStimulus can help to find such an incorrect extractor. If StresStimulus deems an extractor may be too short, it shows the surrounding superstring value that is possibly the value that needs to be extracted.
Use the Surrounding superstring suggestive value to manually update your extractor definition and verify your script after that. Keep the new extractor definition only if it fixes script errors that occurred with the old extractor definition.
The surrounding superstring value is provided for informational purposes and should only be used if you are getting errors in your test script.
Comparing recorded sessions where an extractor was created with the same session on playback can be helpful for script troubleshooting. For example, if the extractor was not found on playback, then such comparison can expose the root cause of the issue that may be a consequence of an issue in the previous session.
To use this troubleshooting methodology, right-click on the extractor node and select Compare Extractor's Sessions. After that, a new tab will display Compare Sessions Inspector for the extractor's session.