You need to work out what requests are being sent (if any) as part of this process. Your progress bar is (probably) being run from javascript and JMeter does not run at this level, it works at the HTTP level, so you only need to focus on these calls.
Usually with a progress bar on a webpage there will be some code that is polling a particular request waiting for a certain response - in this case you should see these calls being made, simulate them and then you can build some logic in your test to handle the polling - just make sure you keep any interval values set to realistic levels. If there are no server calls being made then it might be that this progress bar is waiting for something that is running on the client, in which case you probably don't need to concern yourself with this for a traditional load test - this is more of a functional thing. The only issue might be if there is a value that is returned from this process that you need, in which case you have to get a bit clever and simulate the response - you can normally fake these things pretty easily. Have a play around using one of the dev toolsets in a browser (Chrome dev tools/Firefox Firebug etc.) ----- http://www.http503.com/ -- View this message in context: http://jmeter.512774.n5.nabble.com/progress-bars-on-page-tp5281323p5281351.html Sent from the JMeter - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
