Jmeter result analysis

Ankita Prabhu's picture
Ankita Prabhu asked on September 29, 2014 - 4:13am | Replies (2).

Helo, I have recently joined as a tester in an IT company and asked to use jmeter

I dont much knowledge abt jmeter

But through youtube n google I learnt d basic of recording scripts and running it n seeing the results throught listeners

My doubt is how to know dat 'here-and -here' is a bug?

Like in manual testing its easy to point out any mistake

But how to do the same in jmeter?

And how v vl come to know at which module/point is d bug?

Reply asap

2 Answers

Ken De Souza's picture

There are a couple of spots you can look at:

  • Stack traces in the logs of your application
  • Timing issues related to how fast responses are
  • Concurrency issues

Typically. you are doing some sort of performance related activity when you are using jmeter. As for what module, I would suggest working with your developers/architects to help you get a better idea of what your goals are.

Citi Mind's picture
Citi Mind replied on October 9, 2014 - 11:32pm.

Jmeter is a load testing tool. In order to point out defects using jmeter request need to be posted to http/s protocols and navigate to a few pages. You may need to paas all RQ parameters in as they are sent in URL headers. When you pull a report on how much time it took to run your flow/scenario v/s expected or SLA you can figure out if that is a bug.




StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.