"Software testing" software defect superficial understanding and white box Test example

In the last lesson, the teacher talked about the analysis of software defects. First of all

Software defects can be divided into:

1. Input/output defects

2. Logic defects

3. Calculation of defects

4. Interface defects

5. Data defects

the production of software defects：

1. Errors caused by negligence (carelessness defect)

2. Do not understand the errors caused (misapprehend defect)

3. Two errors caused by semantic (ambiguity defect)

4. Errors caused by omission (Skip defect)

(Excerpt from Courseware)

The above is a more generalized classification method.

Software defects in our daily life often appear, such as a software of the PC Client interface design is unreasonable, an app will be inexplicably flash back in the process ...

These are software defects and are more visually visible.

All kinds of defects of software can be found and perfected only after the testers are constantly testing and users have been using them many times.

As a result, most software and download sites now have "user feedback/user ratings" to collect bugs or bugs that are not found by software developers, so that they can be further refined in later versions.

In some cases, even if the developer has found a flaw and did not improve the repair, on the one hand may be limited development time can only be enhanced in subsequent releases, or because some defects do not affect the normal use of the software, so can be a small ignore.

PS: Software defects and software vulnerabilities can be considered the same ...? ==

White box test

White box testing is called structural testing, transparent box testing, logic-driven testing, or code-based testing. White box testing is a test case design Method , the box refers to the software being tested, the white box refers to the box is visible, you know what the inside of the box and how it works. The White box method thoroughly understands the internal logic structure of the program and tests all logical paths . The "white Box" method is a poor lift path test. When using this scenario, the tester must examine the internal structure of the program, starting with the logic of the checker and drawing the test data. (excerpt from Baidu Encyclopedia)

The white box contrasts with the black box.

The white box is like a transparent box, the black box is an opaque box.

White box to understand the internal logic structure of the box, and based on this to test the actual situation and the expected consistency;

Black box does not understand the internal structure, so only according to the product specification to determine whether the software is qualified.

I found a white-box test on the Internet chestnut, the article put Chestnut analysis very clear and comprehensive http://www.uml.org.cn/Test/201205301.asp

I have seen it for a long time that ... A simple software also requires a very thorough and rigorous testing process.

"Software testing" software defect superficial understanding and white box Test example