This topic of the lesson looks as it sounds. This is testing that QA engineers are performing to understand and measure the response of the system after putting it on load.
This is how QA engineers are creating a specific script that runs with an app and measures and catches response of the site, app etc.
These apps that are used for creating specific scripts are not so various. Majority of QA engineers are using:
- Blazemeter;
- Jmeter;
- LoadNinja;
- WebLoad;
- Loadstorm.
All of these apps are working similarly, and many scripts from other apps can be used in another one.
We will check the simple example of the load API request from the Home page of the site. We will need to use the developer bar of the browser, open the ‘Network’ tab and find the main request after opening the site.
The two main parameters from the request are URL and Request Method are usually displayed at the top of the log. We will use them as main parameters for our user to check the home page of the site.
For our improvised Load test I will use the Apache Jmeter app cause I'm familiar with it and use it as soon I need to do a Load & Performance testing.
First step I need to create a Thread Group. It is the main controller of your Load testing. It is used for setting the number of the users that will use the specified link, it’s ramp up period and loop count for one user. This is the basic configuration of the Load testing.
Then, for the successful testing I need to create a one HTTP Request action. I will show you basic fields that needed to be filled by the QA engineer that created Load testing.
So, if you remember we saved the two main parameters from the home page request, URL and Request Method. We need these parameters to input into the HTTP request. And when all fields are filled the QA engineer can start Load testing by clicking the ‘Start’ button.
All these actions are used to create a basic Load & Performance testing that can be used for example and to learn more about this topic if you are interested.