Inconsistencies between QA and rd _ Spit

Just now, just before I said, "OK, trouble." "And when my tears came down. But not cowardice, but thanks, thank QA for the righteous words, thank QA Division of Labor Clear, thank QA for their due diligence. I was wrong, I should not explain so much, just make sure if there is no problem, the CR turned off, if unsure, then continue to verify. QA does not care about the later version is OK, he only cares about the version of his test is not OK, so to give you CR, you do not take after the version to check, as long as the version of the QA report to test the good ... But QA does not know that things are changing and developing. He didn't know that the version he was testing was problematic, and it didn't mean that the later version would have a problem. As an RD, not just staring at the version of QA to have problems on the two eyes a black oblivious hard solution, not to solve, but to take QA before the version and after the version to test, whether there is a problem, this is really wrong. No, I don't think so. So I will feel wronged, can not help shedding tears. But the key is not to say that rd you do wrong, but QA no matter how you do, he just your results, this CR describes the problem, in the next test of QA will appear, in addition, he does not care. So you're wrong, what to do when you go to QA to discuss this problem, tell him later version OK.

QA is the person who discovers the problem, RD is the person who solves the problem, and QA also verifies that Rd really solves the problem. Different division of labor, different responsibilities, so the same point of view is also different. That's all.

Thanks to the role of SI, this great patient can take care of the role of all parties, with him, the problem has been found, resolved, be validated.

Dinner, I was afraid of their good scars forget the pain, I would like to commemorate every day wonderful and no lack of a variety of stories of the programmer life.