It's not really that clear, 'not passed' could mean all sorts of things - try thinking in terms of request/response rather than talking about the GUI - remember, JMeter is not a browser. But I'm guessing that what you are experiencing is that the suggested search is being overloaded. Either that or not all the entries in your csv file are valid. It really depends on how you extract the auto-complete response to use in the main search request.
But in any case, before doing anything else you need to decide what level of load you should be testing at - how many people /users will be making search requests every second and how fast should the requests respond? If you don't know what your success criteria are then you will quickly find load testing to be a confusing and unrewarding experience. Golden rule numero uno is: set objectives. Break it at your peril. I'm sure there are plenty of people out there who think that it is a good idea to not set objectives and simply change the test to make it pass, they probably think that their nice reports with all green show what a good job they are doing. But they are, in fact, deluded. ----- http://www.http503.com/ -- View this message in context: http://jmeter.512774.n5.nabble.com/Timer-how-to-delay-the-HTTP-request-in-the-thread-tp5488599p5489340.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]
