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 create task and assigned to the team member.

3
00:00:09,000 --> 00:00:15,000
And I'm going to cover how we can create a task and assign it to the developer or assign it to the test.

4
00:00:15,000 --> 00:00:17,000
So let's start with the tester.

5
00:00:17,000 --> 00:00:20,000
I'm taking sample and working as a test lead.

6
00:00:20,000 --> 00:00:24,000
I want to create some task and assign it to my team members.

7
00:00:25,000 --> 00:00:26,000
So that's that.

8
00:00:27,000 --> 00:00:30,000
And here I'm logged in as a test lead.

9
00:00:30,000 --> 00:00:33,000
I want to create a task for that.

10
00:00:33,000 --> 00:00:38,000
I'll just go here and click on the create as I click on the Create.

11
00:00:38,000 --> 00:00:43,000
It shows the same form which we have seen while reporting a defect.

12
00:00:43,000 --> 00:00:47,000
But now here in the issue type, I need to select.

13
00:00:47,000 --> 00:00:50,000
Task means I want to create a task.

14
00:00:50,000 --> 00:00:51,000
Okay.

15
00:00:51,000 --> 00:00:53,000
Now what is the task?

16
00:00:53,000 --> 00:00:56,000
You want team to work on something.

17
00:00:57,000 --> 00:01:05,000
Design best guesses of registration module.

18
00:01:08,000 --> 00:01:13,000
We got a new requirement from the client in which registration module is going to be developed.

19
00:01:13,000 --> 00:01:18,000
So what I'm doing, I'm creating a task where the somebody is designed test cases for that instruction

20
00:01:18,000 --> 00:01:19,000
module.

21
00:01:20,000 --> 00:01:26,000
If you want to give a component which component it belongs to that form, it's similar to the back row,

22
00:01:26,000 --> 00:01:27,000
which component it belongs to.

23
00:01:27,000 --> 00:01:30,000
You can put it over there as you can skip it.

24
00:01:31,000 --> 00:01:32,000
No attachment.

25
00:01:33,000 --> 00:01:37,000
So here, when we're creating task, we can do attachment.

26
00:01:37,000 --> 00:01:39,000
We can give document attachment.

27
00:01:39,000 --> 00:01:43,000
So I see here we got a document or it's a requirement document.

28
00:01:43,000 --> 00:01:52,000
So what I can do, I'll just browse, upload and I can select and I can select my requirement documents.

29
00:01:52,000 --> 00:01:55,000
I'm just adding one document over here and I take an example.

30
00:01:55,000 --> 00:01:57,000
That was my requirement document for registration.

31
00:01:57,000 --> 00:02:04,000
That is very important because when my team member is going to create disguises, he or she can use

32
00:02:04,000 --> 00:02:07,000
same document or it's the same requirement document.

33
00:02:07,000 --> 00:02:08,000
So I'll just click on the insert.

34
00:02:09,000 --> 00:02:12,000
So document is added to the task.

35
00:02:12,000 --> 00:02:14,000
Now moving to the description.

36
00:02:14,000 --> 00:02:21,000
In description, we need to define the task clearly because by the description, anybody can easily

37
00:02:21,000 --> 00:02:23,000
understand what exactly they need to follow.

38
00:02:24,000 --> 00:02:32,000
So here I'm writing like write test cases, off registration.

39
00:02:34,000 --> 00:02:35,000
Module.

40
00:02:36,000 --> 00:02:39,000
And here we need to cover functional.

41
00:02:42,000 --> 00:02:48,000
Best kisses, Jill way best kisses.

42
00:02:49,000 --> 00:02:58,000
And I would say usability best kisses, some giving the complete information like I want you to create.

43
00:02:58,000 --> 00:03:00,000
I want my team member to create kisses.

44
00:03:01,000 --> 00:03:04,000
And these are the three type of testing we need to cover in tech.

45
00:03:04,000 --> 00:03:08,000
I'm just highlighting this, this text.

46
00:03:09,000 --> 00:03:10,000
Okay, that is done.

47
00:03:11,000 --> 00:03:19,000
Now, one more important area we go over to you and the name is acceptance criteria.

48
00:03:21,000 --> 00:03:25,000
Normally, we don't get acceptance criteria filled separately.

49
00:03:25,000 --> 00:03:29,000
If you're getting a separate box for the acceptance criteria, that is okay.

50
00:03:29,000 --> 00:03:32,000
If not, you can write it over here.

51
00:03:32,000 --> 00:03:36,000
But here, first of all, we need to understand what do you mean by the acceptance criteria?

52
00:03:37,000 --> 00:03:45,000
Acceptance criteria means when any percent perform distance, what should be the acceptance criteria

53
00:03:45,000 --> 00:03:49,000
for acceptance criteria means if you see the task is completed, how?

54
00:03:49,000 --> 00:03:52,000
As a lead I can check the task is completed or not.

55
00:03:53,000 --> 00:04:01,000
So I'm saying acceptance criteria would be best guess we did and as reviewed.

