Performance Testing and It's Types With Practical Examples | Software Testing

Learn about performance testing, its definition, key concepts, and types like load and stress testing with practical examples.

Key Takeaways

Performance testing is crucial to ensure software can handle expected user loads efficiently.
Understanding stability and response time is fundamental to grasping performance testing.
Load testing verifies software performance under expected user conditions.
Stress testing pushes software beyond its limits to identify failure points.
Practical examples help clarify abstract testing concepts.

What the video covers

Performance testing evaluates the stability and response time of an application by applying load.
Stability is defined as the ability of software to handle the designed number of users simultaneously.
Response time measures how long it takes for a server to process a request and return a response.
Load refers to the number of users accessing the application at a given time.
Load testing involves testing with a load equal to or less than the designed number of users.
Stress testing involves applying load greater than the designed number of users to find breaking points.
The video explains these concepts with practical examples, such as payment processing and user load scenarios.
It emphasizes understanding performance testing basics before diving into its types.
The presenter guarantees viewers will understand performance testing clearly within the first few minutes.
The video also discusses how to identify software crash points under extreme load conditions.

Chapters

What is performance testing?

Performance testing is the process of testing the stability and response time of an application by applying a specific load of users.

What is the difference between load testing and stress testing?

Load testing checks software performance under expected or lower user loads, while stress testing applies loads beyond the design limits to find where the software crashes.

Why is response time important in performance testing?

Response time measures how quickly the server processes requests and returns responses, which impacts user experience and application efficiency.

Full Transcript — Download SRT & Markdown

Speaker A

Hi guys, I welcome you all to my YouTube channel SoftwaretestingbyMKT. In this video, I'm going to talk about what you mean by performance testing and what are the various types of performance testing. Before I proceed with this video, I request you guys to watch this video till the end because this is going to be a very, very knowledgeable video. Many people requested on my channel to talk about performance testing, so this is for you. Watch it till the end. I am giving a guarantee that you won't regret it. So let's get started to talk about what you mean by performance testing.

Speaker A

to be very very knowledgeable video and many people requested on my channel to talk about performance testing so this is for you watch it till end, I am giving a guarantee that you won't regret it. So let's get started to talk about

Speaker A

Performance testing is nothing but testing the stability and response time of an application by applying load. This is called performance testing. If I say it like that, you guys will not understand. I'm going to divide this definition into three parts and make you guys understand step by step.

Speaker A

step by step by step. Guys one more thing if you guys just understand what do you mean by performance testing then understanding that types of performance testing will be just like a tuk(easy). so make sure that you listen to me

Speaker A

Guys, one more thing. If you guys just understand what you mean by performance testing, then understanding the types of performance testing will be just like a tuk (easy). So make sure that you listen to me completely. In the next five minutes, I am giving you a guarantee that you will understand. Just be with me. Let's get started to talk about what you mean by performance testing.

Speaker A

stability and response time. Performance testing is nothing but testing the stability and response time of an application by applying load is called as performance testing. Now what do you mean by stability? Guys when you develop any software when developers will develop any software, customers or

Speaker A

So, performance testing is nothing but testing the stability and response time. Performance testing is nothing but testing the stability and response time of an application by applying load. This is called performance testing. Now, what do you mean by stability? Guys, when you develop any software, when developers develop any software, customers or business analysts or product managers will tell you whatever we are developing should be able to handle how many users at a time.

Speaker A

Stability is nothing but ability to withstand design number of users is called as stability now what do you mean by response the response time is nothing but whenever you deal with any application let's talk about your whenever you are trying to do a payment so when you are on the payment page and

Speaker A

So, talking about stability, stability is nothing but the ability to withstand the designed number of users. That is called stability. Stability is nothing but the ability to withstand the designed number of users. That is called stability. Now, what do you mean by response? The response time is nothing but whenever you deal with any application, let's talk about your payment.

Speaker A

finally it will send the request from the server which will change the page from payments page to the OTP page. Now it will tell you to enter the OTP how it happened how much time it is taking that is called the Response Time.

Speaker A

