Unless your pages return HTTP errors (status 4xx or 5xx) - Jmeter will not automatically flag the requests as errors. You must add assertions. If your test doesnt have assertions , you have no way of knowing whether the test script actually worked or not. . >But there is another point , if we take 100 users/sec in jmeter so can we assume , a particular button would be getting hit more than 10 times per >second? Depends on your test but in general yes , JMeter will make requests concurrently . The actual number will vary with how your application responds to load , timers etc.
On Mon, Oct 18, 2010 at 8:23 PM, samurai241185 <[email protected]> wrote: > > Hi Deepak, > > > Thanks for the reply. > Environment was same while my team conducted this test.But what we exactly > did- > lets say there are 4 webpages and all contains some navigation button to > move to the next page. > We at the same time clicked at first button at the same time.And as > response > time would be different for different users so after moving to second page > , > we waited till all 10 team members reach to the second page.Now we clicked > at the button at the second page button at the same time and page gets > broken. > > Now what is my feel -this seems a kinda stress or load testing for a > particular button rather say it concurrency testing . > But there is another point , if we take 100 users/sec in jmeter so can we > assume , a particular button would be getting hit more than 10 times per > second? > Please make me correct if i am wrong . > > Thanks > samurai > -- > View this message in context: > http://jmeter.512774.n5.nabble.com/Concurreny-test-via-jmeter-is-it-possible-or-not-tp3215261p3218463.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] > >
