Page History
After Verify is completed, the tree in the Extractor Verification tab will show the 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:
...
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 Extractor name, recorded session number, and replayed iterations number (j) are displayed below.
The value returned by a selected extractor is displayed in the property grid (h).
...
The autocorrelation engine works on built-in patterns that, on 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 thatafterward manually. Keep the new extractor definition only if it fixes script errors that occurred with the old extractor definition.
...
| Note | ||
|---|---|---|
| ||
The surrounding superstring value is provided for informational purposes and should only be used if you are getting get errors in your test script. |
Starting from v5.6, the extractor definition is displayed in the grid to help identify extractor definition errors faster.
Troubleshooting script by comparing extractor's sessions
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 a comparison can expose the root cause of the issue that may be a consequence of an issue in the previous session.
...
If the extractor is unnecessary, it can be deleted by selecting Delete Extractor (b) menu item.
...
Overview
Content Tools