For example: the column name is inconsistent with the content under the column name

Completely unable to meet product requirements, basic functions are incompletely implemented or completely unavailable, blocking the testing process and progress (core functional process)

1. The main functions are not implemented or the functions are missing.

2. The business process is incorrect

3. Data is not reported and user data is lost

4. Ultra vires

5. System crashes, freezes, and endless loops caused by routine operations

6. Security issues causing data leakage

7. Involving money, such as payments and balances

8. Serious UI problem: core page

9.Safety issues

10. Compatibility issues lead to major functional abnormalities (such as buttons being blocked and unable to enter the next step)

11. Intolerable lagging and slow page loading (more than 30 seconds)

12. Other errors that prevent testing

urgent

The product function implementation does not meet the requirements and does not achieve the expected results, but it does not block the test progress (non-core functional process, does not affect other functions)

1. Minor functions are not implemented or are missing.

2. The error spreads widely and affects the normal implementation of other important functions.

3. System crashes, freezes, and endless loops caused by unconventional operations (unconventional operations: operations that users will not perform when using the system)

4. The page is not implemented according to U, and the user experience is poor

5. Page jump error (such as clicking to create jump details)

6. The page loads slowly and is obviously stuck (more than 15s)

7. Query sorting is not implemented

8. System compatibility issues lead to minor functional abnormalities (for example: abnormal page UI display, but does not affect the use of functions)

9. Lack of handling of system exceptions

10. Incorrect data type and boundary conditions (for example: only enter numeric values, but other characters can be entered, and no error is reported)

11. Cursor jumps and positioning errors (such as: selecting the red envelope balance, cursor positioning on the red envelope fission)

12.Interface error

high

Relatively minor functional, UI or interaction issues can be tested by bypassing such issues

1. Compatibility issues with non-mainstream systems that account for a low proportion

2. Copywriting errors (such as toast prompts)

3. Page loading is slow (more than 8s)

4. Probabilistic defects

5. Font style and size are not uniform

6. The text is not arranged neatly

7. The copy is too long and is blocked, without line breaks or omissions.

8. Functional description is not given or is unclearly described

9. Deletion without secondary confirmation

10. Unconventional operations, such as problems that can only be reproduced after multi-step compound operations (users generally do not operate this way)

11. Interaction experience issues: Interaction issues that are inconsistent with system interaction or ordinary people’s cognition

12.U compatibility/adaptability issues

13. The hidden part of the page is not hidden (for example: part of the data is displayed)

14. Security protection code (parameter checking, null judgment, type overflow)

15. No toast prompt is given during operation

16. Query error, data column name and value are inconsistent

17.Basic functional errors

middle

ordinary

Some bugs that may or may not be modified, or that are not yet sure whether they can be modified successfully, will not affect the user experience.

1. Very few model adaptation issues

2. It is suggested that the bugs can be corrected or not. Failure to fix them will not affect the version release.

3. Delayed processing of bugs (defects when development is finalized, do not affect the launch of the current version, development can be deferred)

4. Pending bugs (developing technical solutions to be found)

Low