Welcome to the testing work.
Previously we have seen how we can create task and what is task workflow priority task end to end workflow.
Now I'll show you original estimation and actual time estimation means when we're creating a task,
we are doing the estimation like it will be completed in two days.
And when actually somebody is working on this, he or she will enter the time, how many hours or I'll
see how many days spent on a particular task.
So I'll show you how we can put estimation time and actual time.
Okay.
I'm taking example as a lead.
I'm going to create a task and assign it to my tester.
So I'll just go here and going to my dashboard first.
Okay, I take an example.
I'm working here as a lead.
I want to assign a task to my tester.
So this create a task and there's a project.
I'm going to create a task here.
Okay.
What is this, somebody?
So I'm saying it's a testing task.
And execute test cases off registration module.
Or in other words, you can write.
Registration module testing.
Mature testing and okay.
Which components belong to?
That's my registration.
You can attach it to this case of this module.
So just go here, upload.
And if you remember previously I have shown you that was the disk, so I just uploaded here.
Okay.
Now, in description, we need to write.
What exactly?
My test to have to do something first.
Execute all test cases, report all books, which you'll find while doing testing.
Retesting of all.
Fixed issues.
Issues.
So these are the tasks we need to perform.
Acceptance criteria is that.
Criteria.
All test gifts executed all bugs, reported Butera.
The testing completed.
And at the last best execution report.
Shared.
So these are the acceptance criteria for this task.
Okay.
Now I'll go and assign it to my tester.
Okay.
What does the priority?
I'm saying it's a high priority task.
I just create as of now, I'm not giving any estimation because as a lead, I don't know how many hours
my tester is going to take.
We have we can have two condition.
One is as a lead, I'll put hours, how many hours I'm giving to my tester for this task.
That is, that I want my tester to analyze this task and then put estimated hours.
So in both we it is correct.
Sometimes, if configured in the data, you will get estimated hours.
Option over here.
So you can put estimated hours.
Sometimes you will not get it.
The person who is going to work on this task will analyze and put estimated hours.
So as of now, I just put it up without any estimated hours.
Okay.
The Oscars created idea is a failed therapy known as a lead.
I have completed my task now as a tester.
I'm going to my dashboard.
So that's a dashboard of my tester.
Okay.
That is a task which is assigned to me.
Let's go and do it.
Okay.
As of now.
Now I'll go and try to analyze this task.
Okay.
After and this is iPhone.
It is going to take 15 hours or I'll see two days.
So you can put in the days or maybe in the hours.
So I take an example.
Okay.
You want to put in the form of hours.
Okay.
Here on the right hand side, you are getting show more fields.
I just click on this here.
You can put your estimation.
So I'm putting my estimation is 15 at which is 15 hours saved.
So it shows one seminar by four.
It takes eight are four a day.
But this is configurable.
You can change it.
Project admin can change it.
So as of now, original estimation is one day and 7 hours.
So I can see we have created a task, assign it to the tester.
And now estimated time has been given.
Now, as a tester, I have analyzed it.
I'll start working on this.
So when I'm starting this task, I'll just take it to the in progress.
Now, today, complete day.
I'm working on this task means I'm executing.
My task is I'm reporting my bug I verified fix issues I'm doing as bottom steps as a list acceptance
criteria.
Okay.
End of the day, this task is not completed, but I have invested total 8 hours in this task.
So previously we have defined estimated hours.
Now actual hours.
How many actual hours I have invested on this task?
I just go here.
You look at three dots, I just click on this log work as a tick on the log work.
It is asking for how many hours?
What is the time you invested on this?
You can put in the terms of hours or you can put in the terms of bids.
So I set one day I have already invested.
It will automatically calculate and show here 7 hours depending now what description you can define
like executed all functional cases, reported all books.
So these are the two task I have completed today.
I just save it.
You can check it.
Time tracking, one day logged and 7 hours remaining.
So today I started this task.
But it is not completed yet.
It is in the in progress.
I have reported my hours.
These hours are very important because by this anybody can understand how much you estimated and how
many hours you spent on a particular task.
So it's a good practice.
Whenever you are working on JIRA for task tracking, always put your hours in direct self.
So if you're managing one project, like how many hours you will do on a particular ticket or particular
task, he or she will not ask you.
They can just go directly on the JIRA and check it over here.
Okay.
Next day I come to my office and start working on this task again.
Now, today, end of the day, I have completed it.
So what I'll do is, first of all, I'll just go here.
Log work.
I have spent 6 hours even original estimation was I'll take one day and 7 hours.
But the task is completed in the 6 hours.
So.
One artist bending.
So it might be possible if you estimated the task for 20 hours, it will complete in the 20 hours.
But it also possible that if you estimate it for 20 hours, but the task is completed in 15 hours,
so you will put actual hours you spend on a task and sometimes it can take more than that as well.
Means you estimated it will take 20 hours, but in actual it took 25 hours.
So you should have your justification like previously.
While estimation I have given 20 hours.
But while working, we found this this problem.
Because of that, it took 24 hours.
So you should have your justification.
You can put less number of hours or more actual hours as compared to the estimated hours.
Okay, I'm saying task completed.
That is done.
I just click on the save task is completed, I'll just market them.
So here we have reported RS We have put our comments for each and every day.
No, my lead.
Want to check what exactly we have perform on this task.
So the lead will not ask me.
He or she will go to the JIRA.
So I'm just coming as a lead and I'm just searching for that.
But it was a file 13, which I just created.
So I'm just going for 13.
It's a F, I end 30.
Okay.
That was the task I have given to you.
You market done?
I want to check it.
I'll go to the task and here in the bottom you'll get a work log.
You can just click on this here.
You can check testing hours, which does put with the comments.
So first, it put one day executed, all test cases reported all.
But in the second day, he or she put 6 hours and the task is completed.
So as a lead, I'm not asking you what you have done on the day one, what you have done on the data.
We can just go and check it over here on the ticket itself.
Say here on that issue or task itself.
So that is that one page of using JIRA for the task management.
Now, Weber Communication is almost finished.
Mail communication is almost finished.
We are just doing everything here on the JIRA so anybody can track what exactly happening in the team
means, who is working on which ticket, what all the things are completed, what all the things are
pending, how many hours spent.
So everything can be tracked here on the JIRA itself.
So here in the session we have seen how we can go for estimation hours and then actual time logging.
That's all we have for decision tanks watching this video.