Shulou(Shulou.com)06/03 Report--

Review, testing, evaluation-from the testing process to see the software testing requirements, is the system's continuous and stable ability to meet customer requirements. "when do you get involved in the test?" Testers have been thinking about the question of what is the best time for software testing to intervene. "testing as early as possible", both from the test theory and the testers themselves, will think so. The risk moves forward, find the problem as early as possible, correct the problem, reduce the cost of correcting the problem, and the principle of economy. Software development is a creative activity, while software testing is a protective activity, which determines that software testing activities will attract everyone's attention only when there are major problems. So, how early is it as early as possible, starting when the software is intentional? Start as early as possible, so what do you want to do to start testing early? In what way? To what end? First of all, let's take a look at the software development process and the software testing process, which is typical of the V model.

Starting with the requirements, there will be a strict Vendor V process that can be used as a testing process. The executive will be involved in various positions and roles of system development.

During the implementation process, there will be unit tests and interface tests. Executed by the developer.

After programming, there will be functional testing, integration testing, and system testing, followed by repeated regression testing. It is performed by professional testers.

After the system is delivered, there will be acceptance testing. It is carried out by internal and external acceptance personnel, or by a third party.

From the perspective of the whole process, the software testing process will be divided into three categories: review-- > test-- > review.

Review: corresponding to the test plan phase, including the whole process before test execution.

From the whole process of market research, pre-sales support, requirement acquisition, requirements analysis, system planning and system implementation, software testing is in a state of preparation. At this stage, a large number of software testing is doing review work, constantly "review", find the problems and loopholes in the system, so that the system has the premise of testability. At the same time, testers need to pass the audit, complete the understanding of the software system, decompose the system requirements into test requirements, estimate the test workload, complete the test plan, and confirm the test strategy. The X model is recommended here, which emphasizes that the testing and development work are carried out in parallel, and the preparatory work before the test execution is completed.

Test: the execution process of system test.

Once the system is formed and meets the test standard, it can be released for related testing. The X model is recommended here. We need fully integrated system testing, but we still need to implement the principle of testing as soon as possible. Some module functions outside the core business of the system are tested in advance to ensure the focus of different stages and different types of testing. The concept of continuous integration is mentioned here, which is also an agile point of view. The less integration, the earlier testing, the non-mainstream problems are solved in advance, so that the problem location takes less time and less investment. First, ensure the stability and reliability of each module, followed by the stability and reliability of the system interface, and finally the stability and reliability of the whole system. Each stage will have its own testing focus, each stage will have its own testing workflow, through the continuous adjustment of working methods and methods to achieve the best testing results.

Comment: how is the system testing effect, whether the system meets the requirements, the software testing process and results are quantitatively analyzed, so as to quantitatively evaluate the system.

There are two kinds of evaluation here: one is internal evaluation, and the other is external evaluation, also known as third-party evaluation. No matter which kind of "evaluation", we need to adopt a prudent attitude, from the software process to the system itself need to give a clear and effective "evaluation" results. The comments here, whether internal or external, are actually the confirmation of the testing work, thus the quantitative analysis of the quality of the system. Therefore, it is recommended to adopt the form of "third party". The internal organization needs to be composed of relevant project leaders, relevant participants, testers and quality assurance personnel to ensure that all aspects of system development and system implementation will be involved and evaluated. With the help of the third party, the external organization forms a contrast to the original internal test results through the strict testing and evaluation of the third party, so as to effectively evaluate the quality of the system. It should be pointed out here that a good software development process may not guarantee the correctness of the system, but a chaotic software development process will not have a good system implementation. Risks exist from time to time, and there will be problems in any system, which is also an important principle of software testing.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.