MUST KNOW! Types of BUG and their levels
Before we talk about types of bug and their levels, first of all what is a Bug? A bug is an error or defect in the system, be it software or hardware, which causes the system to run abnormally even to the point of being unusable. Bugs themselves can be classified according to the level of damage caused so that the classification of these bugs can provide information to developers to prioritize which bugs will be fixed first.
Bugs are classified into 4, namely:
Bug Trivia has the lowest error rate so that sometimes it doesn’t affect the running of a system. Most developers underestimate this type of bug because it deals with small things that they think are not too urgent to be worked on shortly.
Example: The use of views that are not in line with or not according to the design of the UI, the use of typos such as “Sign Up” to “Sing Pu”.
This bug is a middle level whose urgent level can be considered important even though it does not have a big influence on the running of a system. In other words, this bug does not meet your needs or expectations, and it has no effect on the functionality and the system can still perform its main functions.
Example: When we add a member data, after that we save it, usually a success notification will appear on the system, but the data does not appear on the Member List.
The role of this bug is very pronounced on the functionality of the system. Of course, this bug is most often noticed by developers to be worked on immediately, the urgent level is not kidding because when this bug is found, it has a lot of influence on user usage or it may even be that the user cannot use the system properly.
Example: When we add a new member to the system then we save, the system continues to think there is an error in a certain column so that it cannot be saved even though the input we have done is correct, this will make the user very panicked because the user will ask what is wrong with the process carried out.
This type of bug is a bug with the highest level, the effect is so big on the system that the system really can’t be used at all. However, it should be noted that this type of bug is very rarely found in systems that are designed and arranged properly and correctly before the Development process occurs.
Example: Login failed, which gives a server error message after clicking the Login button or, worst of all, the system cannot be opened or used at all
So, now you know what types of bugs are? So, to avoid errors with bugs, make sure you have cross-checked all the writing and commands that existed before you ran your application, OK! Don’t forget to visit IDstar’s Instagram athttps://www.instagram.com/idstar.id/. See you again in the next article!