Welcome back. In this module, we will discuss the roles and responsibilities of a software tester. And software testers duties. They are to read and analyze requirements. So if I can go back to exercise one, you were required to write at least three requirements for the product or service that you wanted to purchase. While software tester would take the place of view the user, the software tester would read and analyze your requirements that you listed in the world of software development, a business analyst in many cases would come to you and they would take your requirements that you mentioned and they were document them and a requirement documentation, a software tester would read those requirements.

Next, a software tester would come up or create test scenarios and test scenarios. So basically, if I could go back to exercise one, you were required to think of some ways on how you would test your three features or your requirements. Those are call test ideas or test scenarios. Well, a software tester would read those requirements, and they will think of ways on how they can test those requirements. Next, they will create test cases. And as we move further into the course, we will go into will define exactly what test cases are.

A software tester would also generate test data. And again, we'll discuss exactly What tests they do is as we move forward in the course, they then would execute those test cases. And test cases or they are a testing document in a tester would execute those. And again, we'll explain exactly what test cases are as we move forward. And then finally, the next I should say, a tester would create and report defects. So a tester if they found any problems with the system, as we mentioned earlier, and just some of those examples of why software testing is important.

A software tester good software, a text tester would detect those defects. They would document them and send them over to a developer or the person that created this system. report those defects. And the developer designer will fix those problems. Were in addition to these things that I just listed listed as software testers, they are also trying to break this system. So not only are they testing your system out, or testing your requirements to see if they're the system is performing the way it's supposed to, they're going to do something else to try to break the system.

So say for example, if you have a login field, and the User Name field states that that requirement should accept only f1 f1 characters, while a software tester, they will test that login name. feel forced to make sure that africare witches are accepted. Accept it. They would also be in see if something else outside of that like out of alphanumeric or numeric characters, they would also test a new field to see if they feel will accept something else outside of Africa which was only and this is an example of trying to break the system. So, just to recap on the duties of software a test to start, they read and analyze requirement. Next, they create a create test scenarios.

They create test cases, they generate test data, they execute test cases, they create and report defects and they also try to break the system. Now in some other organization There are other miscellaneous duties that a software tester would perform. But as a just in general, these are some duties that a software tester performs across the board regardless of what company that you that tester works for. What makes a great software tester. Now this will vary per Corporation. But these are just just some key skills that a tester should have for one domain knowledge, and what I mean by domain knowledge.

So the more knowledgeable you are on how the system should perform, the better you are as a tester. So let's take for example, if you work on a lending application for years, you are a lender and so the you Understand how the application performs and what it should do, and how it should work. Well, the more knowledge you have about a particular application, the better tester you will be. Next, a tester should have great analytical skills because again, you're reading a lot of documentation. So the more analytical you are, the better you would be as a tester because you're analyzing and you're questioning things. You want to have really good communication skills, you're interacting with various levels of management, and also numerous members on a project team.

You also want to have really good written verbal communication skills. your writing skills as a tester are testers responsible for creating test cases, test scenarios, test it As these things all have to be written, so the more knowledgeable they are and easy they are to read, the easier it is for everyone surrounding you, your colleagues and others to understand. You want to have a great attitude. Sometime it's in the software development industry, especially when there are tight deadlines. It can be really stressful. So you want to always keep a level head and keep calm.

When things are getting a little hairy and not take anything personal. It's everyone has the same mission in mind and agenda has the same agenda and that is to get the product out the door with exceptional quality and to make sure that that product or service meets that customer needs. So again, not take anything personally you want to have a great attitude. So when things get really stressful, it's always good to just, again, have a great attitude. Or you want to have really good technical skills, the more technical you are, the better it is for you, again, you will be a tester communicates often within their interacting with some highly technical project team members. So the more technical you are, the easier it is for you.

So when you're reporting a problem to a developer, and the more information that you can provide them technically, it makes their job easier with troubleshooting and finding out what the problem is, in order to fix it in a timely manner. And then finally, you want to be very detail oriented. The more information that you provide to a developer for example, when there's a problem The easier it is for them to to fix the issue. And, as I mentioned at the top timely manner, manner. Well, that concludes Module Three. Let's recap.

And Module Three, we discussed the roles and responsibilities of a software tester. We learn that a software testers read and analyze requirements. They also create test scenarios, test cases, and generate test data. And software testers also responsible for executing test cases in order to detect defects and bugs in the software. And if defects are found, the software tester reports those defects to a developer to have them fix again before the software is released. And finally, a software tester duties are also to test system out, not only to test the system out, but they attempt to break the system as well to see if they can find defects.

And then finally, we discuss what makes a good software tester. As mentioned in the course, this will vary per company. But just some basic things that a software a good software tester should have. They should have great analytical skills. They should be detail oriented. It would help if they had domain knowledge or knowledge of the system that they're testing.

And they should also have a great attitude. And then finally, a good software tester should have some technical skills. Again, that concludes Module Three. Thank you very much.