What is Performance Testing ? Performance testing is a type of testing to ensure software applications will perform well under their expected workload.
Performance testing is done to provide stakeholders with information about their application regarding speed, stability and scalability. More importantly, performance testing uncovers what needs to be improved before the product goes to market.
Type of Performance Testing
Load testing — Test the application’s ability to perform under anticipated user loads.
Stress testing — involves testing an application under extreme workloads to see how it handles high traffic or data processing. The objective is to identify breaking point of an application.
Endurance testing — is done to make sure the software can handle the expected load over a long period of time.
Spike testing — tests the software’s reaction to sudden large spikes in the load generated by users.
Volume testing — Under Volume Testing large no. of. Data is populated in database and the overall software system’s behavior is monitored. The objective is to check software application’s performance under varying database volumes.
Scalability testing — The objective of scalability testing is to determine the software application’s effectiveness in “scaling up” to support an increase in user load. It helps plan capacity addition to your software system.
What is JMeter ?
The Apache JMeter is pure Java open source software, which was first developed by Stefano Mazzocchi of the Apache Software Foundation, designed to load test functional behavior and measure performance.
Measure the performance of web application or variety of services.
Measure the performance of APIs service.
JMeter originally is used for testing Web Application.
For Full Tutorial, Watch my tutorial on Youtube.
Thanks for reading! 🙂 If you enjoyed it, hit that subscribe button below. Would mean a lot to me and it helps other people see the story.
Its a sequence of the request – If this happens then this happens else this happen is workflow.
How To Use –
Specify the name of the subsequent request.
To terminates execution.
Some Points –
setNextRequest() is always executed at the end of the current script.
This means that if you put setNextRequest() before other code blocks, these blocks will still be executed.
setNextRequest() has a scope, which is the source of your collection run. This means that if you run a collection, you can jump to any request in the collection (even requests inside folders, using the same syntax). However, if you run a folder, the scope of setNextRequest() is limited to that folder. This means that you can jump to any request within this folder, but not ones that are outside of the folder.