In this session, I'll explain you what is book?
When we are going to work as a software tester, this is a very common word.
We are going to face in daily activities.
So here we need to understand what is bug and different conditions of the bug.
So here I start with what is bug?
A very simple definition of the bug is if actual results of the application is not same as expected
result of the application that is called bug.
So when we are comparing actual results with expected result, there could be two possibilities either
it is compared or not.
If it is compared, then if not, it's a bug.
Okay, let me explain you.
But before moving to that, I just want to show you.
That is my client document means I have application, which is an e-commerce application.
I need to test these functionalities over there.
So here we call it S8's means system requirements, specification meets whatever the requirement we
got from the client we just placed over here.
Now, if you try to understand this fourth requirement, user can add items to the cart.
Only after user is logged in to the application.
So if I understand this requirement, after understanding, we can easily generate expected user x result
results that a person can only add items to the cart if he or she is locked in.
Now let me move to my application and and according to this requirement.
So that's my application, which is shop doctor testing.
Where dot com.
OK, here I'm not logged into the application.
I try to search for the item.
I'm searching for iPhone as I search here.
Does it add to cart button?
But as per the requirement, a person can add item to the cart.
Only person is logged in.
If you check it, I'm not logged in as of now.
I'll just click on add to cart.
If you notice items added to the cart, if you want, just check it over there.
I'm just going to cart.
And the item, the spirit over him, if you see, I'm getting my expected result from the requirement
and actual results coming when we are actually doing the testing on the application.
So if actual result is not equal to the expected dessert expected results we are getting from the client
equipment actual result.
We are getting well.
We're actually testing the application if actual results is not equal to the expected dessert, that
is bulk.
So it's a very simple definition of the book.
I'm going to explain a few more points about the book.
Here.
We have five points, which we need to understand this, we can understand book in detail.
OK?
The first point is if software's is doing something which should not do according to the SRS, OK,
let me move to the SARS first.
That's my client, Aquaman.
Try to understand these requirements.
Need Log-in functionality an application that is OK user can search item by the name, not by the partial
limb.
So here the requirement is.
User can search any item by the name.
We should get that item in the result.
But if I give partially, it should not search.
That's a requirement of the client.
OK, let's move to the application, and I'm just going to the homepage.
I'm searching by the complete name.
We are getting output.
But the requirement was if I give the partial name, we should not get any output.
That's a requirement of the client.
If you want, you can check it over here.
Requirement of the client is user can search item by the name, not by the partial name, but if I try
to do it over here, still, we are getting the dirt.
So that is our first point here, which says if software's doing something we should not do, according
to the SRS.
It's a bug.
So here in our case, software is stretching.
The result at application is giving the result with a partial limb, but as per the requirement, it
should not be.
So if software is doing something which should not do according to the to the SRS, it's it.
But second, as opposed to the first is software is not doing something which should do according to
the SRS.
OK.
Let me move to this, Chris, and I show you one more requirement.
If you click on the search result image, it should be added to the card.
So requirement is when we click any result image, it should be automatically added to the card.
Okay, let's check on the application.
So just go back.
And I'm searching for the item, and the requirement is if somebody click on this image, it should
be added to the cart.
I'm doing that, but if you notice.
Still, it is giving.
Would you like to add it to the cart?
But the comment was on the image.
It should be added to the cart.
I should not get details.
So here's the second point is if if software's not doing something, we should do according to the SRS.
So according to the SRS, it should be added to the cart, but it is not doing here.
Third point is, if Software's is doing something which is not mentioned in this us, again, if you
take it here, I'm just testing my application and I phone, I just go back.
iPhone developer has given this add to wish list functionality.
Claim don't need it time did not give any comment for this, but developer added this functionality
by his own understanding.
But that is not the requirement of the client, so we cannot add to the functionalities as per the developer
understanding it should be coming from the client.
So that's a bug because Klein does not want it.
It is not mentioned in the requirement.
So third point, if software is doing something which is not mentioned in this office, there is no
requirement for add to wishlist, but still so if they're doing something.
So that is a fourth point is very confusing.
But we should understand this if software's not doing something which is not mentioning this address,
but it should be OK.
What does it mean if software's not doing something which is not mentioning this or.
If you check it in SARS this requirement, it need need log in functionality of the application.
There is nowhere mention need logout functionality.
So the point here is developer develop that log in functionality, but not given the option of log out.
But few things are which are really common.
If you have given that log in functionality, there should be no doubt functionality as well.
But if software's not doing something, developer did not give logout functionality, which is not mentioned
in this ad is that's OK, but it should be because logging is there.
So log out is by default, so that kind of things, which should be even that is not mentioned in their
site as logout is not mentioning the site is, but that should be.
So it's a bug for you.
And last point, which is very, very good to understand if application you think it's difficult to
use or difficult to understand.
It's a bug for you.
Let me take an example.
If you developed a very good application with lots of graphics, a lot of functionalities, but when
actually users trying to use that application, he's not getting any help, he's not getting any suggestions.
So it becomes very difficult for them to use it.
So if you think application is difficult to use or if you don't understand, that's it.
But.
So here we have caught what is book on daily basis.
You will have to face this book many times daily basis.
That's all we have.
Thanks for watching this video.