LOAD TEST fetches URLs based on the recorded scripts. However, many web applications have dynamic contents, which changes based on time, place, and other factors. In addition, contents may change from release to release. Therefore, to do realistic testing and to avoid reordering the script with every release, Auto Fetching embedded objects is required. So, the concept of auto-fetch is used to fetch embedded URLs from the real site.
Inline Resource Options
Do not fetch inline resources
When enabled, no dynamic inline URLs are captured in the network. It captures only the main URL.
Fetch recorder inline resources
When enabled, only recorded inline URLs are captured in the network.
Fetch inline resource based on main URL response
When enabled, all dynamic inline resources based on the main URL's response are captured.
URL Pattern
The user needs to define the URL pattern that he wants to include or exclude. Using a combination of includes and excludes, the user, should be able to execute the script with what he is interested in and skip what he is not.
Example : If a user doesn't want to execute the test with a specific inline url of any domain then he/she can exclude that url / domain from the script at the time of execution. Like if the user wants to exclude an image then the user can put *.jpg in the URL pattern and select exclude from the drop-down.
Include Url
Select this if you want to include the specified URL Filter.
Exclude Url
Select this if you want to exclude the specified URL Filter.
Minimum Connection Reuse delay of random value from a specified range
In most applications, user can make a limit on the connections pool for parallel URL fetching of inline resources. Specify the range to apply delay while reusing the connection. It is used to simulate some blocking time.
Runtime Changeable No