Relationship between development and QA

Developers should not tell qa about it.ProgramHow the function is implemented, you only need to tell him which requirement and what functions are implemented, and you can establish and propose the methods in which these functions can be verified. Developers cannot tell QA how to test a function. This is a taboo for teamwork. QA develops its own test plan through requirement analysis and design understanding, it includes test scheme, test method, test data, and test tool. Both development and QA are based on requirements. Their division of labor is a serial relationship, but the function is a parallel relationship.
QA verifies the compliance of the program from its own perspective based on the information they have mastered. They must communicate with developers in depth, but must stick to their own positions to avoid being misled ", they will never believe in the Self-integrity of development, nor use the "one-sided word" of development as the test criteria or change the standards of their own tests-they are objective needs.
The relationship between development and QA is mutual cooperation, but they are independent of each other. They promote each other, but they are mutually constrained. They have their own expertise and shortcomings, so they can make up for each other; they have different angles and different priorities, so they can be fully controlled. The relationship between development and QA, such as the two legs of the same person, can work together to move forward steadily.

As mentioned above, the most important thing is that QA cannot repeat the development path. If so, there is no guarantee for product quality testing. Developers cannot instill their own testing methods into QA as soon as possible. Our goal is to discover as many bugs as possible before going online, we hope that our own people will discover bugs, rather than waiting for users to discover bugs after going online. This is our sin.

Hangzhou 2011.8