1
00:00:00,000 --> 00:00:04,000
In this session, I'll explain you what is book?

2
00:00:05,000 --> 00:00:10,000
When we are going to work as a software tester, this is a very common word.

3
00:00:11,000 --> 00:00:14,000
We are going to face in daily activities.

4
00:00:14,000 --> 00:00:19,000
So here we need to understand what is bug and different conditions of the bug.

5
00:00:20,000 --> 00:00:22,000
So here I start with what is bug?

6
00:00:23,000 --> 00:00:31,000
A very simple definition of the bug is if actual results of the application is not same as expected

7
00:00:31,000 --> 00:00:33,000
result of the application that is called bug.

8
00:00:33,000 --> 00:00:38,000
So when we are comparing actual results with expected result, there could be two possibilities either

9
00:00:38,000 --> 00:00:40,000
it is compared or not.

10
00:00:40,000 --> 00:00:43,000
If it is compared, then if not, it's a bug.

11
00:00:44,000 --> 00:00:45,000
Okay, let me explain you.

12
00:00:46,000 --> 00:00:48,000
But before moving to that, I just want to show you.

13
00:00:49,000 --> 00:00:53,000
That is my client document means I have application, which is an e-commerce application.

14
00:00:54,000 --> 00:00:56,000
I need to test these functionalities over there.

15
00:00:57,000 --> 00:01:04,000
So here we call it S8's means system requirements, specification meets whatever the requirement we

16
00:01:04,000 --> 00:01:06,000
got from the client we just placed over here.

17
00:01:07,000 --> 00:01:13,000
Now, if you try to understand this fourth requirement, user can add items to the cart.

18
00:01:13,000 --> 00:01:16,000
Only after user is logged in to the application.

19
00:01:17,000 --> 00:01:25,000
So if I understand this requirement, after understanding, we can easily generate expected user x result

20
00:01:25,000 --> 00:01:31,000
results that a person can only add items to the cart if he or she is locked in.

21
00:01:32,000 --> 00:01:37,000
Now let me move to my application and and according to this requirement.

22
00:01:37,000 --> 00:01:41,000
So that's my application, which is shop doctor testing.

23
00:01:41,000 --> 00:01:42,000
Where dot com.

24
00:01:42,000 --> 00:01:44,000
OK, here I'm not logged into the application.

25
00:01:44,000 --> 00:01:46,000
I try to search for the item.

26
00:01:46,000 --> 00:01:50,000
I'm searching for iPhone as I search here.

27
00:01:50,000 --> 00:01:51,000
Does it add to cart button?

28
00:01:51,000 --> 00:01:55,000
But as per the requirement, a person can add item to the cart.

29
00:01:55,000 --> 00:01:57,000
Only person is logged in.

30
00:01:58,000 --> 00:02:00,000
If you check it, I'm not logged in as of now.

31
00:02:01,000 --> 00:02:02,000
I'll just click on add to cart.

32
00:02:03,000 --> 00:02:07,000
If you notice items added to the cart, if you want, just check it over there.

33
00:02:07,000 --> 00:02:08,000
I'm just going to cart.

34
00:02:09,000 --> 00:02:15,000
And the item, the spirit over him, if you see, I'm getting my expected result from the requirement

35
00:02:16,000 --> 00:02:20,000
and actual results coming when we are actually doing the testing on the application.

36
00:02:21,000 --> 00:02:27,000
So if actual result is not equal to the expected dessert expected results we are getting from the client

37
00:02:27,000 --> 00:02:29,000
equipment actual result.

38
00:02:29,000 --> 00:02:31,000
We are getting well.

39
00:02:31,000 --> 00:02:37,000
We're actually testing the application if actual results is not equal to the expected dessert, that

40
00:02:37,000 --> 00:02:38,000
is bulk.

41
00:02:39,000 --> 00:02:41,000
So it's a very simple definition of the book.

42
00:02:42,000 --> 00:02:45,000
I'm going to explain a few more points about the book.

