Polling request specificities
In NeoLoad, all the polling requests in a recording are represented by a single polling request. In addition to the normal parameters for a standard request, a polling request:
- is a multi-response request
- is a Push message Container
- contains a rule to calculate the response time
Multi-response requests
At the end of a recording using a Push framework, NeoLoad creates a copy of the recorded User Path. This copy is modified so that the polling requests can be handled correctly. See Push frameworks. A single, special request replaces all the polling requests captured in the recording containing all the responses received for each polling request. In a polling request Advanced section, the Recorded response tab shows a list of all the responses received.
This list allows viewing all the responses received. When a response is selected, its content is displayed on the right. The search field allows searching for text contained in the responses. When the search text is entered, the response list is filtered to leave only those responses containing the searched-for text. Furthermore, each occurrence of the text is underlined; the next / previous buttons allow browsing the occurrences.
During playback, the variable extractors and assertions placed on the request are executed for each response received.
Push message Container
When a polling request is used in a User Path, numerous updates are received from the server in the responses to the request. NeoLoad provides an easy way to carry out actions according to the server responses.
For more information about Push message handling, see Push messages.
Response time calculation
The request defines the way the response time to each of the request Push messages is calculated.
For more information about calculating Push message response times, see Push messages response times.
