I saw a few articles about QA today. Personally, QA's work should actually be divided into two parts, part of the external quality assurance, part of the internal quality control. Good software quality must be inside and outside, inside and outside. China's software companies, an indisputable fact is weakened the technical requirements of QA personnel. From the perspective of the resource itself, although it is difficult to be thick, after all, the software talents are limited, the project cycle is tight, and of course, it is necessary to put the most productive resources into the product production link. However, I want to add a little bit of experience. In addition to the test of software quality assurance, companies do not forget that there is also an internal quality needs to be effectively controlled, and this control may need to be established on a senior development / designer. Enterprises really want to make effective checks in quality, so that software products can have a longer life cycle, this work must be handed over to those senior expert team. And to let these experts are in the "fair, open" position angle to review, audit, and report on the internal quality of the software. When it comes to this, it is related to this idiom. If the quality of the software is placed in a later test, it is a post-controlled control, and this control is surface, the effect is short. A bug is already smashed, can you tell me how much a similar bug? The quality of the software is really controlled, and "there is a" trumpet salary "," anti-prevention and longness ", in the production process of software, pay attention to its inner quality in every specific link. The inherent quality is improved, and the quality of the outside is also improved, which also highlights the value of software process management.