43
00:02:47,000 --> 00:02:48,000
Here.

44
00:02:49,000 --> 00:02:54,000
We have five points, which we need to understand this, we can understand book in detail.

45
00:02:55,000 --> 00:02:55,000
OK?

46
00:02:55,000 --> 00:03:01,000
The first point is if software's is doing something which should not do according to the SRS, OK,

47
00:03:01,000 --> 00:03:03,000
let me move to the SARS first.

48
00:03:03,000 --> 00:03:04,000
That's my client, Aquaman.

49
00:03:05,000 --> 00:03:06,000
Try to understand these requirements.

50
00:03:07,000 --> 00:03:14,000
Need Log-in functionality an application that is OK user can search item by the name, not by the partial

51
00:03:14,000 --> 00:03:14,000
limb.

52
00:03:15,000 --> 00:03:16,000
So here the requirement is.

53
00:03:17,000 --> 00:03:20,000
User can search any item by the name.

54
00:03:20,000 --> 00:03:22,000
We should get that item in the result.

55
00:03:23,000 --> 00:03:25,000
But if I give partially, it should not search.

56
00:03:25,000 --> 00:03:26,000
That's a requirement of the client.

57
00:03:27,000 --> 00:03:33,000
OK, let's move to the application, and I'm just going to the homepage.

58
00:03:33,000 --> 00:03:35,000
I'm searching by the complete name.

59
00:03:36,000 --> 00:03:37,000
We are getting output.

60
00:03:37,000 --> 00:03:41,000
But the requirement was if I give the partial name, we should not get any output.

61
00:03:41,000 --> 00:03:43,000
That's a requirement of the client.

62
00:03:43,000 --> 00:03:45,000
If you want, you can check it over here.

63
00:03:45,000 --> 00:03:51,000
Requirement of the client is user can search item by the name, not by the partial name, but if I try

64
00:03:51,000 --> 00:03:54,000
to do it over here, still, we are getting the dirt.

65
00:03:56,000 --> 00:04:03,000
So that is our first point here, which says if software's doing something we should not do, according

66
00:04:03,000 --> 00:04:04,000
to the SRS.

67
00:04:04,000 --> 00:04:05,000
It's a bug.

68
00:04:05,000 --> 00:04:08,000
So here in our case, software is stretching.

69
00:04:08,000 --> 00:04:14,000
The result at application is giving the result with a partial limb, but as per the requirement, it

70
00:04:14,000 --> 00:04:15,000
should not be.

71
00:04:15,000 --> 00:04:20,000
So if software is doing something which should not do according to the to the SRS, it's it.

72
00:04:20,000 --> 00:04:27,000
But second, as opposed to the first is software is not doing something which should do according to

73
00:04:27,000 --> 00:04:27,000
the SRS.

74
00:04:27,000 --> 00:04:28,000
OK.

75
00:04:28,000 --> 00:04:31,000
Let me move to this, Chris, and I show you one more requirement.

76
00:04:32,000 --> 00:04:36,000
If you click on the search result image, it should be added to the card.

77
00:04:36,000 --> 00:04:43,000
So requirement is when we click any result image, it should be automatically added to the card.

78
00:04:43,000 --> 00:04:45,000
Okay, let's check on the application.

79
00:04:47,000 --> 00:04:48,000
So just go back.

80
00:04:50,000 --> 00:04:56,000
And I'm searching for the item, and the requirement is if somebody click on this image, it should

81
00:04:56,000 --> 00:04:57,000
be added to the cart.

82
00:04:57,000 --> 00:04:59,000
I'm doing that, but if you notice.

83
00:05:00,000 --> 00:05:01,000
Still, it is giving.

84
00:05:02,000 --> 00:05:03,000
Would you like to add it to the cart?

85
00:05:04,000 --> 00:05:06,000
But the comment was on the image.

86
00:05:06,000 --> 00:05:07,000
It should be added to the cart.

87
00:05:07,000 --> 00:05:09,000
I should not get details.

