Software testing, what unexpected things? [Music] stroke TestPRO

First, the cause of defects of software testing

Most cognitive testers, the reasons for testing software defects is to develop a code problems, but through research, summarize, analyze, surprising that we found that most software defects are not generated because of a programming error of. Numerous studies from small programs to large projects come to a unanimous conclusion: the root cause of software defects that requirements specifications, because the proportion of software defects as shown below:

Second, the test coverage does not meet the requirements, excessive residual defects

Lack of test coverage, not just test design is not enough, there are a number of factors, as follows:

1. Test design is wrong
2. Testing insufficient resources
3. The lack of test management
4. Demand Management is defective
5. Review is not enough
6. Configuration management is not strict

Three, ISO / IEC25010 Product Quality Model

ISO in March 2011 issued ISO / IEC25010 software quality evaluation criteria, which describes two models: the use of quality models and product quality model, quality characteristics of the product model are as follows:

1. Function Applicability: functional integrity, functional correctness, functional adequacy
2. Compatibility: time characteristics, resource utilization, capacity
3. Ease of use: suitability, variable capricious, easy to learn, easy operability, user error defense, beautiful user interface, accessibility
4. Reliability: maturity, availability, fault tolerance, easy recovery
5. Security: confidentiality, integrity, non-repudiation, Accountability, authenticity
6. Maintainability: modularity, reusability, easy to analyze, easy modifiability, testability
7. Portability: applicability, easy to install, easy replacement of

Fourth, the history of the development of software testing

So far, the development of software testing experienced a total of five important periods:

1. Before 1957 - based debugging: developers a needs analysis to bear all the work, design, development, testing, and so on.
2. 1957 to 1978 - mainly to prove: Ensure that the program solves the problem it solved
3. 1979 to 1982 - the main damage: to find errors and execution of the program process, not only to prove that the software did the right thing, but also to ensure that it did not do should not do, which makes testing more comprehensive and more easy to find problems.
4. 1983 to 1987 - Evaluation based: Software Test Engineering rapid development in this period, the emergence of test managers and test analysts and other positions
5. 1988 - present - prevention: one of the current mainstream software testing ideas.

Welcome to add V core: lebotest, receive software testing spree, boutique-end version of the open class video courses (152G), covering functionality, performance, automation, interface, job interview, resume and so on.