Software testing process continues to improve
Author: qz
1. introduction
With the rapid development of software technology, the quality of software is increasingly emphasized. The test is an important means of ensuring software quality. According to the IEEE / ANSI standard, the software test is defined as: "The process of executing the code using the combination of the input and status of the error selected." This makes it very clearly proposed that software testing is to find errors, and test whether to meet demand. Software Tests have a very prominent important point in the software life cycle, which is an important means of ensuring software quality. According to the statistics of Boehm, in the total cost of software development, it takes 40% to 50% to 50%. The purpose of software testing is to discover the errors in software as much as possible before the software is put into productive, to improve software quality. Modern software tests are not only finished in software development, but to penetrate the testing of software development, and improve automation software test means to improve test efficiency.
Some projects' hosts believe that all the development phases prior to the test were completed as soon as possible (actual and not completed), start testing as soon as possible to achieve fast and high quality (because there seems to have a longer time available for test). The actual effect will be the "desire speed of the future". From common sense, you can know that the development time will continue to expand the income introduced in the previous stage, and it can only be a more large amount of error that takes time consuming. Therefore, the results of correctly analyzing and utilizing tests, we can improve software process very efficiently.
2. Improve test process strategy
2.1. Double effects, continuous improvement
The company's management and quality control team usually performs improvement in software, and writes a series of corporate standards and norms. After a series of review, training, then let developers will perform. However, in the implementation process, the resistance is often encountered from the developer. In addition to the intense development, they often complain how many other work, such as the writing of a certain standard document; In line with the actual situation of the company, the standard is too high and cannot be reached. This kind of practice, the fees are not good, everyone's opinions are relatively large, the standard is relatively perfect, and it is necessary to recognize the surface when reviewing, and the norms have spent a lot of energy, for the normative The review wasted to have a lot of time, and it was difficult to implement it. This way is certainly effective. This is a relatively low efficiency.
Typically, there will be another practice: reduce requirements, temporarily abandon various standards and norms, using a simple and easy strategy, namely the quality control team to find developers, project managers let them find questions: What do you have? Disadvantages? How will you improve? After the developer, the project management personnel tells the improvement measures, let them make sure it can do. In this approach, it is not necessary to manage too much energy to make standard development, improvement, these tasks are made by the developers, and the management personnel have played the role of supervision, as long as the developers themselves It's okay to say it. However, we have made an attempt, if you use only a standard from the developer's perspective, everyone's habits, developers often tend to develop their own program habits to develop their needs, which is relatively large. It is difficult to form a unified, formal document architecture. Moreover, developers often use this and have sufficient flexibility to themselves. It is often a different solution that has been developed, which will cause non-uniform programming style. Since it is a standard, there is always a certain mandatory, and if it comes from bottom to the developer, a bigger problem may occur during the implementation of the developer. In summary, we have taken a compromise, that is, according to the requirements of the developer, first develop a development specification and submit it to the developer or project management review. Allows them to make their own opinions, if the comments are reasonable, you can modify the norms. For example, it is assumed that there is a programming specification in the original document system itself, but when actually developed, some of the rules are not very practical, so the company is based on the development tools and languages used in each project group. Different, develop different programming standards, and these programming standards have funded substantially from developers, but they are reviewed by the company's managers and quality control departments.
The advantage of this approach is that you can take the initiative to improve the quality awareness of all the staff of the company. For senior management, all specifications have been approved by them, they play a supervision;
For developers, many rules are what they put forward, they will consciously abide by. Such a two-pronged, double-effect, not only greatly improve the quality of the software, but it doesn't have to push all the responsibilities of the mistake to the test personnel, but to prevent mistakes in advance, reduce the occurrence of potential hazards, reduce the responsibility of the test staff, and cultivate the developer's good Program habits. 2. Pay attention to the document, requires the skill software document, also known as document, usually refers to some recorded data and data media, which has fixed forms, can be read by people and computer. It works with the computer program constitutes a computer software that can complete a specific function (someone is also part of the source program as part of the document). Hardware products and product information are shaped throughout the production process, software production is very different, the document itself is software products. Software without documents, not called software, can't talk about software products. The preparation of software documents has a highlighted status and quite workload in software development. High efficiency, high-quality development, distribution, management and maintenance documents have important significance for transfer, change, correction, expansion, and use documents, which has important significance to give full play to software products.
However, in actual work, there are many problems in the preparation and use, and they need to be resolved. Software developers are more common in the phenomenon that is not interested in the compilation document. From the user, they often complain: the price of the document is too high, the document is not complete enough, the document is written, the document is old is difficult to use.
As we all know, the writing of documents is a very headache for developers. The development cycle is very tight, but also written documents in accordance with the required format. Therefore, this is often the incomplete document, or the document is too simple to make the test personnel can't understand. Even, sometimes the project demand has been updated, and the content of the document is still constant. Think about it, if you don't understand the document, the tester will definitely ask the corresponding developers, then developers must spend time to explain. This will cause very inconvenience if the testers and developers are in different work.
During the software development, the document is very important, and the workload of writing documents is also quite large. However, as long as you master the skill, you can still alleviate this a headache problem. First, we must stand at this issue at the perspective of others. I am going to do development. Of course, I must be very clear about the process and function of the program, but others are not necessarily, including testers. So don't rejection to write a document, first try your way. Again, explain the basic function, to focus on highlighting. That is to say, use a simple language to introduce the function. For the key part of it, it is necessary to stand out. It is not very detailed in the language, but the perspective of understanding is detailed. In order to allow testers to quickly understand the functionality of the module, the best way is: Functional flow charts, data flow charts and examples. Especially for those who have considerable logic, the data flow charts and examples are very good ways, which can not only help indicate the flow of data, but also help testers understand the type of test case, as well as the result form. The flowcharts and examples of making a concise and concise work is a task force, saving time and effort. For testers, it is an important document for understanding procedures logic and functionality. In the later stage of the development process, you can continue to refine and improve your document.
2.2. Text programming, advance test
In order to improve the quality of the software, the company can try to implement first-test team programming, which also runs through quality awareness. Because two developers of the team are turned by turning, whenevering documents, mutual supervision, and testing each other. This not only has energy to write the document well, but also can test in advance, supervise each other to develop good program habits. Finally improve work efficiency. After the knuckle is programmed, the unit module first tests the test personnel equipped by the project team first test, and the personnel of the Quality Control Department will perform in accordance with the project plan to check whether the project is normal according to the scheduled plan, and the relevant document is written and integrated test.
2.3. Good at summary, improve efficiency
Summary is a very good way to learn, it can save energy, saving time to achieve a half-time effect. During the development of the project, the important technical problems that can be encountered will be recorded in time and record the solutions to the reference of other related personnel. Similarly, during the test, the tester should sum up the discovered errors and classify, indicate that it is often easily error-in, and submits the project manager. After the review, it has set a unified standard and provide to developers, so You can avoid errors in advance, avoid repeating errors and repeat tests, and improve test efficiency. Not only that, the summary reports after the project will be the post-maintenance or two-time valuable reference for the project.
3. in conclusion
