First, the test case and test work itself is constantly perfect. In the early stages of the development process, it can be considered as a demand phase, or there is no design phase of the regulation of demand. If there is a relatively clear demand document, you can check the design test case after you check the demand document at this stage. Here, the inspection of the demand document is mainly two aspects: 1. Check the correctness of the demand document description, and is very familiar with the business involved in the test, such as a simple financial software, then the tester itself It is necessary to familiarize with accounting work, the financial system is familiar, do not superstitially the so-called "real needs" when checking the demand document, there are two problems, one is whether the user really describes its needs correctly. Second, whether the demand person can really understand the demand correctly. In addition, there is another problem that the user is in line with the problem of industry norms. If it does not meet, if it is necessary to confirm that there is a hidden danger, the user may suddenly ask them to take industry norms in the later stage of development, let you Demand changes, so you have to be clear in advance. 2. Check the accuracy of the demand document description. It is mainly to consider whether there is a blurred place in the document, which must be clear for yourself unclear. At this time, it is necessary to guarantee the testability of the demand - I am proud to say that the guarantee demand can be fully served. So after the demand is finished, you can start designing test cases, ignorant, because you didn't start design work, so on the test case, you can't just start from the interface - Although the RUP requires this item. Therefore, the design of the test case should be set from the actual business from the actual business. Of course, in the description of the test case, try to consider how the application is disengaged from the application. Of course, the test case implemented at this stage is perfect, only some content can only be covered, but I think these usual examples are not all functional test cases, but also in the entire project. However, when lacking the demand document, it is necessary to play the ability of the test personnel, to take the initiative, not passive waiting. To try to be familiar with the actual business, try to work with what you can think of. I believe that friends who have learned Marx's philosophy know what is objective and subjective initiative.
Of course, in the design phase and the final coding phase, you can continue to add, modify or remove some test cases, making it more perfect.
Jackei by 2004-01-09
