Based on the understanding of software engineering, product quality and testing, summed up the following seven types of test-driven mode.
1. Business / demand-driven testing
Software is always a problem to solve certain types of business users. Business-driven test is from the user's actual business needs, analysis of business objectives, business processes, user roles, business rules, business development and other test subjects,
Determine the test range for these objects test methods and strategies. The adequacy test, is measured in terms of business processes and data; software system can fully meet the business needs, the business problem / demand-driven tests are the most concerned,
Demand-based authentication methods, testing methods based on user scenarios, can be classified as such tests.
2, product quality risk driving test
According to product quality model: internal quality -> External Quality -> use to test the quality, emphasizing lifecycle to eliminate the risk of product quality, starting from the code review, code complexity metrics, etc., internal quality assessment
To expose the quality of the risk, and then gradually extended to external quality system, users evaluate the quality, continuous reveal, product quality feedback major risks. In these tests, the properties of the product quality of the analysis would be more thorough,
Also stressed static tests, including manual code review and design review, use the code static analysis or inspection tool.
3, model-driven testing
Construction abstract model for verification practical problems, such as UML modeling, finite state machines, Petri net, Kripke structure, temporal logic formula available system property (e.g., CTL, LTL) will be described.
Broader understanding, decision tables, cause and effect diagram, Pair-Wise, etc. also belong to a test model. Modeling of large-scale test of complex application system will be a big challenge, with the development and integration of software technology and modeling technology, these problems will gradually be resolved.
However, the model can automatically generate test cases based automation scripting can automate the testing process more thoroughly, and before most people perform limited testing automated testing,
We need to develop and maintain a large number of test scripts, not a small proportion of manual, semi-automatic count up.
4 (System) features a drive test
Many people comes to software testing is functionality testing, performance testing, which more or less reflects the "functional test drive" ideology.
Functional test drive, that is from the system features, (probably not), verified for each function depending on the software functional specifications design specifications, determine the function of operation is normal, and design consistency.
General function will be decomposed into sub-function, sub-function sub-functions, to form a functional point list, a test case for the design and implementation of function point.
5, design-driven testing (DDT)
DDT inspired by TDD, test analysis and design, test drive is designed in advance. DDT has these following features: test more flexible, simpler, eliminate duplication of work, to guide test case test plan (and traditional testing the contrary),
Test cases can be converted into a test code contains the business needs of test scenarios and test, controller test, the test is very useful for development and test teams.
About design-driven test, the topic has been discussed in the works: design-driven testing - allows programmers to test more easily.
6, (a program / code) drive test structure
It is substantially similar: Structured testing, white box. Test driven from the program structure, for structural analysis program, gradually covering various portions of its association procedures, such as those based component test, a test based on API or an interface test;
From the test code structure, comprising a line of code coverage, branch coverage, path substantially covering the like. Full measure of the structure of the driving test would be more objectivity, particularly those based on code coverage analysis, there are a lot of tools to support.
7, statistical / empirical test drive
It can be seen as part of the "experience of software engineering," the recognition of actual measurement data and experience more valuable than various theoretical models. Software testing process by collecting data and experience, statistical analysis, collate, generate empirical models to carry out the test.
Context-driven testing, exploratory testing, defect prevention, error guessing method can be classified as such, although not very strict, but are basically driven from statistical test / experience.