1. You don't need to record any calls to images, scripts, styles, fonts, etc. you should configure JMeter to retrieve all embedded resources from the page and use concurrent thread pool of 4-6 threads for fetching them as this is something what real browsers do in the HTTP Request Defaults <http://jmeter.apache.org/usermanual/component_reference.html#HTTP_Request_Defaults> . You should also exclude requests which belong to external domains so your test would focus only application under test and not include any stuff from i.e. Google, Youtube, whatever. See Web Testing with JMeter: How To Properly Handle Embedded Resources in HTML Responses <https://www.blazemeter.com/blog/web-testing-jmeter-how-properly-handle-embedded-resources-html-responses> for more details.
2. You can use Debug Sampler <http://jmeter.apache.org/usermanual/component_reference.html#Debug_Sampler> or Debug PostProcessor <http://jmeter.apache.org/usermanual/component_reference.html#Debug_PostProcessor> . You can also print variables values to /jmeter.log/ file using __logn() function <https://jmeter.apache.org/usermanual/functions.html#__logn> 3. The question is not clear. 4. Well-behaved JMeter test (assumes you handle embedded resources like described in point 1, use HTTP Cache Manager <http://jmeter.apache.org/usermanual/component_reference.html#HTTP_Cache_Manager> to represent browser cache, use Parallel Controller <https://github.com/Blazemeter/jmeter-bzm-plugins/blob/master/parallel/Parallel.md#parallel-controller> to represent JavaScript calls, etc) should produce the same response time as real browser does. -- Sent from: http://www.jmeter-archive.org/JMeter-User-f512775.html --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
