Hello tester, here in this module, you will learn a bit about process in how it works within the test area software as in any area of activity, the process is the next lnt strategy for those who wants to perform a particular task in a more organized and more efficient way. We can use it for example, companies, factories that produce foods, clothes, our automobiles. Anyway. If we repair off then have a manufacturing process before the product is and reaches you, he goes through a lot of modifications process of the transformation of raw material in the cleaning as well was in the finishing part. So, you can get that project in perfect condition. This also happens in the software testing area.

If you We aim to deliver quality software are very consistent software that is serving good part or rather most say so close to my requirements, it is necessary that you come to tested within well defined process. Okay. So, Eddie Wilson here to our next slide I'm here illustrating you the steps. So let's say off this software testing process, which is composed of plan that is, before even from you starts to run tests. No, that has to be tested. You plan, you raise their requirements.

You understand that the costumers need on their standards they need of the product and only then is that you pass to the other step, which would is design in the cases of test. So, I'll see you have the notion and the no ledge of the produce you were working on. You elaborate your test plan is the test cases. The two that you intend to use the test technique there you intend to use the functional test the unit in test B therefore must erase anyway. And right after that you execute the plan. You perform all this planning to validate that what you define it there in the test cases are co varying the requirements.

If the software really easy to be held in the weight, you respected your taste test. And after everything is tested and validated, you deliver their results through execution reports of the test show in which scenarios have passed In which scenarios have failed and there the team can identify where the failures are to come and be correct. So, you see that is necessary to follow this process. From the moment you do any of these activities in in incorporated order. Surely you will not make a code test. In addition to performing the corrected you just you also needed to run then in the correct order.

This is what defines a good software testing process. Well, in the next class, I'm going to talk about the process in the texture of nation part because I really lies that it many companies have a process for executing of manual tests. But as far as our automated tests are concerned, that is no longer this is standard of planning or execution. So, I'm going to talk a little better about this next class. Thanks for the attention in until then,