Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
You can change this under Settings & Account at any time.
JMeter Test Automation Tool
Transcript of JMeter Test Automation Tool
REST API for a
Why use JMeter?
JMeter is an application designed to
load test functional behavior and
measure performance of a variety
of services, with a focus on web
REST API’s are based on HTTP, URI requests. The URI is sent to the to the web service. Both the data sent, and the data returned are in formats specified by the web service. In the demo the format is JSON.
A must have tool for the toolbox!
It saves time and it's Free!
Low learning curve with simple intuitive GUI.
Find problems quickly with regression testing.
Simplifies the hunting of bugs.
Versatile - It can used to test more than web apps.
Allows coding with confidence.
Pre & Post Processor
Thread group elements are the beginning points of any test plan.
All controllers and samplers must be under a thread group.
Other elements, e.g. Listeners, may be placed directly under the test plan, in which case they will apply to all the thread groups.
As the name implies, the thread group element controls the number of threads JMeter will use to execute your test.
Samplers send requests to a server and wait for a response.
Java object request
WebService (SOAP) Request
JMeter samplers include:
The Test Plan is where all of our JMeter components reside. It allows for declaration of user defined variables and has some other bits of functionality.
Unlike unit tests, integration tests do not test single pieces of functionality. Integration tests test how the components of a project interact with each other. This will allow us to catch bugs as they are created.
Thus, it makes sense to write an integration test for each use case specified.
JIRA is web based software primarily used for bug, issue tracking, and project management.
Logic Controllers lets you control the flow of your test.
Logic Controllers can change the order of requests coming from any of their child elements.
They can modify the requests themselves, cause the JMeter to repeat request, etc.
Config elements can be used to set up
defaults and variables for later use by samplers.
HTTP Request Defaults
By default, a Jmeter thread will send requests without pausing between each sampler.
A timer element will cause JMeter to delay a certain time before each sampler.
They are processed in the order they appear in the tree.
A Pre-Procesor is something that will happen before a sampler executes.
A Post Processor executes after a sampler finishes its execution.
They are useful processing the response which is received from the application
A test isn't a test unless it checks something!
Assertions are what do the checking.
Jmeter will highlight when an assertion fails.
Using an assertion you can verify the results that what your application is returning are the expected results.
Listeners provide access to the information JMeter gathers about the tests which are executing.
The "View Results Tree" Listener shows details of the sampler requests and the responses.
For instance Response codes, messages etc.