56
00:04:03,000 --> 00:04:06,000
That is one our best guess.

57
00:04:07,000 --> 00:04:12,000
Uploaded in shared location.

58
00:04:13,000 --> 00:04:15,000
So these are the two acceptance criteria I'm giving.

59
00:04:16,000 --> 00:04:23,000
It means when somebody is going to complete this task, we can see the task is completed only if these

60
00:04:23,000 --> 00:04:25,000
except this criteria are met.

61
00:04:26,000 --> 00:04:31,000
So as I told you, if we have a separate box, you can write the acceptance criterion, the separate

62
00:04:31,000 --> 00:04:34,000
box, else you have to put it in that description.

63
00:04:35,000 --> 00:04:42,000
So now we have created a task and given what all the things we have to cover and what is the acceptance

64
00:04:42,000 --> 00:04:43,000
criteria.

65
00:04:43,000 --> 00:04:48,000
You can also use different formatting option for doing this.

66
00:04:49,000 --> 00:04:49,000
Okay.

67
00:04:50,000 --> 00:04:53,000
As of now, I'm not relating with the issues and all issues.

68
00:04:53,000 --> 00:04:57,000
I'm just coming to assigning whom you want to assign this.

69
00:04:58,000 --> 00:05:03,000
I want to assign this to my team member with the name testing work tester.

70
00:05:03,000 --> 00:05:04,000
So you can select anybody.

71
00:05:05,000 --> 00:05:06,000
So I just selected that.

72
00:05:06,000 --> 00:05:08,000
What is the importance of this task?

73
00:05:08,000 --> 00:05:11,000
So I would say it's a high priority task.

74
00:05:12,000 --> 00:05:13,000
I had given the high priority over here.

75
00:05:13,000 --> 00:05:19,000
So as I told you, this form is almost seem, as we have seen in case of bug reporting.

76
00:05:20,000 --> 00:05:25,000
Now label, you can define the label if you want to use it in the search.

77
00:05:25,000 --> 00:05:27,000
We have seen what is the use of label previously.

78
00:05:28,000 --> 00:05:30,000
As of now, I'm not putting Epic and Sprint.

79
00:05:31,000 --> 00:05:33,000
Later on when we are going to learn Agile.

80
00:05:34,000 --> 00:05:35,000
After that, I'll show you.

81
00:05:35,000 --> 00:05:37,000
Meaning of these two fields.

82
00:05:37,000 --> 00:05:38,000
Everything is done.

83
00:05:38,000 --> 00:05:40,000
I just pick on the create.

84
00:05:40,000 --> 00:05:42,000
So one task is created.

85
00:05:42,000 --> 00:05:48,000
Idea of the task is file 11 and it is assigned to a person or 20 member.

86
00:05:48,000 --> 00:05:50,000
If you want, I just go.

87
00:05:50,000 --> 00:05:56,000
I just go to the JIRA of my team member that allows you to remember the screen.

88
00:05:56,000 --> 00:05:59,000
Now I go and check on the dashboard.

89
00:05:59,000 --> 00:06:01,000
So that is actually remember.

90
00:06:01,000 --> 00:06:04,000
One task is assigned to this member.

91
00:06:06,000 --> 00:06:13,000
So here we have seen how we can create a task and assigned to any team member in the same way.

92
00:06:13,000 --> 00:06:16,000
As of now, I have created only one task.

93
00:06:16,000 --> 00:06:18,000
We can create any number of task.

94
00:06:18,000 --> 00:06:24,000
So normally I have seen team lead is going to create the task and assigning to the different members

95
00:06:24,000 --> 00:06:24,000
of the team.

96
00:06:25,000 --> 00:06:30,000
But sometimes in the real time I have seen team lead is sending me email.

97
00:06:30,000 --> 00:06:33,000
These are the four task created.

98
00:06:34,000 --> 00:06:36,000
I'll create the task and assign it to myself.

99
00:06:36,000 --> 00:06:39,000
Then I'll send email back to the team lead.

100
00:06:39,000 --> 00:06:40,000
I have created the task.

101
00:06:40,000 --> 00:06:41,000
Please verify.

102
00:06:42,000 --> 00:06:42,000
So.

103
00:06:42,000 --> 00:06:43,000
So.

104
00:06:43,000 --> 00:06:46,000
Sometimes you will notice team lead is going to create task and assign it to you.

105
00:06:47,000 --> 00:06:54,000
And in some cases you will see you got an email to create a task for yourself, assign it to yourself

106
00:06:54,000 --> 00:06:57,000
and just verify with that lead.

107
00:06:58,000 --> 00:07:02,000
Now, as of now, I have created only one task and assigned to the team member.

108
00:07:02,000 --> 00:07:08,000
In the same way as a lead, I can create many task and assign to that different team members.

109
00:07:08,000 --> 00:07:13,000
So I can assign five task to one team members, seven task to another team member.