88
00:05:09,000 --> 00:05:17,000
So here's the second point is if if software's not doing something, we should do according to the SRS.

89
00:05:17,000 --> 00:05:22,000
So according to the SRS, it should be added to the cart, but it is not doing here.

90
00:05:23,000 --> 00:05:30,000
Third point is, if Software's is doing something which is not mentioned in this us, again, if you

91
00:05:30,000 --> 00:05:34,000
take it here, I'm just testing my application and I phone, I just go back.

92
00:05:35,000 --> 00:05:40,000
iPhone developer has given this add to wish list functionality.

93
00:05:41,000 --> 00:05:47,000
Claim don't need it time did not give any comment for this, but developer added this functionality

94
00:05:47,000 --> 00:05:49,000
by his own understanding.

95
00:05:50,000 --> 00:05:56,000
But that is not the requirement of the client, so we cannot add to the functionalities as per the developer

96
00:05:56,000 --> 00:05:59,000
understanding it should be coming from the client.

97
00:05:59,000 --> 00:06:02,000
So that's a bug because Klein does not want it.

98
00:06:02,000 --> 00:06:04,000
It is not mentioned in the requirement.

99
00:06:05,000 --> 00:06:11,000
So third point, if software is doing something which is not mentioned in this office, there is no

100
00:06:11,000 --> 00:06:15,000
requirement for add to wishlist, but still so if they're doing something.

101
00:06:16,000 --> 00:06:19,000
So that is a fourth point is very confusing.

102
00:06:20,000 --> 00:06:26,000
But we should understand this if software's not doing something which is not mentioning this address,

103
00:06:26,000 --> 00:06:27,000
but it should be OK.

104
00:06:27,000 --> 00:06:31,000
What does it mean if software's not doing something which is not mentioning this or.

105
00:06:32,000 --> 00:06:40,000
If you check it in SARS this requirement, it need need log in functionality of the application.

106
00:06:41,000 --> 00:06:45,000
There is nowhere mention need logout functionality.

107
00:06:46,000 --> 00:06:53,000
So the point here is developer develop that log in functionality, but not given the option of log out.

108
00:06:54,000 --> 00:06:56,000
But few things are which are really common.

109
00:06:56,000 --> 00:07:01,000
If you have given that log in functionality, there should be no doubt functionality as well.

110
00:07:01,000 --> 00:07:07,000
But if software's not doing something, developer did not give logout functionality, which is not mentioned

111
00:07:07,000 --> 00:07:11,000
in this ad is that's OK, but it should be because logging is there.

112
00:07:11,000 --> 00:07:17,000
So log out is by default, so that kind of things, which should be even that is not mentioned in their

113
00:07:17,000 --> 00:07:21,000
site as logout is not mentioning the site is, but that should be.

114
00:07:21,000 --> 00:07:22,000
So it's a bug for you.

115
00:07:23,000 --> 00:07:29,000
And last point, which is very, very good to understand if application you think it's difficult to

116
00:07:29,000 --> 00:07:31,000
use or difficult to understand.

117
00:07:31,000 --> 00:07:32,000
It's a bug for you.

118
00:07:32,000 --> 00:07:34,000
Let me take an example.

119
00:07:34,000 --> 00:07:40,000
If you developed a very good application with lots of graphics, a lot of functionalities, but when

120
00:07:40,000 --> 00:07:45,000
actually users trying to use that application, he's not getting any help, he's not getting any suggestions.

121
00:07:46,000 --> 00:07:48,000
So it becomes very difficult for them to use it.

122
00:07:49,000 --> 00:07:54,000
So if you think application is difficult to use or if you don't understand, that's it.

123
00:07:54,000 --> 00:07:54,000
But.

124
00:07:56,000 --> 00:08:00,000
So here we have caught what is book on daily basis.

125
00:08:00,000 --> 00:08:04,000
You will have to face this book many times daily basis.

126
00:08:05,000 --> 00:08:06,000
That's all we have.

127
00:08:07,000 --> 00:08:08,000
Thanks for watching this video.