Welcome to the testing world in this session, I'll show you the testing and integration testing.
So first of all, I'm just coming to the retesting, OK, before moving to the retesting.
Let me move to the Gita.
If you notice I'm here on the ground and previously I have shown you how to report a defect, what I
say, how to report a bug.
So if you remember that was the book which we have reported back, you know, once we report this book,
it will go to the developer and developers are going to fix it.
We are sending it to the developer developer checking the pockets of external.
So this complete process, we are going to go in bug lifecycle.
But here I'm taking example.
I have reported the bug now developer.
Check that bug and fix it.
So once developer fix that bug developer will market the market fix as part of the status we are having
and will assign a new developer fixed bug and assign back to you.
What as a does to you will do.
So one option is that developer said it is fixed.
I just assume it is fixed and I'll close it until just no whenever any book is fixed by the developer.
We need to check it again.
But it's fixed or not is fixed.
I'll close it, if not fixed.
I just reopen the open.
It means I sign it back to the developer for fixing it again.
So what we are doing once a bug is fixed by the developer we're checking, it is fixed or not.
So I'm just coming to my application again.
And what was my book if I enter a partial data?
It should not search any dessert.
So here developers see it is fixed.
I'm checking it again.
It is fixed or not.
It is still not fixed.
So means I'm checking the buckets fixed or not.
This process is called retesting, so retesting is performed when a book is fixed by the developer and
assigned to you in the testing check.
Uppercase, fixed or not.
If it is not fixed, we will reopen it.
Reopen means we are giving it back to the developer for fixing it.
If it is fixed, we will just close it.
So I hope your understanding of retesting so you can understand this retesting is a very common testing
which you are going to do on a daily basis because when you are going to perform testing, you will
report many defects.
And whenever a developer fix fix that effect, you have to check bug or defect is fixed or not.
So that is the testing.
Next time I'm coming to regulation testing.
OK, let's take an example that that.
And it is fixed now that example, it is fixed.
To fix this defect, developer made some changes in the coding.
OK, now I have done retesting and which is past.
But the point is it might be possible because of the changes which are done by the developer.
Some other functionality which is working before now started to get filled.
So I take an example before search was working fine for other data means for the special characters
for complete data before it was working fine.
No developer change some code in the search functionality.
Because of that, this book is fixed, but it might be possible that other functionality which are working
before started to get filled.
So next type of testing is a regression testing integration testing widget.
Changes which are done by the developer are making any negative impact on the other part of the application
or not.
So integration test.
We are checking our application again because of the changes.
The functionality which are previously working fine are still working fine or not.
So that is the regression testing.
So again, as I mentioned it, creation testing is done when changes are made in the system, and these
changes could be because of bug fixing, adding a new functionality or updating the current functionality.
So changes could be because of any reason integration reject any negative impact on existing functionality
after changes made by the developer due to different reason.
OK, let's take an example of a washing machine.
I'm using my washing machine and one of the functions.
It is not working.
I called for assistance and somebody came to my home and now fixing it.
So after you fix the defect, you fix that functionality.
I'm checking that functionality is working or not.
That is retesting.
But now I'm checking other functionality of the washing machine, which are working before are still
working now or not.
That is a regression testing.
So integration, whatever the things which are working before, should work now as well.
That district integration testing now it's up to us.
We can go for the full regression or partial regression.
Full regression means whatever the changes made by the developer, and it could be changes in one functionality
and in application.
We have one functionality.
So now I'm testing all 100 functionalities again after changes done by the developer.
So that is called full duration.
Partial regression means developer made changes in one functionality.
So I'm checking only a few functionality which are related to that.
That is partial integration.
So here we have seen what is retesting and regression testing?
That's all.
We have tanks watching this video.