110
00:07:13,000 --> 00:07:17,000
So different task can be assigned to that different number of team members.

111
00:07:18,000 --> 00:07:18,000
Okay.

112
00:07:18,000 --> 00:07:21,000
As of now, we have created tasks for the testing.

113
00:07:21,000 --> 00:07:22,000
Let's take an example.

114
00:07:23,000 --> 00:07:28,000
I'm working as a development lead and I want to create a task for the developer for that.

115
00:07:28,000 --> 00:07:33,000
I'm just going I'm taking example like I have logged in as a team lead or as a development team lead.

116
00:07:34,000 --> 00:07:38,000
I just go to create and here I want to create a task.

117
00:07:38,000 --> 00:07:39,000
Okay.

118
00:07:39,000 --> 00:07:40,000
What task?

119
00:07:40,000 --> 00:07:45,000
You want to create something design achievement of.

120
00:07:47,000 --> 00:07:51,000
I sit at the table, I'm just giving front end off.

121
00:07:53,000 --> 00:07:54,000
The registration.

122
00:07:57,000 --> 00:08:02,000
Beach and again, component you can select or you can skip again.

123
00:08:02,000 --> 00:08:08,000
You can attach your requirement document, which developer can follow while doing the task.

124
00:08:09,000 --> 00:08:13,000
Okay, now I'm coming to the description and we know what we need to write in the description first.

125
00:08:14,000 --> 00:08:14,000
What exactly?

126
00:08:14,000 --> 00:08:24,000
You want your team member to perform something right at DML of registration page

127
00:08:26,000 --> 00:08:32,000
seven page as per requirement document.

128
00:08:34,000 --> 00:08:37,000
Second, I'm saying apply.

129
00:08:39,000 --> 00:08:41,000
Do you wait validations.

130
00:08:42,000 --> 00:08:42,000
Okay.

131
00:08:42,000 --> 00:08:45,000
What is acceptance criteria?

132
00:08:45,000 --> 00:08:49,000
So I'm saying acceptance criteria is.

133
00:08:51,000 --> 00:08:55,000
Which is reviewed.

134
00:08:59,000 --> 00:09:01,000
Unit testing is completed.

135
00:09:04,000 --> 00:09:13,000
Completed in the same way you can write more points or adhere or more acceptance criteria again whom

136
00:09:13,000 --> 00:09:13,000
you want to assign it.

137
00:09:13,000 --> 00:09:18,000
I want to assign it to my developer so that as a developer user, what is the priority you want to give?

138
00:09:18,000 --> 00:09:22,000
So you can give any priority and you can just click on that create.

139
00:09:22,000 --> 00:09:27,000
So one more task is created, which is assigned to the developer in the same way you can create many

140
00:09:27,000 --> 00:09:29,000
task assigned to the different developers.

141
00:09:31,000 --> 00:09:34,000
One more thing I want to show you here when we are creating task.

142
00:09:34,000 --> 00:09:35,000
So let's take an example.

143
00:09:35,000 --> 00:09:40,000
I have created a task and the ID was 12.

144
00:09:40,000 --> 00:09:48,000
So when you are creating tasks, it's always a good practice to define what kind of task it is because

145
00:09:48,000 --> 00:09:53,000
same form you are using for creating a testing task, same you are using for the development task.

146
00:09:54,000 --> 00:09:56,000
Same will be used for the different type of task.

147
00:09:56,000 --> 00:09:59,000
So it will be a good practice when you are creating the task.

148
00:09:59,000 --> 00:10:01,000
You can define what kind of task it is.

149
00:10:02,000 --> 00:10:07,000
So you can mention like Dev or you can write it like testing.

150
00:10:08,000 --> 00:10:10,000
So I'm just writing here development.

151
00:10:13,000 --> 00:10:14,000
I just save it.

152
00:10:14,000 --> 00:10:19,000
Now, it will be easy for anyone to track, which is the development task and which is the testing task.

153
00:10:20,000 --> 00:10:25,000
As of now, we only two task, but later on when we have many team members, I have created a lot of

154
00:10:25,000 --> 00:10:28,000
task or I take an example, I have created 200,000.

155
00:10:29,000 --> 00:10:34,000
In that case, if we mention like which is the development and which is the distinct path, anybody

156
00:10:34,000 --> 00:10:39,000
can understand which one is the development or testing task just by looking somebody of the task.

157
00:10:40,000 --> 00:10:44,000
So it's always a good practice to write what kind of task you are creating.

158
00:10:45,000 --> 00:10:46,000
But it's not mandatory.

159
00:10:46,000 --> 00:10:47,000
It's up to you.

160
00:10:47,000 --> 00:10:50,000
If you want to write it, you can else you can skip.

161
00:10:51,000 --> 00:10:56,000
So here in this session, we have seen how we can create task assigning to the team members.

162
00:10:56,000 --> 00:10:57,000
It could be developer or tester.

163
00:10:59,000 --> 00:11:01,000
There's all we have tanks watching this video.