Welcome to the testing work.
In this session, I'll show you how we can create task and assigned to the team member.
And I'm going to cover how we can create a task and assign it to the developer or assign it to the test.
So let's start with the tester.
I'm taking sample and working as a test lead.
I want to create some task and assign it to my team members.
So that's that.
And here I'm logged in as a test lead.
I want to create a task for that.
I'll just go here and click on the create as I click on the Create.
It shows the same form which we have seen while reporting a defect.
But now here in the issue type, I need to select.
Task means I want to create a task.
Okay.
Now what is the task?
You want team to work on something.
Design best guesses of registration module.
We got a new requirement from the client in which registration module is going to be developed.
So what I'm doing, I'm creating a task where the somebody is designed test cases for that instruction
module.
If you want to give a component which component it belongs to that form, it's similar to the back row,
which component it belongs to.
You can put it over there as you can skip it.
No attachment.
So here, when we're creating task, we can do attachment.
We can give document attachment.
So I see here we got a document or it's a requirement document.
So what I can do, I'll just browse, upload and I can select and I can select my requirement documents.
I'm just adding one document over here and I take an example.
That was my requirement document for registration.
That is very important because when my team member is going to create disguises, he or she can use
same document or it's the same requirement document.
So I'll just click on the insert.
So document is added to the task.
Now moving to the description.
In description, we need to define the task clearly because by the description, anybody can easily
understand what exactly they need to follow.
So here I'm writing like write test cases, off registration.
Module.
And here we need to cover functional.
Best kisses, Jill way best kisses.
And I would say usability best kisses, some giving the complete information like I want you to create.
I want my team member to create kisses.
And these are the three type of testing we need to cover in tech.
I'm just highlighting this, this text.
Okay, that is done.
Now, one more important area we go over to you and the name is acceptance criteria.
Normally, we don't get acceptance criteria filled separately.
If you're getting a separate box for the acceptance criteria, that is okay.
If not, you can write it over here.
But here, first of all, we need to understand what do you mean by the acceptance criteria?
Acceptance criteria means when any percent perform distance, what should be the acceptance criteria
for acceptance criteria means if you see the task is completed, how?
As a lead I can check the task is completed or not.
So I'm saying acceptance criteria would be best guess we did and as reviewed.
That is one our best guess.
Uploaded in shared location.
So these are the two acceptance criteria I'm giving.
It means when somebody is going to complete this task, we can see the task is completed only if these
except this criteria are met.
So as I told you, if we have a separate box, you can write the acceptance criterion, the separate
box, else you have to put it in that description.
So now we have created a task and given what all the things we have to cover and what is the acceptance
criteria.
You can also use different formatting option for doing this.
Okay.
As of now, I'm not relating with the issues and all issues.
I'm just coming to assigning whom you want to assign this.
I want to assign this to my team member with the name testing work tester.
So you can select anybody.
So I just selected that.
What is the importance of this task?
So I would say it's a high priority task.
I had given the high priority over here.
So as I told you, this form is almost seem, as we have seen in case of bug reporting.
Now label, you can define the label if you want to use it in the search.
We have seen what is the use of label previously.
As of now, I'm not putting Epic and Sprint.
Later on when we are going to learn Agile.
After that, I'll show you.
Meaning of these two fields.
Everything is done.
I just pick on the create.
So one task is created.
Idea of the task is file 11 and it is assigned to a person or 20 member.
If you want, I just go.
I just go to the JIRA of my team member that allows you to remember the screen.
Now I go and check on the dashboard.
So that is actually remember.
One task is assigned to this member.
So here we have seen how we can create a task and assigned to any team member in the same way.
As of now, I have created only one task.
We can create any number of task.
So normally I have seen team lead is going to create the task and assigning to the different members
of the team.
But sometimes in the real time I have seen team lead is sending me email.
These are the four task created.
I'll create the task and assign it to myself.
Then I'll send email back to the team lead.
I have created the task.
Please verify.
So.
Sometimes you will notice team lead is going to create task and assign it to you.
And in some cases you will see you got an email to create a task for yourself, assign it to yourself
and just verify with that lead.
Now, as of now, I have created only one task and assigned to the team member.
In the same way as a lead, I can create many task and assign to that different team members.
So I can assign five task to one team members, seven task to another team member.
So different task can be assigned to that different number of team members.
Okay.
As of now, we have created tasks for the testing.
Let's take an example.
I'm working as a development lead and I want to create a task for the developer for that.
I'm just going I'm taking example like I have logged in as a team lead or as a development team lead.
I just go to create and here I want to create a task.
Okay.
What task?
You want to create something design achievement of.
I sit at the table, I'm just giving front end off.
The registration.
Beach and again, component you can select or you can skip again.
You can attach your requirement document, which developer can follow while doing the task.
Okay, now I'm coming to the description and we know what we need to write in the description first.
What exactly?
You want your team member to perform something right at DML of registration page
seven page as per requirement document.
Second, I'm saying apply.
Do you wait validations.
Okay.
What is acceptance criteria?
So I'm saying acceptance criteria is.
Which is reviewed.
Unit testing is completed.
Completed in the same way you can write more points or adhere or more acceptance criteria again whom
you want to assign it.
I want to assign it to my developer so that as a developer user, what is the priority you want to give?
So you can give any priority and you can just click on that create.
So one more task is created, which is assigned to the developer in the same way you can create many
task assigned to the different developers.
One more thing I want to show you here when we are creating task.
So let's take an example.
I have created a task and the ID was 12.
So when you are creating tasks, it's always a good practice to define what kind of task it is because
same form you are using for creating a testing task, same you are using for the development task.
Same will be used for the different type of task.
So it will be a good practice when you are creating the task.
You can define what kind of task it is.
So you can mention like Dev or you can write it like testing.
So I'm just writing here development.
I just save it.
Now, it will be easy for anyone to track, which is the development task and which is the testing task.
As of now, we only two task, but later on when we have many team members, I have created a lot of
task or I take an example, I have created 200,000.
In that case, if we mention like which is the development and which is the distinct path, anybody
can understand which one is the development or testing task just by looking somebody of the task.
So it's always a good practice to write what kind of task you are creating.
But it's not mandatory.
It's up to you.
If you want to write it, you can else you can skip.
So here in this session, we have seen how we can create task assigning to the team members.
It could be developer or tester.
There's all we have tanks watching this video.