Proxy Server while recording creates http requests for elments gif, css, js, ico,png
I am new to performance testing with Jmeter
I have to load testing with web applications
I created script using Jmeter's Http proxy server
Http proxy recorder, creates one http request for each main page and also separate http request for each of the embedded resources like
for *.css, *.js, *.gif, *.ico, *.png
Conidering best practice of performance testing with(or without) Jmeter, do we need to use http request for *.css, *.js, *.gif, *.ico, *.png
or we can ignore such request and only consider the main page request such as ending *.html or *.jsp
while recording you can exclude the images which you mentioned in the list, but if you consider as main request most of the application having different page extension ,so it will not help to record. my suggestion is ensure to exclude image types but for request no need to mention any file types.
It depends if the files exercises something in the System Under Test. In our system, since we deal with digital asset management, static assets such as CSS, JS, and image files for our branding look and feel we exclude from our unittest since they are served up by a separate CDN and do not call any back end functionality. However, say viewing images the customer has uploaded, we do include because it's stressing the database when the view count and reporting related metrics are incremented.
It's best to exclude as much as you can, so you can save your machine resources and put them towards generating higher load. I think a good question to ask yourself is, "Does the request run any code in your server side application?" If not, it's probably safe to exclude because you'll only be stressing the Web Front End, which is normally served by CDNs in production.
If you need to simulate a realistic browser behavior you need to ʺtellʺ JMeter to behave like a real browser. It assumes downloading embedded resources, using Cookie Manager to send/receive cookies, include user-agent string, use Cache Manager to store those embedded resources to they won't be downloaded in nested requests. I would suggest to delete all ʺgarbageʺ recorded via proxy as it may be a subject to change when you revisit page apart from (HTTP GET/POST/PUT/)whatever requests and add controllers listed above with appropriate configuration to simulate reallife conditionsp