So, when you are on the payment page and you are doing the payments, you have entered all your credit card details or debit card details and you're clicking on the send button. What actually happens? The request will go to the server, it will run a program in the server, and finally, it will send the request from the server which will change the page from the payments page to the OTP page.

Speaker A

but number of users using the application at a particular period of time that is called as load. Usually load is nothing but number of users using the application now let me tell you guys the definition of performance testing once

Speaker A

Now, it will tell you to enter the OTP. How it happened, how much time it is taking, that is called the response time. The response time is nothing but the time taken to send the request to the server, run that program in the server, and then finally take back the request from the server. It is called response time.

Speaker A

the stability you are testing that you have designed your application for 50 users so you are testing the stability ability to withstand the design number of users. You have developed for 50 users, to use your application any moment of time so you are testing the stability now you are testing

Speaker A

Now, what do you mean by load? Load is nothing but the number of users using the application at a particular period of time. That is called load. Usually, load is nothing but the number of users using the application.

Speaker A

able to handle it or not and also you are testing the response time by applying load it is called as performance testing I hope it is clear to you guys now let's talk about what are the various types of performance

Speaker A

Now, let me tell you guys the definition of performance testing once again. This time you guys will be able to understand it. So, I told you performance testing is nothing but testing the stability and response time of an application by applying load. This is called performance testing.

Speaker A

of our users examples my application that we have developed we have developed it for 50 users at a time now we have developed it for 50 users but when I am doing your testing I am testing it with only 45 users or maximum I'm testing it

Speaker A

You are testing the stability. You are testing that you have designed your application for 50 users, so you are testing the stability, the ability to withstand the designed number of users. You have developed for 50 users to use your application at any moment of time, so you are testing the stability.

Speaker A

about what do you mean by stress testing. Now stress testing, in stress testing you are testing the stability and response time by applying a load more than the design number of users it is called as stress testing suppose you have

Speaker A

Now, you are testing whether it is able to handle the request for 50 users at a particular period of time or not. Performance testing is nothing but testing the stability. That is, you are testing if you have developed the software for 50 users whether it is able to handle it or not. Also, you are testing the response time by applying load. It is called performance testing.

Speaker A

stability that is ability to withstand at least the design number of users and the response time that is three seconds how by applying load which is more than the design number of users so definition says that, definitely I'm not going to

Speaker A

I hope it is clear to you guys. Now, let's talk about what are the various types of performance testing.

Speaker A

is more than the design number of users I have designed the revision 4,000 users but since it is a stress testing I am going to test it with more number of users at any moment of time and also I will check the response

Speaker A

Talking about the types of performance testing, the first type of performance testing is called load testing. So, in load testing, you are testing the stability and response time of an application by applying load which is equal to the designed number of users and also which is less than the designed number of users.

Speaker A

application by applying load which is more than the design number of users and here we try to find out where exactly my software is crashing that means you are applying load more than the design number of users and you are exactly

Speaker A

Examples: My application that we have developed, we have developed it for 50 users at a time. Now, we have developed it for 50 users, but when I am doing your testing, I am testing it with only 45 users or maximum I'm testing it with 50 users because load testing says that testing the stability and response time by applying load which is less than the designed number of users or equal to the designed number of users. That is called load testing.

Speaker A

my application by applying load more than the design number of users and I will try to break my software by applying more load I am just checking since my software can handle thousand users at any moment of time but what

Speaker A

Now, let's talk about what you mean by stress testing. Now, stress testing: In stress testing, you are testing the stability and response time by applying a load more than the designed number of users. It is called stress testing.

Speaker A

software will crash so in scalability testing you are testing the stability and response time by applying load more than the design number of users and here exactly.you trying to find out where my software is crashing that point it is

Speaker A

Suppose you have developed an application and the requirement is telling that my application should be able to handle a thousand requests or a thousand users at any moment of time and it should give the response time within three seconds. This is my requirement.

Speaker A

just giving you an example to make you guys understand by giving you a small example so my software will give me I am testing my software with thousand five hundred users and it is giving me responds in 2 second I am testing my software with two

Speaker A

But in stress testing, I am testing the stability, that is, the ability to withstand at least the designed number of users and the response time that is three seconds, how? By applying load which is more than the designed number of users.

