The development stage of software testing

- century on one of the leaves of the day, our Super Cutie program ape " Gracie · Hobo "in the supercomputer's big House secret of a most military system development and commissioning, found that the program did not according to their own assumptions to give the expected results, after a hard investigation, found that a moth was clamped in the middle of the relay contacts, This moth is the " moth "that caused a great change in the following industry. The emergence of this BUG Indicates the advent of the software testing tide. in the beautiful "Gracie · Hobo "after the discovery of the first moth, in order to avoid another moth into the computer to make a date, after the formal delivery of the program, the beginning of the program debugging work, which is the predecessor of software testing. This period of software testing is to prove that the program is correct and exists.

1972 The first formal software testing meeting was held at the University of North Carolina. Software testing is officially independent from the moment it is formally done as a job. And for the follow-up development, here is not listed, such as interested friends, you can see another article. A description of the software testing process.

from the development of software testing and trends in recent years, you can see the software testing is to systematize, unified, intelligent direction to find, individual according to the software testing industry understanding (reference other materials), The development process of software testing is summarized into the following five stages: individual hero stage, teamwork stage, process maturity stage, intelligent testing stage, and fifth stage "none".

Personal hero Stage

before the software engineering, the small size, the development & Testers independently complete the software writing and testing work, at this time the tester may be directly with the developer, at this time the main debugging + run test-oriented, manual testing phase, at this time the test process is more chaotic, often is developed to complete a software, to test personnel to test, test to get the software, according to their own understanding and personal experience of the software inspection, and the ultimate goal is to find defects, Therefore, the quality of software testing during this period is generally to see the number of defects found by individuals, but the overall quality of the software is no way to measure.

Team mates

With the development of software engineering and the increase of complexity, the software internal logic is more and more complex, the software code line also refers to the number of increases, this time if there is a programmer part-time software testing, there will be obvious flaws, so this phase began, software testing by professional testers to serve, Testers need stronger thinking skills, sharper insight, deeper industry knowledge, and broader business knowledge. From here, software testing is formally differentiated from the software engineering as a separate industry, and the testing is carried out with various practices.

with the improvement of the system complexity, everyone has no full grasp of the quality of the system, and the defects will certainly exist in the system, so this phase of testing, is mainly to verify that the software did the thing, do not do things that should not be done, to the team with confidence. And with the expansion of the team, testing also set up an independent team, this time, how to face a complex system, to ensure the quality of the system, and become a team problem, and not a person's things, this time, the problem of testing rose to the team, in order to solve the problem, from the software engineering, according to the basic idea of the project In accordance with the industry CMMI standards for division of labor and collaboration, at the same time in order to better save manpower and start using automation, the use of automated regression, and the process of data recording and analysis, try to use the data to evaluate the software system. The vast majority of companies are at this stage.

Full Process control stage of maturity

This stage is the follow-up stage of the team cooperation stage, is the stage of further development of the project engineering, is also the stage of the current phase of the test preface, the phase of software engineering is more explosive, the integration of various third-party components, third-party systems, so that the complexity of the system to improve a step, In the private software also for the clear conditions, but also to join the third party system or software, in this case, the complexity is conceivable, the quality of the requirements, the requirements of the testers higher.

This stage is designed to control the whole process for better control, and according to the characteristics of the test, use the specific test process management specification, using the existing TMMI/TPI system or the subsequent more suitable system for the overall process management and control, trying to pass the process of full management, say all the problems are strangled in the cradle. In order to achieve this, this stage, more professional tools, there are code scanning tools, performance, security testing tools and other tools, testing through the analysis of data collected by the data, through analysis, trying to use the return data of each tool to measure the quality of software, this phase of software quality can really measure it? Not really

Intelligence testing phase

This stage is currently a handful of top companies are trying to the direction of the original test thinking is a big leap, this stage mainly using big data thinking of the software itself, the person itself, the process of multi-dimensional data integration, to achieve real data quantification of a software or product quality, Software quality at this stage is the ability to actually quantify the data.

this stage of data collection and analysis will be a focus, and in order to obtain the corresponding data, need to Team System, process specifications, industry data transparency and other related industry system or management system to carry out matching construction. For example, I use Java, based on the Netty Service Framework for development, the quality of the product is directly related to the quality of the Netty you use, At the same time, the development level of each person in your field development team is directly related to the team's architect level, the team's management model, the Java version used by the team, and what needs to be done in the intelligence testing phase is Netty When developing service components, other teams encounter problems and existing problems, the technical level of personnel to open a lot of data, through these data and team management together to quantify product quality.

In this process, the continuous delivery will become the basis, the comprehensive automation test will be used as a basic test method for the layout, all the testing related work can be completed using tools, this phase of the tester is mainly for the problem analysis, writing test tools or scripts, the results of model optimization.

None - Test kill Test

through the above 4 stages of development, you can see that in the final phase, the test will focus on tool writing, model training, and after that, "testing" the industry?

The final goal of the test is to test and kill the "test", and "test" will live forever!

The development stage of software testing