The China Software Industry Association will hold the "Software Testing and Industrial Development Seminar" on August 22. Zheng Renjie and Chen honggang delivered their unique insights before the Conference.
"If you put software testing completely at the final stage, you miss the time to discover serious problems in Architecture Design and business logic design. By then, it will be inconvenient to fix these defects, because the defects have been spread to the system, it is difficult to find and fix such errors. The cost is higher, because errors have spread!" Professor Zheng Renjie of Tsinghua University pointed out.
Professor Zheng Renjie said: "My first access to software testing and software outsourcing at Tsinghua University was in the early 1980s S. the specific content of the project was a general software testing tool. It is a FORTRAN-based Dynamic Testing Tool ." Professor Zheng, with a strong sense of responsibility, undertook the project with three other experts. The project was successfully accepted. on the front page of Japanese "read and sell news", it was highly regarded as "fujitsu imported high-quality software from Tsinghua University in China ". This should be an attempt by early Chinese IT workers to outsource software in terms of software testing technology. This newspaper has also become the "household" of Professor Zheng Renjie ".
Software testing is Software Quality Assurance
In the broad sense, software testing and testing includes testing the entire process of software production, including testing the user requirements and outline design, such as whether the product meets the user requirements and the user's usage habits; not only do some people think that testing starts from the code stage. Therefore, the demand indicators and so on need to be tested to ensure that there is a system to ensure the product quality in all aspects, commonly known as "one step three back ". Just as a manufacturing enterprise has a specialized quality inspection department, it is necessary to use various means and perform inspections according to specifications in various processes and stages. These are the processes of discovering problems, these measures ensure that unqualified products are downgraded or cannot be transferred to the next process.
Professor Zheng Renjie said: "We also found that whether a product is successful in the market is related to the initial market positioning and user demand analysis of the product. Any problems in any link will seriously damage the overall product quality. Therefore, when talking about software testing, we should have a higher understanding of this issue. We are discussing how to control and ensure product quality throughout the product development cycle ."
In the product development process, relevant inspection and control measures (QC) should be adopted in every step. This is a routine work of software testing. The inspection manager needs to answer the following questions: Are the testing methods used by software testers adequate, the steps reasonable, the necessary and efficient, and whether the inspection personnel technical standards are met, the quality manager should eventually be responsible to the top management of the enterprise, which ensures that the testing methods of the enterprise are fully necessary. This is what we often say about quality assurance (QA ).
Differences between third-party evaluation and Software Testing
We can see that software testing is a quality control and assurance system within the enterprise, rather than a third-party software evaluation.
The evaluation is a confirmation of the functions and performance of software products by a fair organization. The purpose of testing to evaluate the functions of the software is not to detect and locate internal problems of the software and to test the stress of the software. Professor Zheng Renjie believes that we cannot pin the quality control of software enterprises on a review of finished products.
Software testing is designed to test errors in the development process. It may continue until users buy a trial or buy software. After users discover problems during use, they will report to the developers, these are all in the scope of software testing, so we can see the difference between them and the evaluation.
V model for Software Testing
According to the V model shown in the figure, two methods are generally used for testing:
First, after the code is complete, the unit is tested, and then integrated testing and acceptance testing are carried out, which is equivalent to testing parts, parts, and the entire machine separately.
The second method is to detect each step in the outline design, detailed design, and encoding. Discover and eliminate problems as soon as possible.
If problems cannot be identified in a timely manner, these hidden problems will also be taken to the next process. The correct design is encoded, and the wrong design is also encoded.
Professor Zheng Renjie gave developers a suggestion that they should consider testing in every step of their work. Do not think that, in the end, some people will test it, and some people will correct it. In an image, it would be too late to go to the hospital after the disease is serious. Constantly aware of possible problems and promptly discover them. Developers must have this idea from beginning to end to become mature software engineers.
At present, as a computer undergraduate student, there may be no software testing courses, which may easily lead to practitioners not paying enough attention to software testing problems or lack sufficient background knowledge. However, due to the rapid development of IT technology, the school curriculum cannot be expected to provide students with labor skills for five years after graduation. In terms of software testing and quality control, we also need the attention of various parties, especially the business community.
CMM and ISO
Software quality standards are more complex than other products. The quantification of standards, the acquisition of test results, and the scope of standard values all require the joint efforts of the industry to improve software quality standards. Software Development V MODEL
However, quantification of software product quality standards is a world-wide problem. The standards are not comprehensive and difficult to quantify. However, it does not compromise the practical application value of this application discipline and the enthusiasm of enterprises to invest money and energy in solving this problem. To solve this problem, we can use another solution: to solve this problem in the process, enterprises must meet various quantitative quality assurance measures in the process of product development, ensure that the enterprise development process complies with standards and has the ability to ensure product quality (the Enterprise is mature, the rationality of the process ensures product quality ).
Therefore, we have ISO9000, CMM, and so on to ensure that the interests of consumers are protected from the process perspective.
|
