?? Now in terms of testing, the first is the introduction of some tools. Here,: ?? 1.TestManager. It is mainly used to manage test cases and test implementation and some things in test logs, and more features have not been studied. ?? 2. ClearQUSET. Since the introduction, the effect is better, this time is mainly to consider adjustments to some process details. ?? 3.Robot. It will be used as a near future, and it is desirable to improve test efficiency by using the automated script. ?? 4.Manual test. It is also a test tool for Rational, mainly considering instead of Word documents, used to write test cases that use manual methods. ?? 5.RequisitePro. Test the management of test requirements. The content regarding the test demand will be specified below.
?? For testing the same needs, the relationship between testing the same development, the idea of the same needs is clear, and now is shown below. ?? First of all, the relationship between software or product needs is the same as test needs. Test demand is a event recommended in the test process in Rational, but there is no specificity in Rational. The current understanding is similar to the role of software requirements, clear what is going to do and determines priority. The concept of testing the test demand is to consider that if many people do, there may be different views due to different understandings of the demand, but may miss some test content. For example, a "user login" feature, this feature is described below: User Login: The user can verify the legality of the user by user login, and legal users can log in to the system. So this feature has two places that need to be tested, you can generate two test requirements: ?? 1. Check if the user's legitimacy check function is correct; ?? 2. Checking the system correctly corresponds to whether the user login operation is correct.?? Here is a check standard, how can it be an end of the user login operation. For the first test requirements, different usernames and passwords will be verified, and the second feature uses the legal user of different attributes to verify. That is, through two test needs to ensure coverage of a software requirement, the test needs are performed in design test requirements. The above example is a software demand corresponding to multiple test requirements. Of course, most software needs may be a corresponding relationship with test requirements, and many software requirements correspond to a test demand. • The solution for this problem is as follows: ?? Add a demand type in the RequsitePro demand item - can be defined as TsetRequirement (TR), with one or more software requirements in the FROM property of each test. When the demand changes are, they can be used directly through the view to be connected to modify the test demand. After completing the design of the test case, establish a test case in the TestManager to associate the association to the test demand directly - of course, can also be associated with software requirements. In this way, the tester is modified by the view through the view, and then finds the test case that the test demand changes after the test demand change is found, and the modification of the test case will ensure the software requirements of the test case. Effectiveness. How many questions are still not clear now, and it is also a major reason for the test. It is if the test needs are maintained separately, how old is the workload? When there is a change in demand, it is not a reality that the test demand and test case is maintained. If the software requirements are more than 80% of the test demand, it is necessary to increase the maintenance of a test demand? ?? Of course, consider the maintenance of test demand, there is another idea, that is, test priority considerations. But if the maintenance of the test needs is only this function, then you can put it in the software requirements to complete, add two or three fields to solve it.
When the last demand, development, test tripartite talks, one of the problems discussed is that the test work is based on the principle of demand, and the design of test cases is only standard for demand. In fact, I took into account this time, it is also dynamic, and it will constantly supplement and modify during the project process, so the source of test case designs has become broad. In the early days, the test case is designed, but the test case will be supplemented and perfect in the process of developing architectural and detailed design; even after the test version is delivered, the test is executed The test case will still be added and modified during the process. Therefore, the test case is not only related to the needs, but also related to the design document, the product delivered. So now there is a new problem, just how to communicate with development? When the demand changes, the design changes, the test will also be adjusted according to the requirements and design, then the demand can be obtained by REQUSITEPRO, what is the design? If the test can be tracked by the "Demand-> Test Demand -> Test Sample", how can it be managed by the development of a similar approach? From a test perspective, it is very hoped to have a method to associate testing and development to demand, establish a node of communication. There are still many ways to operate, and now I don't think about it, so I hope there is a need for demand, development, testing, and we can try together to try to coordinate the work of the parties.
?????????????????????????????????? Tester: Chen Lei
