1. You don't need to record them but you MAY need to run them. Ignore anyone that tells you that they are not required - whether or not you should include them is dependent on your circumstances and if you make the wrong choice you will be running an invalid test.
2. So, yes, this option enables you to simulate these calls without having to record them and have explicit references to them in your test. JM2.5 has the added bonus of concurrent requests. 3. Read the manual for this config element. It's pretty straight forward and does what it says on the tin - simulates caching. It's not fantastic, pretty basic in fact, but that makes it simple to understand. Remember, before you can decide what to do here you need to understand what your objectives are and the setup of your test rig - specifically, from where you will be injecting load and through which architectural components your requests will pass. ----- http://www.http503.com/ -- View this message in context: http://jmeter.512774.n5.nabble.com/JMeter-script-recording-tp4785669p4785888.html Sent from the JMeter - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
