Welcome to the testing world in this session, I'll explain the end stupidity.
So first of all, we have to understand where we are going to use variety and severity in last session
we have seen when we are reporting a new book.
So let me go to just here on Gita.
And when we are creating a new defect that we found a dropdown with the name Variety.
So it was here.
And if you take it here, you have many options here.
Highest, high, medium, low, lowest in the same way.
If configured, you can also get one more drop down with the name severity.
Whenever we are reporting a defect, we can enter priority or severity or both.
It depends what all the fields we are getting, but how to enter, like which priority we need to select,
how to decide that so that we are going to cover in this session.
So first of all, we need to understand priority and severity, and then I'll show you how we can decide
priority and severity.
So first of all, priority in priority recheck how big the bulk is, how quick this bug need to be fixed
so you can easily understand.
It is very common that if we have a bug, which is more important, so that need to be fixed first.
So definition is saying the same thing here.
They decide in priority.
We check how big the bug is and how quick this bug need to be fixed.
So here in the priority, we find out the importance of the bug, but how to find out or decide the
priority.
We check what is the impact of this bug on the plane or the client business.
So if I take an example, I have a bug and it is very important from the client point of view for the
client business point of view, it will be a big bug when I say it will be a high priority bug.
So in practice, we are going to check how big the bug is and how quick this bug needs to be fixed and
to decide the priority.
We are checking what is the impact of this bug on the client or the client business.
Okay, let me take you on the Facebook application.
OK, here.
If I say I have entered username, correct username and password, I try to log in, but I'm not able
to log into the application with correct credentials.
So it's a bug.
But what should be the priority of this?
It should be the highest priority.
But why?
Because if a customer is not able to log in so he or she will not be able to perform any duty on the
application means my customer or my business is impacted by this more than means if the high or highest
priority.
But if you notice here, it's the highest priority just because it is just blocking my customer to use
this application.
So in priority, we check what is the impact of this book on the client or the client business?
OK, let me take one more example here we have a Facebook page.
Let's take an example here.
The spelling of the Facebook is incorrect.
I'm just taking example.
So it's a book.
But what should be the priority?
From my point of view, it should be the highest, or I say, high priority.
Why?
Because all the customers.
It could be a normal customer.
Or it could be any person who is going to give advertisement to the Facebook is coming to the login
page first.
And here, if I check, OK, the spelling is incorrect means if Facebook is not able to handle their
own data or they are not able to correct their own data.
So it's not sure, but they will be able to display my advertisement correctly or not.
So ultimately, Facebook is going to lose the customer or lose the business.
So here in practice, we check what is the impact of the book on the client or the client business,
and more impact means more priority.
Then we talk about severity in severity.
We check what is the impact of the book on the application.
More and more severity.
So let's take the same example.
I'm putting username.
I'm putting password.
I click on the sign in button.
I'm not able to log in.
It's about what should be the priority.
It highest priority book way because it is impacting my business.
But in severity, we check what is the impact of the on the application.
So if we take the same scenario here, if we are not able to log in, so means we are not able to use
application.
No.
So it's it's a blocker for the complete application.
It's also a high severity book.
But if we take an example, second example I was taking like Facebook or spelling is incorrect.
We are taking example.
So it's a high priority book.
But if you talk about the severity, severity is low whilo because this is not impacting my application
functionality.
So there is almost very minimal impact when I see almost no impact because I think his a mistake.
Still, your user is able to use the application, still am able to like still, I'm able to share so
everything is working.
It is very less impact on the application.
Again, in part, we are checking what the impact of the bug on the client and the client business.
So we are talking about a Real-Time User's usage of the application, but in severity, we check impact
of the bug on application.
So that is priority and severity.
That is one of the most common question which you are going to face when you're going for software testing
interviews.
So here you have to find out some examples of high priority, high severity, high priority, low severity,
low priority and high severity, low priority and low severity.
So you can take any application like Facebook dot com, Yahoo dot com, and you can find out these examples.
That's all we have.
Thanks for watching this video.