This is an old post, sent to this, please discuss it together. Recently, I have recently seen a post on the development and testing strategy of the test plan, and some friends asked some questions about how to develop test plans and how to determine the time of the plan, I'm foolish, I'm doing a lot of testers for some The basic work is still not very familiar, so this article, I hope I can help everyone. The target's goal is to find defects as early as possible and make sure it is really solved. A good test plan can better help testers grasp their work. First of all, a concept-test plan that often sees some testers understand the wrong mistake. The test plan here, the plan is to be used as a verb rather than the noun, or should be called "plan test" is more appropriate, focusing on the plan for the entire test project, and the "test plan" is only used to record the final result. Documentation. It is said that it is a "plan test work" instead of "preparation test plan". I have also seen some people responsible for developing test programs. Find a test plan template or sample through various channels, spend a few hours or even shorter time copy, cut, paste, completed with extremely high efficiency. A "test plan" and take this with this. Ah, BOSS once thought that such people were disastrous for his company. Plan testing is usually the first task that starts testing work. Generally speaking, the team should have rich testing experience, the test manager, the supervisor, not recommended to test the newcomer to take over - because this is like a woman research Philosophy, both the unfortunateness of philosophy, is also a misfortune of a woman - different roles or peace of mind. However, novices can help organize some of the information needed for some plan tests, or you can know those information from the plan test work, and look forward to the test problem from the global perspective. In addition, the test novice can also learn to develop their own test tasks and plan their own work by helping to organize materials, is also a good exercise! I don't know if someone will look at the above content. I will say: I have said so much nonsense, what is the use of the test plan! ? The final purpose of the plan test is to communicate. Hi, is it very different from you? Does anyone think the plan test is to make your own work? Well, you can have this role. However, in the actual development process, multiple teams are coordinated to complete the work, and the test work is used as a ring in this process. During the process of planning test, testers should clearly specify the scope, methods, resources and progress of test activities, and clearly being tested, the characteristics of test, the person in charge of each task, and the risk associated with testing. The definition of these content is to communicate with the understanding of the task to be executed, and finally confirmed the development unit (or plus the departmental department, etc.), and finally determined. This is my first "long story", see here, if you are interested, spend some time to study the following content, if you are very familiar with the following questions, then I have experienced some practical work Will help you. Recently, I saw a post of Seanhe friends on the Test Times Forum, which lists a list of contents of the test plan. It can be said that the test work needs to be considered, very comprehensive, but there is no The project makes a specific explanation.
And I prefer to use a list of questions to work - this is also a working method from "Database Design" book, the original author of this book is Ryan K.Stephens, Chinese version by Machinery Industry Press 2001 Annual publication, it is recommended that even friends who are not interested in the database can also refer to some of these working methods and ideas. For information on the Chinese version of this book, please refer to the following URL http://www.china-pub.com/computers/ COMMON / INFO.ASP? ID = 3435. Below is some of the problems that I have considered in the development of test plans and some other experiences. Of course, because the plan itself should be a dynamic process, it is found that the following problems do not apply to the specific operation, it can be increased, reduced or other adjustments. However, there is a little, the list of questions under the final determination should be discussed in the project group. Different departments communicate with each other, eventually agree. In addition, it is limited to my own experience, and these issues cannot be guaranteed to be suitable for all items, but only some common needs, many specific work issues, everyone still wants "everything from actual start", Think more. 1. What is the purpose of the plan test process? I have always advised the way to make what you want, and then you will make what you want to do for this goal. Applicable as planned tests. If you can't find the reason for the plan test, then don't be too strong in this. For this issue, my point of view has been described above - for communication. In order to better carry out the development, the Development Department, Customer Support, Marketing Department, management know what you have to do, and you still need more to fight for their recognition and support. 2. What is the product and version you want to test? Many friends will say: Our project management is now chaotic, and there is a new version of the whole test process, and the test work is too passive. OH, if this is true, then consider introducing a perfect version management method. Because I have been engaged in some major projects, I have already eaten the hardship for the version iteration, and it is disorderly iteration. If you are unable to concentrate on the testor and developers to a version, then the emotions and confidence will gradually fall. 3. What is the quality goal of the product? In a project, the BOSS, the Marketing Department, the customer support department is different from developers, testers are different for quality, so it may argue. But no matter what to say, there must be a clear quality request. Since everyone has their own request, then give a accurate definition for their requirements: request the response speed, it is to be clearly how many business response per second, or What else; if it is stable, it is necessary to clearly run N hours without dead or in some environment. It can work properly; or ask the system to do a level bug when using it? Ultimately, the test target must be explicitly adopted, so as not to determine the time of the test end and the program release. 4. What resources are needed? First of all, it is a problem. How many people do you need to test? Are there of those roles? What is the responsibility of these roles? Who is responsible for what work? What kind of question should I look for? It is recommended to consider the exchange of communication between mutuals. If only a few people may vote for verbal ways in a big house, there are too many testers, and the scope involved is relatively wide. Some tools are convenient. Where is the software you need to download, where is the test tool? How to solve the hardware needed? Where is the document? And the above questions should be used to contact, considering it.
If some resources are depends on other teams, they should also clear the responsibilities and tasks of these teams. 5. What are the terms or nouns need to be defined? It is also a very important place here. When some concepts in the project are blurred and everyone has their own understanding, but they may have some effects on the development of work when they have never communicated these different understandings. The most common question is that you want to go to you to west ^ _ ^ 6. What need to test? What don't you need to test? Here, if possible, try to explain the reasons for testing and no testing. Usually my approach is to test the part as a test demand, and no test is required as a test risk. 7. How to define a test phase? During the plan test, the specific meaning, work content, and final delivery of the workpiece should be clarified. For the definition test phase, ignorance is more in order to form the coherence of testing and help you better accurate test workload. The two concepts associated with this are entry and exit rules. Each clearly defined stage should have a clear entry rule and exit rule, absolutely to explain the rules of a phase, and the rules of the next phase of the work and enter the next stage. If these two rules are missing, you will be able to find that the original definition is lost, and the test work is no longer coherent, but it has become a lot of uncomfortable single work, and the test work has become far. No one says that you can end. 8. How do I define test strategies? This is the most important part of the plan test process, absolutely do not want to be completed by the newcomers. Usually I am responsible for defining the test strategy of the system test phase. There are several questions that consider: a. Prepare those test types? Different software involved test types may differ. For these specific selections, it is recommended to refer to the contents in the RUP. B. Different test types are ready to use different test methods and technologies? When do these methods and techniques are prepared? How to adopt, for example, is it ready to use a black box test? Do you need to consider white box testing? Do you want to consider using test tools? Those manual testing? Those automated tests? and many more. C. Some factors will affect your test strategy? Will it lead to changes in strategies or impact policies? 9. How is the test progress? Hey, on this issue, I can plant my head. It must be understood that the test work is closely related to other teams - such as the development department - work is interdependent. At the beginning, I didn't understand this problem, it was too ideal, and the progress made could not be completed, dragging and dragging - of course, it is not held responsibility. It is recommended that you must clarify those factors before formulating progress, will have a positive impact on your progress, and those factors will have a positive impact, and if these factors have changed what effects. For factors as a necessary condition, consider the progress in the progress of the progress, and the relative date is used instead of the absolute date when determining the progress and end dates. For example, XXX work begins at the end of the XXX department XXXX and submits XXXX Dongdong. It is expected to use the current task. 10. Do you need to specify the risk? In actual work, the test work will be affected and restricted by many factors, and sometimes even restrict the completion of the test work, such as the deadline. I have opened a "Time-limited Test Project" on 51cmm. The result of the discussion is that in this case, it can only grasp the key business, the most basic quality requirements, other parts, as a risk treatment. Regarding this problem, it is a great responsibility for testers. It must be clearly pointed out in the planned test powder line and discussed with other teams to achieve consistent opinions.
