Throughout the domestic software test industry, from 2001, testers and test supervisors often study the preparation method of test cases. Think, you can do a good test work. actually not. Test cases are only used to meet the test override and test experience accumulation.
Our department began testing tasks in 2002, but until 2004, test cases did not bring significant results on actual testing, but in turn caused increases and resource waste. Because, the test case that has been prepared has not been seriously executed and maintained. This is not a problem with the test case itself, but the test manager's mistake!
Why have we always show a bad attitude towards test cases? Analysis, four:
1. The first is the problem of resource input. The number of people testing teams will be directly triggered. The test case is also a very meticulous job.
2. The technical knowledge required to develop test cases. The design of test cases is inseparable from technology (although in some cases can not be required), the current test team does not have a good technical foundation (such as programming experience, design experience, etc.). In addition, communication with the development group and product demand planning group is not smooth. Leading the design of the test case is very different and is too subjective (purely designer's experience).
3. The understanding of the test case is too thin. Why do you say this? Since QC is a very complex job, things are more and messy (especially in tissues in development processes), the test supervisors can easily fell into the trap of "designed to design". The preparation process and quality of the test case is not all "test case work", the implementation of the test case is the focus of this work.
4. The test authorities are too high for the expected value of the test case. The test case has been written, and it is also implemented. But after all, it is a document, it is dead, we need to use it. That is to say, the test case also needs a matching of the use of the use. For example, the test of a software version is screened and packaged according to the actual project (such as test time limits, personnel and its level, the quality of the target software), which can be better implemented in test cases. effect.