JMeter Report Analysis

1. Before you go on to do performance testing you need to define benchmarks&

objectives of your performance testing. There could be variety of goals for any
performance testing activity.

For example, we can perform a performance test to identify the breakpoint of

application or the maximum number of users application can handle with
reasonable response time.

In an alternative case, we can have a requirement to just analyze the server

resource utilization under different user loads.

Some time performance tests are also used to analyze the changes in
application performance after some code changes or hardware changes. In
such cases we should have base line results (i.e results before & after
changes so a comparison can be done)

So in short it all depends upon requirements. If you are new to performance

testing and have a real time project to do then first of all you need to clarify
the requirements, goals and objectives of performance test.

2. To analyze the report you must first get a tad familiar with performance
related terms like throughput etc. I would suggest you to add the Summary
Report listener to get a better view of your application's performance. The
error % column in the Summary report needs to be zero throughout to ensure
that your application is performing at-least.

There is no such standards and depends what are your expectations from the
application. Try to analyze what amount of traffic you want to handle and then
prepare your script accordingly.

3.
Creating the Test Plan (Scripts):

A test plan is a series of steps that JMeter executes during running time and will

consist of one or more elements like:

1. Thread Groups
The Thread Group will be used to define the number of users that will be
simulated and the number of times the test plan will be repeated: loop x
times with – or loop forever – using x VUs (Virtual Users).
2. Logic Controllers
3. Sample Generating Controllers
4. Listeners
5. Timers
6. Assertions
7. Configuration Elements
8. User defined Variables or User Parameters

9. Regular Expression Extractor