1
00:00:00,000 --> 00:00:08,000
Welcome to the testing world in this session, I'll show you the testing and integration testing.

2
00:00:09,000 --> 00:00:14,000
So first of all, I'm just coming to the retesting, OK, before moving to the retesting.

3
00:00:15,000 --> 00:00:16,000
Let me move to the Gita.

4
00:00:17,000 --> 00:00:22,000
If you notice I'm here on the ground and previously I have shown you how to report a defect, what I

5
00:00:22,000 --> 00:00:23,000
say, how to report a bug.

6
00:00:24,000 --> 00:00:31,000
So if you remember that was the book which we have reported back, you know, once we report this book,

7
00:00:32,000 --> 00:00:35,000
it will go to the developer and developers are going to fix it.

8
00:00:36,000 --> 00:00:39,000
We are sending it to the developer developer checking the pockets of external.

9
00:00:40,000 --> 00:00:43,000
So this complete process, we are going to go in bug lifecycle.

10
00:00:44,000 --> 00:00:45,000
But here I'm taking example.

11
00:00:45,000 --> 00:00:48,000
I have reported the bug now developer.

12
00:00:49,000 --> 00:00:50,000
Check that bug and fix it.

13
00:00:51,000 --> 00:00:58,000
So once developer fix that bug developer will market the market fix as part of the status we are having

14
00:00:59,000 --> 00:01:04,000
and will assign a new developer fixed bug and assign back to you.

15
00:01:06,000 --> 00:01:08,000
What as a does to you will do.

16
00:01:09,000 --> 00:01:12,000
So one option is that developer said it is fixed.

17
00:01:12,000 --> 00:01:20,000
I just assume it is fixed and I'll close it until just no whenever any book is fixed by the developer.

18
00:01:21,000 --> 00:01:22,000
We need to check it again.

19
00:01:23,000 --> 00:01:25,000
But it's fixed or not is fixed.

20
00:01:26,000 --> 00:01:28,000
I'll close it, if not fixed.

21
00:01:28,000 --> 00:01:30,000
I just reopen the open.

22
00:01:30,000 --> 00:01:34,000
It means I sign it back to the developer for fixing it again.

23
00:01:35,000 --> 00:01:41,000
So what we are doing once a bug is fixed by the developer we're checking, it is fixed or not.

24
00:01:41,000 --> 00:01:43,000
So I'm just coming to my application again.

25
00:01:44,000 --> 00:01:49,000
And what was my book if I enter a partial data?

26
00:01:49,000 --> 00:01:51,000
It should not search any dessert.

27
00:01:52,000 --> 00:01:54,000
So here developers see it is fixed.

28
00:01:54,000 --> 00:01:56,000
I'm checking it again.

29
00:01:56,000 --> 00:01:57,000
It is fixed or not.

30
00:01:59,000 --> 00:02:00,000
It is still not fixed.

31
00:02:01,000 --> 00:02:04,000
So means I'm checking the buckets fixed or not.

32
00:02:05,000 --> 00:02:12,000
This process is called retesting, so retesting is performed when a book is fixed by the developer and

33
00:02:12,000 --> 00:02:15,000
assigned to you in the testing check.

34
00:02:15,000 --> 00:02:16,000
Uppercase, fixed or not.

35
00:02:16,000 --> 00:02:19,000
If it is not fixed, we will reopen it.

36
00:02:19,000 --> 00:02:24,000
Reopen means we are giving it back to the developer for fixing it.

37
00:02:24,000 --> 00:02:27,000
If it is fixed, we will just close it.

38
00:02:28,000 --> 00:02:36,000
So I hope your understanding of retesting so you can understand this retesting is a very common testing

39
00:02:36,000 --> 00:02:42,000
which you are going to do on a daily basis because when you are going to perform testing, you will

40
00:02:42,000 --> 00:02:43,000
report many defects.

41
00:02:43,000 --> 00:02:50,000
And whenever a developer fix fix that effect, you have to check bug or defect is fixed or not.

42
00:02:50,000 --> 00:02:52,000
So that is the testing.

43
00:02:54,000 --> 00:02:56,000
Next time I'm coming to regulation testing.

44
00:02:57,000 --> 00:03:00,000
OK, let's take an example that that.

