Is development training necessary before testing?
After so many years of testing, we sometimes find that, in the initial stage of project testing, for example, p1c1 testing, we often start to work with the initial stages of project software products.
Bugs that may be found in the first few days are relatively superficial, and deep bugs will be found after the expiration period. So, how can we shorten or advance the expiration time?
Training in the beta version will be helpful.
Training is not a business training but requires the following:
The training mainly demonstrates system functions,
1. The environment and interface functions must be overwritten.
2. The main process must be overwritten.
3. Requirements and product coverage must be covered.
In this way, the role of training will become more obvious. Its role is reflected in the following aspects,
1. There is no doubt that we have already mentioned earlier that we will shorten the expiration time and advance the expiration time.
2. Naturally, development must ensure that some training functions are normal, which ensures the pass rate of Smoke Testing to a certain extent.
3. Improved self-testing requirements for development.
Some people are worried about the enforceability of such training requirements. In fact, I have used this solution in many projects.
For development, the training time is not too long, and developers developProgramIt is a natural task to explain it by yourself. It does not take too much extra time.
Of course, not all projects or daily tasks require pre-test training. If the requirements of a project or UC are complex or not detailed, such a solution will become more useful.
This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/phphot/archive/2009/07/07/4324669.aspx