Product Design Experience (5th)-QA and Testing

Suddenly I think of a professional saying of QA: You are not doing this right ...... When the PD is in full swing, there is a harsh QA/test control. It is really necessary, although often quarreling ,:)

 

First, we should clarify the two concepts. Originally, we thought that QA and testing are a concept. In fact, QA is quality control and mainly responsible for process management (such as requirement tracking process and requirement change process) configuration Management (Version Management, multi-branch Development Management), document management (such as development specifications, UI specifications), and so on. What about the maturity of the typical CMM is this, however, I do not know much about this. If you are interested, you can search for the "Maturity Model for testing", which is mentioned in the Mythical man-month blog. The test itself is simple. Let me explain my understanding.

 

From the process point of view, Alibaba's testers usually intervene in the project for the first time during the UC review. After the review is completed, developers start coding and testing starts to write the test case (TC, generally, the requirement/design document plus is used to communicate with the PD/development in person). The Tc is written at the end of the coding process and the TC review is conducted (the PD and development of corresponding functions must participate ), after the evaluation, the system enters the test execution stage, and then generates a report for multiple rounds of regression.

 

From the perspective of type, including Function Testing (unit testing, integration testing, and system testing), we use mercury quality center as a test management tool; performance testing (mainly depends on whether the system meets the performance requirements. During this period, stress testing is included to test the maximum pressure that the system can withstand ).

 

There are also two special items: one is "Acceptance Test", which is generally used when the project is outsourced or isV (independent software supplier) is introduced, tests all the functions and performance related to the system, and checks whether the project deliverables (Project Phase documents, user manuals, etc.) are complete and compliant with the specifications.

 

The second is "availability testing", which belongs to the scope of user research. The testers are not the tester in the company but the users. Microsoft calls it UAT (user acceptance testing ), it is similar.