![]() These activities would be the ones that are hidden from view, but nevertheless is where the biggest benefit is gained for the whole organization. Furthermore, there are several important activities that should be performed before and after test execution to obtain the best possible insight into the quality of a developed product. However, this does not means that test execution is the only remarkable activity to be performed in a well-established QA process. Let’s try to explain, with a simple analogy how this can be reflected in the real life.Ģ Influence of an early start of test activitiesĪs is evidenced in IT projects, the most visible part of a quality assurance process is the actual execution of the designed test cases. Therefore, QA should be the driving force behind the quality of both the project and the process. In fact, following this last strategy could lead us, sooner or later, to important issues with the developed product, or even with the same development process as well. However, testing is (or should be) an important part from a whole known as ”Quality Assurance”: while testing is a process that provides information about quality and related risks, QA contains all the planned activities used to ensure that a system meets the requirements of quality.Īlso, it’s quite accepted all the benefits that are gained by starting quality activities as soon as possible (even from the beginning of a project!), and not only when test object has been delivered and it’s ready for test execution. It is not a surprise to find examples, even from inside of several IT organizations, of people referring to quality activities as only ”testing”.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |