Response filters remove unwanted text from a response after a step has executed and before Spirent iTest applies analysis rules. The “filtered” response is typically cleaner to read and easier to map and to understand. As a result, the sample responses that you use to create Response maps are simpler, and test reports are more readable.
1. The response contains a lot of irrelevant text, and it would be easier to analyze and display only a portion of the response and to ignore the rest.
2. The device produces XML output, but the output includes non-XML headers and footers that corrupt the XML (or HTML) mapping. Filtering can remove the headers and footers before you apply the queries.
We can set the response filter at different levels:
1. For a step in a test case
In the Test Case editor, select the step. In the Step Properties section, open the Response Filters page.
2. In the Session profile (these filters will apply to all steps which use this session profile)
3. In the Response map Editor
Comparing the filtered and unfiltered version of a response:
The regex and an associated “exclude lines with matching text” action can therefore act as a “filter” to remove all “IP” text from response. The result is the “filtered” response at the bottom
Response of “ipconfig” command before applying “response filter”.
Configuring Response Filter (in order to Filter 'IP' from above response)
Select one of the following methods for applying the pattern while filtering a response.
Apply the above “Response Filter”
Regex that matches any ' IP ' and an action 'Exclude matches of the Pattern found within lines'
Response of “ipconfig” command after applying “response filter”, where the text 'IP' is filtered out from the response.