1
00:00:01,000 --> 00:00:02,000
In this session, I'll explain you.

2
00:00:03,000 --> 00:00:06,000
What is the role of software, esto.

3
00:00:07,000 --> 00:00:16,000
So when you are going to start job as a software tester, what all the duties you have to do so here.

4
00:00:16,000 --> 00:00:19,000
First of all, I'll start with client requirement.

5
00:00:20,000 --> 00:00:25,000
So whenever a project is started, we will get some requirement from the client.

6
00:00:26,000 --> 00:00:28,000
So I would say these are the kind requirements.

7
00:00:29,000 --> 00:00:33,000
Now there is a very common rules in I.T. industry.

8
00:00:34,000 --> 00:00:38,000
One is software developer and other one is software desktop.

9
00:00:39,000 --> 00:00:48,000
So these requirements are given to the developers, as well as software to roll of software developers

10
00:00:48,000 --> 00:00:53,000
to understand the client, Aquaman start developing application.

11
00:00:54,000 --> 00:01:03,000
So here the role of the developer is to develop application once developers develop one or fewer functionality,

12
00:01:03,000 --> 00:01:09,000
not complete application, whenever development team develop one or few functionality that deliver that

13
00:01:09,000 --> 00:01:11,000
application to the testing team.

14
00:01:13,000 --> 00:01:19,000
Now here, the role of a software tester, this started because we also have the requirement, so we

15
00:01:19,000 --> 00:01:20,000
understand the requirement.

16
00:01:21,000 --> 00:01:25,000
And as per the requirement, we start testing that application.

17
00:01:26,000 --> 00:01:33,000
So let's take an example developer develop log in functionality of their application and deliver to

18
00:01:33,000 --> 00:01:33,000
the testing team.

19
00:01:34,000 --> 00:01:43,000
Now, as a tester, we have already understand what all the requirements given by the user for log in

20
00:01:43,000 --> 00:01:46,000
functionality know as per the requirement.

21
00:01:46,000 --> 00:01:49,000
Now we are testing that functionality here.

22
00:01:50,000 --> 00:01:58,000
It could be two situations one application is working correctly as per or I say, log in functionality

23
00:01:58,000 --> 00:02:02,000
is working correctly as per the client requirement, then everything is fine.

24
00:02:02,000 --> 00:02:05,000
You have to start the application and it is working correctly.

25
00:02:06,000 --> 00:02:11,000
But second condition could be you are testing that functionality or I would say, logging functionality

26
00:02:12,000 --> 00:02:14,000
as per the client requirement.

27
00:02:14,000 --> 00:02:22,000
But somewhere you found it is not working as per the client requirement, then you'll find application

28
00:02:22,000 --> 00:02:30,000
is not working as per the client requirement means it's error, or we can call it the fix or bug, so

29
00:02:30,000 --> 00:02:31,000
you'll find a bug.

30
00:02:32,000 --> 00:02:34,000
What will you do when you find a bug?

31
00:02:36,000 --> 00:02:43,000
We, as a software tester will report that bug to the developer means the part that bugs information

32
00:02:43,000 --> 00:02:44,000
to the developer.

33
00:02:45,000 --> 00:02:49,000
Now it's developer responsibility to fix it or to correct it.

34
00:02:50,000 --> 00:02:55,000
Now, after correcting developer will give that fix to the tester.

35
00:02:55,000 --> 00:03:00,000
And now, as a tester, we need to test it again that the bug is fixed or not.

36
00:03:00,000 --> 00:03:02,000
So here you can see major live.

37
00:03:02,000 --> 00:03:07,000
You are doing the two tasks one we are testing whatever the new functionalities we are getting.

38
00:03:08,000 --> 00:03:14,000
And second, whatever the bugs we have reported, that is fixed by the developer.

39
00:03:15,000 --> 00:03:16,000
We are testing it.

40
00:03:16,000 --> 00:03:17,000
It is fixed or not.

41
00:03:18,000 --> 00:03:18,000
So here.

42
00:03:18,000 --> 00:03:20,000
That is a very important point.

43
00:03:20,000 --> 00:03:24,000
Whenever we are getting any bug, we are not fixing it.

44
00:03:24,000 --> 00:03:25,000
We are not changing the code.

45
00:03:26,000 --> 00:03:31,000
We are just informing that to the developer and developers, the person who is going to change code

46
00:03:32,000 --> 00:03:33,000
to fix that bug.

47
00:03:34,000 --> 00:03:41,000
So as a tester, my responsibilities are to understand the client requirement to test functionalities,

48
00:03:41,000 --> 00:03:44,000
which we are getting from the development team for the testing.

49
00:03:44,000 --> 00:03:49,000
As for declined to comment and report defect or bug whenever we are getting.

50
00:03:50,000 --> 00:03:55,000
So that is a task we are going to do on the daily basis when we are working as a software tester.

51
00:03:56,000 --> 00:04:01,000
No hope you got a difference between the role of software developer and software tester.

52
00:04:02,000 --> 00:04:04,000
That's all we have for the session.

53
00:04:05,000 --> 00:04:05,000
For watching this with you.