Welcome to the testing world in this session, I'll show you what Bester will have to do in case when
he or she find a book.
OK, what does it mean?
It means when we are doing software testing and while doing testing, if I find a book, what will be
the next process?
OK, so let's take an example.
Previously, I've shown you that I have SARS means that if you have some requirements.
So let me go and check that requirement.
OK?
There is a requirement like user can search item by the name only, not by the partial name.
OK.
I have already shown you.
Let me move to my application and I'm doing the testing of that.
Like if users search by the complete name, it should give the output.
OK, you are getting the result.
But as per the requirement, if user search by partial name, it should not be such a key for testing
that I'm just going to the application again and I'm putting partial name like IP Edge, I'm searching
again.
Here it is still searching.
So if you see as per the requirement, it should not search, but actually it is searching.
So the expected result was in case with a partial input it should not search, but in actual results
it is working means actual and expected are not matching and we have seen previously if actual results
is not equal to the X Factor result that is called book.
Now the point is what do we need to do when we find a bug in the application so that we need to understand
in the current video?
So what?
As a tester, we will do in case we find a bug in the application?
So first of all, whenever you find a bug in the application, we will try to replicate by using the
same steps.
OK?
Sometimes when we are doing testing, we find a bug, but it always a good practice.
Whenever you find a bug, try to replicate it one more time by following the same steps.
So my step was I was going to the main page or two homepage putting partial data in the search box,
then click it.
And still, yes, I'm getting the bug.
So always, it's a good practice whenever you find a bug.
Just confirm it one more time.
So once you find a bug, try to replicate by using same steps.
If you replicate it successfully, what do we have to do now?
Once we replicate and the book is replicated successfully now, we will do bug reporting.
For that, we are going to use bug reporting tool.
So later on, I show you, what do you mean by the bug reporting tool?
So it's nothing but a software there.
We can put information about the bug, know whenever we are going for the bug reporting software.
I'm just telling you the standard process.
We are not directly filling the information of the code.
First of all, we check might be a 30 member already reported that bug.
So we're checking it over there.
If Bug is already in the system by searching it, but I'm taking example.
No, nobody reported this bug.
I'm the first person who is going to report this book.
So if no, we have to report a new bill into the system.
So I'll show you how we can report people did.
Are many bug reporting software available in the market might be you have heard about the Bug Jila JIRA
vendors.
So we have many softwares.
One of the most popular software is JIRA.
So next session, I'll show you how we can set up JIRA for this purpose.
And then I'll show you how we can report Bug into the Giro gyro.
Just to summarize over here, whenever you are testing and you find a bug first step, we will try to
replicate that by using the same ESTEP.
Yes.
Still, we are getting that book.
Now I'll go to the software, which is our bug reporting software, and then I will check.
Does anybody else previously put this bug into the software?
If answer is no, no, it's not there.
Then we'll have to report Bug for reporting we can use different software.
Just remember these names like Bajela, JIRA or BSD or many others.
We are going to use JIRA, as I told you in the next session, I'll show you how we can set up JIRA
so that you can practice on that.
And after that, I'll show you how we can report bug in that.
That's all we have for the session.
Thanks for watching this video.