1. JMeter automatically treats responses with HTTP Status Codes <https://developer.mozilla.org/en-US/docs/Web/HTTP/Status> below 400 as successful. It doesn't do any extra checks so you might want to introduce Assertions <https://www.blazemeter.com/blog/how-use-jmeter-assertions-3-easy-steps> in order to verify that your test is doing what it is supposed to be doing.
2. Make sure to add HTTP Cookie Manager <http://jmeter.apache.org/usermanual/component_reference.html#HTTP_Cookie_Manager> to your Test Plan 3. Record the same scenario one more time and compare the recorded scripts. If you see the differences - these values need to be *correlated* - to wit extracted from the previous response using suitable JMeter Post-Processor <http://jmeter.apache.org/usermanual/component_reference.html#postprocessors> and stored into JMeter Variables <https://jmeter.apache.org/usermanual/functions.html> . Once done you will need to replace hard-coded values which need to be dynamic with the aforementioned variables. -- Sent from: http://www.jmeter-archive.org/JMeter-User-f512775.html --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org For additional commands, e-mail: user-h...@jmeter.apache.org
