Software testing-what is a bug, software testing bug

Software testing-what is a bug, software testing bug
I. What is a bug?

People who have learned programming have heard of the word bug. but what exactly does a bug mean? System defects? Error? Or a vulnerability? However, if I know something in English, I will say that bug is what insects mean. But how can insects relate to computers?

This is the case. Since the birth of the computer, there has been a computer BUG. The first documented bug was discovered by Grace Hopper, inventor of the compiler, a programmer from the US Navy. He became a general of the US Navy and led the development of the famous computer language Cobol.
September 9, 1945 three o'clock P.M. Lieutenant Harper is leading her group to construct a computer called the "Mark 2. 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 team is working day and night. The IDC is an old building built during the First World War. It was a hot summer with no air conditioning in the room and all the windows were open for heat dissipation.
Suddenly, Mark 2 crashed. The technicians tried a lot of methods and finally found that the No. 70th relay had an error. Harper observed the faulty relay and found a moth lying in the middle, which had been killed by the relay. She was careful to clip the moth out with a video clip and paste it in the "Event Log Book" with transparent glue, and noted "the first instance for discovering bugs ."
Since then, people have called computer errors a bug, and the work of searching for errors is called a debug ).

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

Ii. bug Classification

Although I know what a bug is, what is a bug? What types of bugs are there?

Different classification criteria can divide bugs into different categories. Here, we introduce two methods to classify bugs by severity.

1. Level 5 Classification (commonly used)

Urgent: Fatal Error
Fatal errors are usually caused by the following situations:
(1) important functions in the demand book have not been implemented;
(2) system crashes and crashes, and functions cannot be implemented through other methods;
(3) regular operations may result in illegal program exit, endless loops, communication interruptions or exceptions, loss of data damage or database exceptions, and the functions cannot be implemented through other methods.

Very High: Serious Error
Serious errors usually make the system unstable, insecure, damage data, or produce error results. They are also the main and unavoidable problems in conventional or unconventional operations,
(1) important functions can be basically implemented, but the system is unstable. Operations under some boundary conditions may cause errors such as run-time error, file operation exception, communication exception, data loss or damage;
(2) important functions cannot be implemented according to normal operations, but can be implemented through other methods;
(3) wide coverage of errors, affecting the normal implementation of other important functions;
(4) plaintext display of passwords;
(5) In C/S and B/S modes, some operations on the client may prevent the server from continuing to work normally.

High: general error
The functions of the program are basically normal, but there are some requirements, design or implementation defects; Secondary functions are not normal,
(1) Secondary functions cannot be implemented normally; operation interface errors (including inconsistent column names and definitions in the data window); query errors and data error display; printed content and format errors; the deletion operation was not prompted; the program was interrupted due to incorrect operations; simple input restrictions were not placed on the foreground for control;
(2) performance problems, good or bad when a regular rule is not found; after a period of operation, the system performance or response time will slow down; after a hardware or communication exception recovers, the system cannot automatically continue working normally (too much manual intervention is required );
(3) There are too many blank fields in the database table; constraints such as the database table, business rules, and default value without integrity;

(4) Poor system compatibility, which is prone to errors when working with other support systems. There is no sufficient reason to indicate that it is caused by the support system; or, due to the use of unconventional technologies or third-party components, automated testing tools cannot be used for testing.

(5) poor security, important information, such as Unencrypted Password Storage (including the password in the configuration file), or other security risks;

Medium: minor errors
The program is not visually displayed, does not meet user habits, or has some text errors,
(1) the interface is not standard; there is a text error on the interface; there is no obvious distinction between the input and read-only areas;
(2) The auxiliary description is unclear; the prompt text does not use industry terminology; the input and output are not standard;
(3) The user is not prompted for the long operation (or the message does not disappear after the long operation );
(4) If the function implementation method is not clearly defined in the requirement, but is not implemented as usual, and is not superior to the conventional method; (for example, the first user name must contain numbers or special characters)

Low: suggestions for improvement
Suggestions for improving product quality, including new requirements and improvements to requirements.

2. Seven-level classification Blocker level-interrupt Defect
The client program does not respond and cannot perform the next operation.
Critical Level-Critical Defects

Including: lack of features, client burst pages.
Major level-more serious defects
Including: functional points do not meet the requirements.

Normal Level-Common Defect
Including numeric calculation errors and JavaScript errors.

Minor level-one defect,
Including: interface errors and UI requirements do not match, the printed content, format errors, the program is not robust, the operation did not give a clear prompt.

Trivial level-minor defect,
Including: unclear descriptions, nonstandard display formats, numbers, formats such as date, user progress prompt not provided for long-time operations, industry terminology not used for Prompt window text, enter areas and read-only areas are not clearly distinguished, mandatory items are not prompted, or the prompt is invalid.

Enhancement level-test suggestion, other (non-defect)
Including usability test suggestions from the customer's perspective and potential demands discovered through tests.

Editor's note: here, the editor only introduces the categories of bugs, bug management, and how to analyze the quality of software through bugs, we also need to continue learning in the future testing process. Here, we only hope to learn some bugs through this article. We hope to increase your interest in software testing, manage our own bugs to make our software better.