On quality Assurance

All the development activities without quality assurance means are mostly not controllable, most of them have no long-term significance, and most of the norms will not really fall into the development process, and even the final delivery of the majority of the need for a substantial gas. Quality assurance in front of the added attribute: continuous, automated.
Quality assurance cannot be stopped or canceled for any internal or external reasons. If the quality assurance is canceled, it is equivalent to placing the product line on the edge of the cliff. To transition from the project to the product, first solve the product has no way to do a good job of continuous automation quality assurance. If not, then the life cycle of the product cannot be counted on for how long he can, unless he invests a lot of manpower. Because there is no continuous quality assurance, there is no reliable continuous improvement, a product that cannot be continuously improved is not a product in the real sense.
Quality assurance is not what specialized departments are going to do, nor which time period is specifically to do. It is not time to implant, root in each person's development testing activities. The lower the cost of solving the problem, the more the process of implementing quality assurance is on the front. Quality assurance should be full-face, the executive is not the leader or the grassroots cadres or employees. The more grass-roots staff level uneven project team must do a good quality assurance.
Quality assurance can not be simply understood as a narrow functional test, it to form a system, not only reflected in the test activities, but also in the project management, development process, code specification, development tools, build integration, eventually to reach everyone's habits.
In particular, products rather than operations as the core competitiveness of the company, quality assurance is the key to determine the company's business direction. If for all kinds of objective reasons really can not do continuous quality assurance, it can only show that this product is a porcelain live, we have not found diamond. Otherwise it is a product as the core is an empty talk or the ideal can not be landed.
We should not give up the quality assurance of intermediate links because of the final function test. You cannot give up quality assurance because there is no background data to match or no background service. You cannot give up quality assurance because there is a dedicated testing company to service this project. You cannot abandon quality assurance because you want to iterate quickly. None of this is contradictory.
The specific implementation of quality assurance cannot be fits. To sub-level, sub-modules according to their different characteristics to refine the specific guarantee strategy, but these strategies can not be drawn from the above description.

On quality Assurance