Remember a project test questions interval is too long

I do not want to become a great programmer, just want to be a good programmer with good habits.

Foreword

Before the company experienced a project has been completed four months before the case started testing, project background is too much due to the rapid development of the company, testers backlog of projects understaffed, and I am in charge of this project test priority so it was a low has been pressing.

text

When the company recruited a number of testers, I go with the flow of the project also started testing, but the tester is the first contact of the project, did not participate in some of our previous meeting demand, so I had a premonition of this cost will be high.

Since we are already in a high-priority new project development, testers have many details need to be repeated to confirm, because the more frequent result in reduced efficiency of the new research and development projects, and later through communication testers agreed fortunately fixed time every day, to confirm she could not confirm the test point.

In the absence of a detailed meeting minutes to confirm the meeting test cases, resulting not know why four months ago confirmed To test this point, I usually have the minutes of the meeting or the decision-making process to do, is afraid of the future can not be traced to a particular Why get out of the decision-making, but this test is not the dominant conference record.

So long interval test projects need to preserve the scene and follow-up in order to avoid communication errors, repeated a few detours to reduce development efficiency.

Article continued weekly update, the original is short, really is not easy, we welcome thumbs concern, together with the exchange of technology to enhance growth.

Published 38 original articles · won praise 4 · Views 3130

Guess you like

Origin blog.csdn.net/qq845699/article/details/104313245