October 2014
Intermediate to advanced
228 pages
5h 5m
English
In practice, web browsers have a caching mechanism to reduce the amount of data transferred over the network. This in turn gives end users a better experience. If data has not changed since the first time it was fetched from the remote server, there is no point fetching it again and thus, it can be fetched from a locally cached copy of the browser.
This same behavior can also be achieved with JMeter using the HTTP Cache Manager component. With the HTTP Cache Manager configured, JMeter is able to cache responses from sampled requests and serve them back on subsequent requests if they have not changed on the remote server.
In this recipe, we will add an HTTP Cache Manager component to a test plan ...
Read now
Unlock full access