1
00:00:00,000 --> 00:00:06,000
Welcome to the testing world in this session, I'll explain the end stupidity.

2
00:00:08,000 --> 00:00:14,000
So first of all, we have to understand where we are going to use variety and severity in last session

3
00:00:14,000 --> 00:00:17,000
we have seen when we are reporting a new book.

4
00:00:18,000 --> 00:00:22,000
So let me go to just here on Gita.

5
00:00:22,000 --> 00:00:29,000
And when we are creating a new defect that we found a dropdown with the name Variety.

6
00:00:30,000 --> 00:00:31,000
So it was here.

7
00:00:32,000 --> 00:00:35,000
And if you take it here, you have many options here.

8
00:00:35,000 --> 00:00:40,000
Highest, high, medium, low, lowest in the same way.

9
00:00:41,000 --> 00:00:45,000
If configured, you can also get one more drop down with the name severity.

10
00:00:46,000 --> 00:00:53,000
Whenever we are reporting a defect, we can enter priority or severity or both.

11
00:00:53,000 --> 00:00:59,000
It depends what all the fields we are getting, but how to enter, like which priority we need to select,

12
00:00:59,000 --> 00:01:02,000
how to decide that so that we are going to cover in this session.

13
00:01:02,000 --> 00:01:08,000
So first of all, we need to understand priority and severity, and then I'll show you how we can decide

14
00:01:08,000 --> 00:01:09,000
priority and severity.

15
00:01:10,000 --> 00:01:19,000
So first of all, priority in priority recheck how big the bulk is, how quick this bug need to be fixed

16
00:01:19,000 --> 00:01:21,000
so you can easily understand.

17
00:01:22,000 --> 00:01:29,000
It is very common that if we have a bug, which is more important, so that need to be fixed first.

18
00:01:30,000 --> 00:01:33,000
So definition is saying the same thing here.

19
00:01:34,000 --> 00:01:35,000
They decide in priority.

20
00:01:35,000 --> 00:01:39,000
We check how big the bug is and how quick this bug need to be fixed.

21
00:01:40,000 --> 00:01:47,000
So here in the priority, we find out the importance of the bug, but how to find out or decide the

22
00:01:47,000 --> 00:01:47,000
priority.

23
00:01:47,000 --> 00:01:52,000
We check what is the impact of this bug on the plane or the client business.

24
00:01:52,000 --> 00:01:58,000
So if I take an example, I have a bug and it is very important from the client point of view for the

25
00:01:58,000 --> 00:02:03,000
client business point of view, it will be a big bug when I say it will be a high priority bug.

26
00:02:04,000 --> 00:02:09,000
So in practice, we are going to check how big the bug is and how quick this bug needs to be fixed and

27
00:02:09,000 --> 00:02:10,000
to decide the priority.

28
00:02:11,000 --> 00:02:15,000
We are checking what is the impact of this bug on the client or the client business.

29
00:02:15,000 --> 00:02:18,000
Okay, let me take you on the Facebook application.

30
00:02:18,000 --> 00:02:20,000
OK, here.

31
00:02:20,000 --> 00:02:27,000
If I say I have entered username, correct username and password, I try to log in, but I'm not able

32
00:02:27,000 --> 00:02:30,000
to log into the application with correct credentials.

33
00:02:30,000 --> 00:02:31,000
So it's a bug.

34
00:02:31,000 --> 00:02:33,000
But what should be the priority of this?

35
00:02:33,000 --> 00:02:35,000
It should be the highest priority.

36
00:02:35,000 --> 00:02:36,000
But why?

37
00:02:36,000 --> 00:02:42,000
Because if a customer is not able to log in so he or she will not be able to perform any duty on the

38
00:02:42,000 --> 00:02:51,000
application means my customer or my business is impacted by this more than means if the high or highest

39
00:02:51,000 --> 00:02:51,000
priority.

40
00:02:52,000 --> 00:02:58,000
But if you notice here, it's the highest priority just because it is just blocking my customer to use

41
00:02:58,000 --> 00:02:58,000
this application.

42
00:02:59,000 --> 00:03:03,000
So in priority, we check what is the impact of this book on the client or the client business?

43
00:03:03,000 --> 00:03:08,000
OK, let me take one more example here we have a Facebook page.

44
00:03:09,000 --> 00:03:10,000
Let's take an example here.

45
00:03:10,000 --> 00:03:12,000
The spelling of the Facebook is incorrect.

46
00:03:13,000 --> 00:03:14,000
I'm just taking example.