Speaker A

point we are trying to find out in our scalability testing that is where exactly your software is breaking you are trying to find out is in your scalability testing so we will say that when we applied 5150 users load in the software

Speaker A

So, the definition says that definitely I'm not going to apply the load as per the requirement, but I will apply the load more than the designed number of users. So, since it is stress testing, I am here testing the stability and response time of an application by applying load which is more than the designed number of users.

Speaker A

so the fourth type of performance testing we have is called as volume testing the other name of volume testing is also called as flood testing now why it is called as volume testing and why it is called as flood testing let's get

Speaker A

I have designed the revision for 4,000 users, but since it is stress testing, I am going to test it with more number of users at any moment of time and also I will check the response time.

Speaker A

have created a website called a SoftwaretestingbyMKT my database says that you can use up to 1gb of data on your website suppose i have uploaded 50 youtube videos on my softwaretestingbyMKT.com video it is able database is able to handle the request because it has the capacity to serve 1 GB of data

Speaker A

Now, let's go ahead to talk about the third type of performance testing which is called scalability testing. So, in scalability testing, it is a type of performance testing where we test the stability and response time of an application by applying load which is more than the designed number of users.

Speaker A

by transferring the huge volume of data in volume testing or flood testing you are testing the capacity of your database or your DB. Let's go ahead to talk about the next and last type of performance testing which is called as

Speaker A

Here, we try to find out where exactly my software is crashing. That means you are applying load more than the designed number of users and you are exactly trying to find out where my software is going to crash.

Speaker A

testing but there are many chances that people will ask you what do you mean by soak testing or endurance testing this is one of the most important type of performance testing. Let's get understand so testing the stability and response

Speaker A

Examples: You have your software for 1,000 users at any moment of time which should give the response time within 2 seconds, but since it is scalability testing, I am going to test my application by applying load more than the designed number of users and I will try to break my software by applying more load.

Speaker A

watching TV and somehow you got sleep and your TV is on whole night not nowadays now nowadays we have a facility that it gets turn off automatically but in olden days chances are there that when you were watching you got sleep and

Speaker A

I am just checking since my software can handle a thousand users at any moment of time, but what happens if you apply one lakh of load at any moment of time? Your software will crash definitely since your application can handle only a thousand users at any moment of time.

Speaker A

want the software to be in such a way that customer do not complain later so what exactly do they do soak testing or endurance testing so what they test in this they test the stability and they also test the response time they

Speaker A

If we apply one lakh, what will happen? Your software will crash. So, in scalability testing, you are testing the stability and response time by applying load more than the designed number of users and here exactly you are trying to find out where my software is crashing. That point is called scalability testing.

Speaker A

the type of the application if I am giving some example where and all this kind of testing take place so it takes place in mobile in mobile when any company is developing any mobile let's say Samsung or Apple they do this

Speaker A

So, we have developed a software for a thousand users which should give a response time within 2 seconds, but when I am testing with 1,500 users, it is working perfectly fine. Let's say I'm just giving you an example to make you guys understand by giving you a small example.

Speaker A

nothing happens to the bike or your car because company has done proper soak testing. Guys I hope this video was useful to you guys if you think that I have missed anything list out all your doubts in the comment section I will be

Speaker A

So, my software will give me—I am testing my software with 1,500 users and it is giving me a response in 2 seconds. I am testing my software with 2,000 users, it is giving the response within 6 seconds. When I started testing my sof—

Speaker A

all your doubts in the comment section I will be answering. In next video what shall I make next? put out in the comment section you can also reach to me out by my gmail account, quora account and Twitter account link is there in the

Speaker A

description please check out soon thank you

Topics:performance testingload testingstress testingsoftware testingresponse timestability testingapplication loadsoftware performancetesting typesSoftwaretestingbyMKT

Get More with the SozAI App

Transcribe recordings, audio files, and YouTube videos — with AI summaries and speaker detection. 30 minutes free.

App Store Google Play

Or transcribe another YouTube video here →

Free tools: TXT to SRT · SRT Validator · Merge SRT · Subtitle to Text · All tools