1
00:00:00,000 --> 00:00:02,000
Welcome to the testing work.

2
00:00:03,000 --> 00:00:08,000
In this session, I'll show you how we can link a defect to our task.

3
00:00:09,000 --> 00:00:13,000
But before going to that, first of all, we need to understand why it is required.

4
00:00:14,000 --> 00:00:16,000
Okay, let's take an example.

5
00:00:17,000 --> 00:00:23,000
As a lead, I have created $5 to five testing task and given to the different team members.

6
00:00:24,000 --> 00:00:28,000
Now they are reporting their defects and I am checking the defects.

7
00:00:29,000 --> 00:00:33,000
But how can I identify a particular defect belongs to which task?

8
00:00:34,000 --> 00:00:41,000
So if we go for linking the defect with the task, it will be easy for anyone to find out what all the

9
00:00:41,000 --> 00:00:44,000
difference we found while doing a particular task.

10
00:00:44,000 --> 00:00:45,000
Or I can say the reverse of that.

11
00:00:46,000 --> 00:00:51,000
Whenever we are going to the defect, we can easily find out in which testing we find this defect means.

12
00:00:51,000 --> 00:00:54,000
I found this defect in registration page testing.

13
00:00:55,000 --> 00:01:02,000
So this link will be helpful from both side, from the task side and from the defect side as well.

14
00:01:02,000 --> 00:01:03,000
So let's take an example.

15
00:01:04,000 --> 00:01:08,000
Previously we have created a task which is assigned to a test.

16
00:01:08,000 --> 00:01:09,000
So let me just go there.

17
00:01:10,000 --> 00:01:12,000
So I'm working as a tester.

18
00:01:12,000 --> 00:01:17,000
My lead is lead assigned this task to me it was registration module testing.

19
00:01:17,000 --> 00:01:18,000
Okay, let's go there.

20
00:01:20,000 --> 00:01:21,000
So this was the task.

21
00:01:21,000 --> 00:01:22,000
Okay.

22
00:01:22,000 --> 00:01:24,000
Now it is in the in progress.

23
00:01:24,000 --> 00:01:26,000
I'm doing testing of this.

24
00:01:26,000 --> 00:01:27,000
Okay.

25
00:01:27,000 --> 00:01:29,000
While testing, I found a book.

26
00:01:30,000 --> 00:01:32,000
I want to report a book here.

27
00:01:33,000 --> 00:01:36,000
So we have two option either.

28
00:01:36,000 --> 00:01:39,000
I can just go and create a book.

29
00:01:40,000 --> 00:01:42,000
I'm just going here and creating a new book.

30
00:01:43,000 --> 00:01:46,000
I'm seeing registration.

31
00:01:48,000 --> 00:01:53,000
Is not working in case of.

32
00:01:56,000 --> 00:02:03,000
In case of not filling, not mandatory data.

33
00:02:03,000 --> 00:02:10,000
My point over here is it could be any, but as of now, I'm just taking as in the details.

34
00:02:11,000 --> 00:02:17,000
Okay, here I'm putting details and priority is medium.

35
00:02:17,000 --> 00:02:21,000
Important thing is that I want to link this defect to task.

36
00:02:22,000 --> 00:02:25,000
So if you can see the task, it was a file 13.

37
00:02:26,000 --> 00:02:29,000
I want to link this defect to that particular task.

38
00:02:29,000 --> 00:02:30,000
So how we can do it.

39
00:02:31,000 --> 00:02:36,000
I just go and here you are getting link issue.

40
00:02:36,000 --> 00:02:45,000
So I'm just linking this defect to I'm just selecting the relates to means this defect related to and

41
00:02:45,000 --> 00:02:56,000
I'm just going for file 13 that is my task just make it link at advantage would be now if someone comes

42
00:02:56,000 --> 00:02:57,000
to this task.

43
00:02:57,000 --> 00:03:04,000
So I have while doing testing I have reported a defect and this defect is linked to a particular task.

44
00:03:04,000 --> 00:03:06,000
So let's take an example.

45
00:03:06,000 --> 00:03:14,000
Anybody who will go to a particular task so as a lead or as a manager, I'm just checking the task.

46
00:03:14,000 --> 00:03:15,000
File 13.

47
00:03:16,000 --> 00:03:22,000
Here on this page you can easily find okay, while doing the testing, this is the bug which is reported

48
00:03:24,000 --> 00:03:32,000
or if somebody is looking this defect here also he or she can check this bug is related to this task.

49
00:03:32,000 --> 00:03:35,000
So I can say we can check it from both site.

50
00:03:35,000 --> 00:03:40,000
Either if you are going to the task, you can check what all the bugs which are link to a particular

51
00:03:40,000 --> 00:03:41,000
task.

52
00:03:42,000 --> 00:03:43,000
On Arxiv.

53
00:03:43,000 --> 00:03:43,000
What?

54
00:03:43,000 --> 00:03:46,000
All the bugs we found while doing a particular task.

55
00:03:46,000 --> 00:03:48,000
In the same vein, you are linked to the bug.

56
00:03:48,000 --> 00:03:53,000
You could easily found task related to the bug.

57
00:03:54,000 --> 00:03:56,000
Now I'll give you one more example.

58
00:03:56,000 --> 00:03:59,000
I'll just go to the dashboard and I'm taking example.

59
00:03:59,000 --> 00:04:00,000
I'm working on this task.

60
00:04:01,000 --> 00:04:01,000
Okay.

61
00:04:01,000 --> 00:04:04,000
While working on this task, I found a bug.

62
00:04:04,000 --> 00:04:11,000
So previously we have reported about by clicking on here on the create button and just make a link from

63
00:04:11,000 --> 00:04:11,000
here.

64
00:04:12,000 --> 00:04:20,000
Another approach is that if you already reported a bug previously but you did not link it with the task

65
00:04:20,000 --> 00:04:23,000
and now you want to link it how we can do it.

66
00:04:23,000 --> 00:04:29,000
So just go here on the link issue and you can see it's related to which bug.

67
00:04:30,000 --> 00:04:33,000
So you can search your book and just put it here.

68
00:04:34,000 --> 00:04:37,000
Now you link with another bug.

69
00:04:38,000 --> 00:04:39,000
So we have two examples.

70
00:04:39,000 --> 00:04:44,000
One, I have reported a defect previously, but then I did not link it.

71
00:04:44,000 --> 00:04:45,000
Here I can link it.

72
00:04:46,000 --> 00:04:48,000
Another option is that I'm creating a new bug.

73
00:04:48,000 --> 00:04:54,000
When I say I am creating it, I'm reporting a new above and want to make link while reporting it.

74
00:04:54,000 --> 00:04:57,000
So we can just make it link from here.

75
00:04:58,000 --> 00:05:05,000
So here we have seen how we can link it effect to the task and how it's going to be important because

76
00:05:05,000 --> 00:05:10,000
he had the importance is if somebody want to check how many you found while doing this task.

77
00:05:11,000 --> 00:05:15,000
So he or she will not have to go to the bugs, will not have to go to the report.

78
00:05:16,000 --> 00:05:17,000
We can easily check it over here.

79
00:05:19,000 --> 00:05:21,000
That's all we have for this session.

80
00:05:21,000 --> 00:05:22,000
Thanks for watching this video.