47
00:03:14,000 --> 00:03:15,000
So it's a book.

48
00:03:16,000 --> 00:03:17,000
But what should be the priority?

49
00:03:18,000 --> 00:03:22,000
From my point of view, it should be the highest, or I say, high priority.

50
00:03:22,000 --> 00:03:23,000
Why?

51
00:03:23,000 --> 00:03:25,000
Because all the customers.

52
00:03:26,000 --> 00:03:28,000
It could be a normal customer.

53
00:03:28,000 --> 00:03:34,000
Or it could be any person who is going to give advertisement to the Facebook is coming to the login

54
00:03:34,000 --> 00:03:35,000
page first.

55
00:03:35,000 --> 00:03:42,000
And here, if I check, OK, the spelling is incorrect means if Facebook is not able to handle their

56
00:03:42,000 --> 00:03:46,000
own data or they are not able to correct their own data.

57
00:03:46,000 --> 00:03:51,000
So it's not sure, but they will be able to display my advertisement correctly or not.

58
00:03:51,000 --> 00:03:57,000
So ultimately, Facebook is going to lose the customer or lose the business.

59
00:03:57,000 --> 00:04:02,000
So here in practice, we check what is the impact of the book on the client or the client business,

60
00:04:03,000 --> 00:04:05,000
and more impact means more priority.

61
00:04:07,000 --> 00:04:11,000
Then we talk about severity in severity.

62
00:04:11,000 --> 00:04:14,000
We check what is the impact of the book on the application.

63
00:04:15,000 --> 00:04:17,000
More and more severity.

64
00:04:17,000 --> 00:04:19,000
So let's take the same example.

65
00:04:20,000 --> 00:04:21,000
I'm putting username.

66
00:04:21,000 --> 00:04:22,000
I'm putting password.

67
00:04:22,000 --> 00:04:24,000
I click on the sign in button.

68
00:04:24,000 --> 00:04:25,000
I'm not able to log in.

69
00:04:25,000 --> 00:04:27,000
It's about what should be the priority.

70
00:04:27,000 --> 00:04:32,000
It highest priority book way because it is impacting my business.

71
00:04:33,000 --> 00:04:37,000
But in severity, we check what is the impact of the on the application.

72
00:04:37,000 --> 00:04:43,000
So if we take the same scenario here, if we are not able to log in, so means we are not able to use

73
00:04:43,000 --> 00:04:43,000
application.

74
00:04:43,000 --> 00:04:44,000
No.

75
00:04:44,000 --> 00:04:47,000
So it's it's a blocker for the complete application.

76
00:04:48,000 --> 00:04:50,000
It's also a high severity book.

77
00:04:51,000 --> 00:04:56,000
But if we take an example, second example I was taking like Facebook or spelling is incorrect.

78
00:04:56,000 --> 00:04:57,000
We are taking example.

79
00:04:58,000 --> 00:04:59,000
So it's a high priority book.

80
00:04:59,000 --> 00:05:07,000
But if you talk about the severity, severity is low whilo because this is not impacting my application

81
00:05:07,000 --> 00:05:07,000
functionality.

82
00:05:08,000 --> 00:05:15,000
So there is almost very minimal impact when I see almost no impact because I think his a mistake.

83
00:05:15,000 --> 00:05:21,000
Still, your user is able to use the application, still am able to like still, I'm able to share so

84
00:05:21,000 --> 00:05:22,000
everything is working.

85
00:05:23,000 --> 00:05:25,000
It is very less impact on the application.

86
00:05:26,000 --> 00:05:31,000
Again, in part, we are checking what the impact of the bug on the client and the client business.

87
00:05:32,000 --> 00:05:39,000
So we are talking about a Real-Time User's usage of the application, but in severity, we check impact

88
00:05:39,000 --> 00:05:42,000
of the bug on application.

89
00:05:43,000 --> 00:05:45,000
So that is priority and severity.

90
00:05:45,000 --> 00:05:51,000
That is one of the most common question which you are going to face when you're going for software testing

91
00:05:51,000 --> 00:05:51,000
interviews.

92
00:05:53,000 --> 00:06:01,000
So here you have to find out some examples of high priority, high severity, high priority, low severity,

93
00:06:01,000 --> 00:06:05,000
low priority and high severity, low priority and low severity.

94
00:06:05,000 --> 00:06:12,000
So you can take any application like Facebook dot com, Yahoo dot com, and you can find out these examples.

95
00:06:13,000 --> 00:06:14,000
That's all we have.

96
00:06:14,000 --> 00:06:16,000
Thanks for watching this video.