What is--bug software testing

first, what is a bug

People who have learned programming have heard the word "bug", but what exactly does a bug mean? System defects? error? Or a loophole? But know the point of English will say, the bug is the meaning of insects, but how can insects and computer related?

This is the way things are. From the date of the birth of the computer, there is a computer bug. The first documented bug was found by the American Navy programmer, Grace Hopper, the inventor of the compiler, Sch Har. Harper later became a general of the United States Navy, leading the development of the famous computer language COBOL.
September 9, 1945, three o'clock in the afternoon. Lieutenant Harper is leading her team to construct a computer called the "Mark two". This is not a complete electronic computer, it uses a large number of relays, an electronic mechanical device. The Second World War is not over yet. Harper's group worked night and night. The room was an old building built during World War I. It was a hot summer, the room was not air-conditioned and all the windows were open to heat.
Suddenly, the mark two crashed. The technician tried a lot of ways and finally fixed the 70th relay error. Harper observed the faulty relay and found a moth lying in the middle, which had been killed by the relay. She carefully clipped the moth with the camera, pasted it into the "event book" with cellophane tape and noted "the first example of a bug found." ”
Since then, people have dubbed computer bugs a Bug (bugs), and they have called the search for the wrong job (debug).

The above is the origin of the bug, we also know that the bug is a computer program error, and now it is overextended as a loophole, or a program is not perfect place.

second, the classification of the bug

Although know what is a bug, but what kind of situation is bug,bug divided into what kind of?

Different classification criteria, the bug can be divided into different categories, here, two kinds of the severity of the bug to classify the method

1, five class classification (common)

              Urgent: Fatal error
fatal errors usually have the following conditions:
(1) The important function of the demand book is not realized;
(2) causes the system to crash, freezes, and cannot realize the function through other methods;
(3) The normal operation causes the program illegal exit, the dead cycle, the communication interruption or the anomaly, the data destruction loss or the database exception, and cannot realize the work through other methodscan.

              Very High: Critical Error
A critical error usually causes the system to be unstable, unsafe, or destroys data, or produces erroneous results, and is an unavoidable major problem in regular or unconventional operations.
(1) Important functions can be achieved basically, but the system is unstable, some boundary conditions operation can cause run-time error, file operation exception, communicationdata loss or destruction, and other errors;
(2) Important functions can not be implemented according to normal operation, but can be achieved by other methods;
(3) A wide range of errors, affecting the normal implementation of other important functions;
(4) The password is displayed in clear text;
(5) c/S, b/s mode, the use of some client operations can cause the service side can not continue to work normally.

              High : General error
function of the program is basically normal, but there are some requirements, design or implementation of the defect; Minor functions are not functioning properly,
(1) minor function can not be realized normally;operator interface error (including column name definition, inconsistent meaning) in the data window;query error, data error display;print content, format error;The delete operation is not prompted;forcing the program to break due to faulty operation;the simple input limit is not placed in the foreground to control;
(2) performance issues, not finding the regular time is good and bad;after a period of time running, the system performance or response time will be slow;after the hardware or communication abnormal recovery, the system will not automatically continue to work normally (requires too much manual intervention);
(3) There are too many empty fields in the database table;the database table, business rules, default values are not added to the integrity of the constraint conditions;

(4) Poor system compatibility, error-prone when working with other support systems, and not adequately justified by support systems, or due to the use of unconventional technologies or third-party components that cannot be tested using automated test tools.     

(5) poor security, important information, such as the password is not encrypted storage (including the password in the configuration file), or other security problems;

Medium: Minor errors
The program in some display, do not conform to user habits, or some of the text errors,
(1) interface is not standard;there is a text error in the interface;There is no obvious distinguishing mark between the input area and the read-only region;
(2) The description of the auxiliary description is unclear;Prompt window text does not use industry terminology;input and output is not standard;
(3) long operation did not give the user prompt (or long operation after the end of the prompt did not disappear);
(4)in the functional implementation of the way if the requirements are not clearly defined, but not in accordance with the conventional implementation, and is not superior to the conventional way;user name first digit or special character)

Low : Suggestions for improvement
Recommendations to improve product quality, including new requirements and improvements to requirements.

Classification 2, level seven Blocker level-interrupt defect
The client program is unresponsive and cannot perform the next operation.
Critical Level – critical defect

include: missing function points, client pop page.
Major level-more severe defects
include: feature points do not meet demand.

Normal level-common defects
includes: numeric calculation error,javascript error.

Minor level-once to be defective ,
include: interface error and UI requirements do not match, print content, format error, program is not robust, the operation did not give a clear hint.

Trivial level-minor defects ,
include: Description of the auxiliary description is unclear, display format is not standardized, numbers, dates and other formats, Long-term operation did not give the user progress tips, Prompt window text does not use industry terminology, There is no marked distinction between the input area and the read-only area, must lose no hint, or hint is not canonical.

Enhancement Level-test recommendations, other (non-defective)
includes: test recommendations for ease of use at the customer's perspective, and potential requirements that are mined through testing.

Small series of words: In this, the small part is simply introduced what is the bug, and some of the classification of the bug, as to how the bug is managed, how to analyze the quality of the software through the bug, but also need us to continue to study in the future test process, here just hope through the study of this article, a simple understanding of some bug knowledge , mainly want to increase the interest in software testing, management of their own bugs, so that our software to do better.

What is--bug software testing