Shulou(Shulou.com)06/01 Report--

Bug is an inevitable problem for programmers, so to speak, most of the Bug will be detected during the test phase and continue to be rebuilt. But there are also some Bug that are very tenacious and not easy to detect. Some of them will bring serious consequences, but some Bug are irrelevant, on the contrary, they can make the public laugh!

Before we start the magical and funny bug complaint conference, let's talk about the hierarchy of bug in detail.

Fatal bug: problems that hinder development or testing; cause system crashes, crashes, dead loops, resulting in loss of database data, incorrect connection to the database, loss of major functions, lack of basic modules, etc.

The modification priority is the highest, and the problem at this level needs to be modified immediately.

1. Code error

two。 System crash

3. Causes the program to restart, crash or exit illegally

4. Important level menu functions cannot be used

5. Endless cycle

6. Data loss or exception

7. Data communication error

8. Hardware failure, system suspension.

Serious bug: loss of main functions of the system, database saving and calling errors, loss of user data, testing that the first-level function menu can not be used but does not affect other functions. The functional design is seriously inconsistent with the requirements, the module can not be started or called, program restart, automatic exit, conflict of calls between related programs, security problems, stability and so on.

The priority of modification is high, which needs to be modified by programmers as soon as possible.

1. Lack of function required by the user

two。 Statistical error in data calculation

3. Business process error

4. Program interface error

5. The program is interrupted due to an error operation.

6. The system can be executed, but the operation function cannot be executed (including instructions)

7. Some items (options) of function items are invalid (non-fatal to the system)

8. The implementation of the function is incomplete, for example, data association is not considered when deleting.

9. The realization of the function is incorrect, such as in the interface of the system, some controls that can accept input have no effect after clicking, and the operation of the database can not be realized correctly.

Recommendation: (this level problem occurs without affecting other functional tests.) you can continue testing this version.

General bug: the function is not fully realized but does not affect the use, the function menu has defects but will not affect the stability of the system.

The priority of modification is medium, which needs to be modified by programmers.

1. Data length is inconsistent

two。 Incorrect content or format

3. Long operation time

4. Long query time

5. Slow response time

6. Functional suggestion

7. The prompt information is not accurate.

8. Error in the operation interface (including whether the definition and meaning of column names in the data window are consistent)

9. Simple input restrictions are not put in the foreground for control

10. Although correctness is not affected, system performance and response time are affected.

11. Unable to locate the focus or incorrect positioning, affecting the implementation of the function

12. The function of adding, deleting and modifying cannot be realized in this interface, but it can be supplemented in another interface.

13. Too many fields in the database table.

Suggestion: (there are most of this problem in the actual test, reasonable arrangement to solve the BUG, resolution relationship between the degree of optimization)

Low-level bug: interface, performance defects, suggested problems, do not affect the implementation of operational functions, solutions that can optimize performance, and so on.

The priority of modification is low, and this level requires programmers to modify it or not.

1. Typos

two。 Interface is not standard

3. The auxiliary description is not clear.

4. Page display overlap

5. Hide what should not be displayed.

6. The description is not clear

7. Input and output is not standard

8. The user is not prompted for a long operation.

9. Prompt window text does not use industry terminology

10. The text is not arranged neatly

11. Incorrect cursor position

twelve。 There is no obvious distinction between the input area and the read-only area.

13. A distinction should be made between required and non-required items.

14. Invalid scroll bar

15. Keyboard support is not good, for example, enter newline is not supported in fields that can enter multiple lines.

16. The interface can not be refreshed in time, which affects the realization of the function.

17. The user experience is not good.

Suggestion: (this kind of problem is more in the early stage of the test, and the priority is lower; it is less in the later stage of the test, so it should be dealt with in time.)

Software test developers will encounter a variety of Bug during their work. After learning about the hierarchy of bug, let's talk about the unexpected bug you have encountered.

@ Xiao Bo

When I think of the bug I met a few days ago, it doesn't count very well, it's just funny. A text box, enter about, banner and other words, submit and then look at the words become aout, anner, find development, development response: block the sensitive letter b.

@ Xiaowei

For those who do the underlying test, they have encountered the log rollback configuration to write rotate as rotare, and then the log is not rolled back successfully. soon the disk is full and the machine hangs.

@ Xiaofeng

It is not as good as our development. When we check the flight information that the departure airport is Shenzhen, he returns a field in which the departure airport is Shenzhen, and I don't give him any other information. I asked him, and he said, "just check the departure airport. I'll give you the departure airport. What's the problem?" You go to Baidu to enter Liu Dehua, Baidu returns to you three words: "Liu Dehua", there is nothing wrong with it, I think this logic is very powerful X.

@ Little soft

It takes a minute to test a bug, and it takes only 28 seconds for some front-end developers to point bug back, even if you don't test yourself, and give you two bug instead.

@ small pieces

Drag the upper and lower modules to sort, the results are not saved in the order of dragging, the programmer confidently said to me: you have to quit first, and then re-enter, sorting is correct.

@ Quiz

I met bug a while ago. System superusers can downgrade themselves. After the downgrade, you can no longer be promoted to superuser. As a solution, only the server-side system software can be reinstalled.

@ try it out

It was the annual meeting some time ago. I believe everyone has received the New year goods issued by the company, and some large companies or enterprises will also hold some lucky draw activities. However, it would be embarrassing to have bug in the lottery. Coincidentally, I came across that every programmer would be very embarrassed to see the four big words "Null". The word "Null" means "empty" and is a common word in the code. However, I feel that the boss of the company who draws a lottery with the code has a big heart. If someone fiddles with the code, isn't that what you want?

In a word, sum up today's complaint meeting: bug tens of thousands of articles, careful first, coding is not standard, test two lines of tears!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.