BUG definition of SonarQube

Definition of Defects

SonarQube's definition of BUG is in the problematic part of the code that can cause some errors.Even if it doesn't cause some software system problems now, it needs to be fixed.

Defect Rating

We can see from the above definition that SonarQube scans for potential problems in some code and gives problem confirmation.SonarQube grades defects as follows:

Blocking level: problems that hinder development or testing work; cause system crashes, freezes, and infinite loops, resulting in loss of database data, errors in connection with the database, loss of main functions, and missing basic modules.Such as: code errors, infinite loops, database deadlocks, important first-level menu functions cannot be used, etc. (this problem rarely occurs in the test, once it occurs, the current version test should be stopped immediately).
Severity: The main function of the system is partially lost, the database is saved and called incorrectly, the user data is lost, and the first-level function menu cannot be used but does not affect the test of other functions.The function design is seriously inconsistent with the requirements, the module cannot be started or called, the program restarts, automatically exits, the conflict between the calls between the associated programs, security issues, stability, etc.Such as: errors are displayed in the database after the data is saved in the software, the functions required by the user are missing, the program interface is wrong, the numerical calculation statistics are wrong, etc.
Main level: The function is not fully realized but does not affect the use, the function menu has defects but does not affect the system stability.Such as: long operation time, long query time, wrong format, wrong boundary condition, deletion without confirmation box, too many fields in database table, etc.)
Secondary level: interface, performance defects, suggestions, problems that do not affect the execution of operational functions, solutions that can optimize performance, etc.Such as: typos, irregular interface format, overlapping page displays, hiding what should not be displayed, unclear description, missing prompts, irregular text arrangement, incorrect cursor position, poor user experience, solutions that can optimize performance, etc.(There are many such problems in the early stage of the test, and the priority is low; in the later stage of the test, there are fewer problems and should be dealt with in time)
Prompt level: other (non-defect), including: usability test suggestions from the perspective of customers,Potential requirements unearthed through testing.

Defect Processing Status

Confirmed: The status of a tester's or user's submission when a new issue is discovered

Open: It is confirmed that it is a BUG after discussion by testers and developers, and the status of submission is set by testers.

Solution: It is confirmed by the R&D personnel that it is a BUG repaired state, and the modification has not been verified yet, and is set by the developer.

Close: The tester believes that the problem has been modified, passed the verification, and is set by the tester.

Restart: The tester believes that the bug has not been successfully fixed, and the problem still exists, which is set by the tester.