45
00:03:00,000 --> 00:03:03,000
And it is fixed now that example, it is fixed.

46
00:03:04,000 --> 00:03:07,000
To fix this defect, developer made some changes in the coding.

47
00:03:08,000 --> 00:03:12,000
OK, now I have done retesting and which is past.

48
00:03:13,000 --> 00:03:19,000
But the point is it might be possible because of the changes which are done by the developer.

49
00:03:20,000 --> 00:03:24,000
Some other functionality which is working before now started to get filled.

50
00:03:25,000 --> 00:03:33,000
So I take an example before search was working fine for other data means for the special characters

51
00:03:33,000 --> 00:03:36,000
for complete data before it was working fine.

52
00:03:37,000 --> 00:03:41,000
No developer change some code in the search functionality.

53
00:03:42,000 --> 00:03:48,000
Because of that, this book is fixed, but it might be possible that other functionality which are working

54
00:03:48,000 --> 00:03:50,000
before started to get filled.

55
00:03:51,000 --> 00:03:56,000
So next type of testing is a regression testing integration testing widget.

56
00:03:57,000 --> 00:04:05,000
Changes which are done by the developer are making any negative impact on the other part of the application

57
00:04:05,000 --> 00:04:05,000
or not.

58
00:04:06,000 --> 00:04:07,000
So integration test.

59
00:04:07,000 --> 00:04:11,000
We are checking our application again because of the changes.

60
00:04:11,000 --> 00:04:16,000
The functionality which are previously working fine are still working fine or not.

61
00:04:17,000 --> 00:04:19,000
So that is the regression testing.

62
00:04:20,000 --> 00:04:26,000
So again, as I mentioned it, creation testing is done when changes are made in the system, and these

63
00:04:26,000 --> 00:04:32,000
changes could be because of bug fixing, adding a new functionality or updating the current functionality.

64
00:04:32,000 --> 00:04:40,000
So changes could be because of any reason integration reject any negative impact on existing functionality

65
00:04:40,000 --> 00:04:44,000
after changes made by the developer due to different reason.

66
00:04:45,000 --> 00:04:47,000
OK, let's take an example of a washing machine.

67
00:04:48,000 --> 00:04:51,000
I'm using my washing machine and one of the functions.

68
00:04:51,000 --> 00:04:52,000
It is not working.

69
00:04:52,000 --> 00:04:56,000
I called for assistance and somebody came to my home and now fixing it.

70
00:04:57,000 --> 00:05:01,000
So after you fix the defect, you fix that functionality.

71
00:05:01,000 --> 00:05:03,000
I'm checking that functionality is working or not.

72
00:05:04,000 --> 00:05:05,000
That is retesting.

73
00:05:05,000 --> 00:05:11,000
But now I'm checking other functionality of the washing machine, which are working before are still

74
00:05:11,000 --> 00:05:12,000
working now or not.

75
00:05:13,000 --> 00:05:14,000
That is a regression testing.

76
00:05:15,000 --> 00:05:20,000
So integration, whatever the things which are working before, should work now as well.

77
00:05:21,000 --> 00:05:25,000
That district integration testing now it's up to us.

78
00:05:25,000 --> 00:05:28,000
We can go for the full regression or partial regression.

79
00:05:29,000 --> 00:05:35,000
Full regression means whatever the changes made by the developer, and it could be changes in one functionality

80
00:05:36,000 --> 00:05:37,000
and in application.

81
00:05:37,000 --> 00:05:38,000
We have one functionality.

82
00:05:38,000 --> 00:05:44,000
So now I'm testing all 100 functionalities again after changes done by the developer.

83
00:05:45,000 --> 00:05:46,000
So that is called full duration.

84
00:05:47,000 --> 00:05:51,000
Partial regression means developer made changes in one functionality.

85
00:05:51,000 --> 00:05:54,000
So I'm checking only a few functionality which are related to that.

86
00:05:55,000 --> 00:05:56,000
That is partial integration.

87
00:05:58,000 --> 00:06:01,000
So here we have seen what is retesting and regression testing?

88
00:06:01,000 --> 00:06:02,000
That's all.

89
00:06:02,000 --> 00:06:04,000
We have tanks watching this video.