Thread: Pliz anyone give me examle of Blocker,critical,Major,Mormal,Minor,Tivial,Enhancement

Pliz anyone give me examle of Blocker,critical,Major,Mormal,Minor,Tivial,Enhancement Bug.Itz very urgent....

Introduction:
Bug can be defined as the abnormal behavior of the software. No software exists without a bug. The elimination of bugs from the software depends upon the efficiency of testing done on the software. A bug is a specific concern about the quality of the Application under Test (AUT).

Bug Life Cycle:
In software development process, the bug has a life cycle. The bug should go through the life cycle to be closed. A specific life cycle ensures that the process is standardized. The bug attains different states in the life cycle. The life cycle of the bug can be shown diagrammatically as follows:



The different states of a bug can be summarized as follows:

1. New
2. Open
3. Assign
4. Test
5. Verified
6. Deferred
7. Reopened
8. Duplicate
9. Rejected and
10. Closed

Description of Various Stages:
1. New: When the bug is posted for the first time, its state will be “NEW”. This means that the bug is not yet approved.

2. Open: After a tester has posted a bug, the lead of the tester approves that the bug is genuine and he changes the state as “OPEN”.

3. Assign: Once the lead changes the state as “OPEN”, he assigns the bug to corresponding developer or developer team. The state of the bug now is changed to “ASSIGN”.

4. Test: Once the developer fixes the bug, he has to assign the bug to the testing team for next round of testing. Before he releases the software with bug fixed, he changes the state of bug to “TEST”. It specifies that the bug has been fixed and is released to testing team.

5. Deferred: The bug, changed to deferred state means the bug is expected to be fixed in next releases. The reasons for changing the bug to this state have many factors. Some of them are priority of the bug may be low, lack of time for the release or the bug may not have major effect on the software.

6. Rejected: If the developer feels that the bug is not genuine, he rejects the bug. Then the state of the bug is changed to “REJECTED”.

7. Duplicate: If the bug is repeated twice or the two bugs mention the same concept of the bug, then one bug status is changed to “DUPLICATE”.

8. Verified: Once the bug is fixed and the status is changed to “TEST”, the tester tests the bug. If the bug is not present in the software, he approves that the bug is fixed and changes the status to “VERIFIED”.

9. Reopened: If the bug still exists even after the bug is fixed by the developer, the tester changes the status to “REOPENED”. The bug traverses the life cycle once again.

10. Closed: Once the bug is fixed, it is tested by the tester. If the tester feels that the bug no longer exists in the software, he changes the status of the bug to “CLOSED”. This state means that the bug is fixed, tested and approved.

While defect prevention is much more effective and efficient in reducing the number of defects, most organization conducts defect discovery and removal. Discovering and removing defects is an expensive and inefficient process. It is much more efficient for an organization to conduct activities that prevent defects.

Guidelines on deciding the Severity of Bug:
Indicate the impact each defect has on testing efforts or users and administrators of the application under test. This information is used by developers and management as the basis for assigning priority of work on defects.

A sample guideline for assignment of Priority Levels during the product test phase includes:

Critical / Show Stopper — An item that prevents further testing of the product or function under test can be classified as Critical Bug. No workaround is possible for such bugs. Examples of this include a missing menu option or security permission required to access a function under test.
.
Major / High — A defect that does not function as expected/designed or cause other functionality to fail to meet requirements can be classified as Major Bug. The workaround can be provided for such bugs. Examples of this include inaccurate calculations; the wrong field being updated, etc.
.
Average / Medium — The defects which do not conform to standards and conventions can be classified as Medium Bugs. Easy workarounds exists to achieve functionality objectives. Examples include matching visual and text links which lead to different end points.
.
Minor / Low — Cosmetic defects which does not affect the functionality of the system can be classified as Minor Bugs.


Guidelines on writing Bug Description:
Bug can be expressed as “Result followed by the action”. That means, the unexpected behavior occurring when a particular action takes place can be given as bug description.

Be specific. State the expected behavior which did not occur - such as after pop-up did not appear and the behavior which occurred instead.
Use present tense.
Don’t use unnecessary words.
Don’t add exclamation points. End sentences with a period.
DON’T USE ALL CAPS. Format words in upper and lower case (mixed case).
Mention steps to reproduce the bug compulsorily.

Hi suneetham,
The actual answer your question comes later in this post. But first you should be clear that "Severity" and "Customer Impact" of a bug are two separate issues altogether, and do not necessarily mean the same. From your question, it seems like you consider both terms to be one and the same.

A bug is usually referred to BOTH, by its severity and customer impact. In Bugzilla, bug severity is usually sub-divided into 5 levels, and Customer Impact is sub-divided into 3 levels. These are described below.

Severity of Bug:
1) Showstopper/ Blocker: (Bugs that crashes the entire system, cause buffer overflow, or cause loss of data.)
2) Very Severe/ Critical: (Bugs that cause the system to stop responding to Mouse actions and Keyboard inputs.)
3) Severe (It is primarily different from the previous type, in the sense that it allows users to perform mouse actions and keyboard inputs.)
4) Cosmetic bugs (Bugs that might pertain to spelling mistakes on labels, grammatical errors in sentences in pop-up boxes, or incorrect company logo).
5) Enhancement requests (These are not Bugs, but are requests logged by client, requesting developers to incorporate newer features in a software. These are usually expected to be incorporated during maintenance phase of a software.)

Customer Impact:
1) High: (Bugs in the application that would greatly affect the customer's business.)
2) Medium: (Bugs in the application that would affect the customer's business moderately.)
3) Low: (Bugs in the application that would hardly affect the customer's business.)

As already mentioned, that bugs are referred to by BOTH their Severity, and Customer Impact, so in an interview you would be expected to give examples of bugs with any combination of Severity and Customer Impact.

Now for my answer:
1) Example of a Show stopper bug, causing High Customer Impact:
You can cite the example of Y2K bug, that could have caused systems recognizing the year 2000 in 2-digits to mis-interpret the '00' to mean any year, and could have impacted banks and financial Institutions worldwide that calculate dividend based on number of years for which investment was done.

2) Example of a Cosmetic bug, causing High Customer Impact:
You could cite a hypothetical example wherein a company's logo/symbol on it's website is replaced by a different company's logo/symbol. You could say that even though the system might work flawlessly, it is a cause of a major concern for the customer for which the site was developed.

3) Severity High, and Customer Impact Low:
No such Bug exists. Because any bug that severely affects the system essentially affects the customer in a big way.

There can be many more combinations of Severity and Customer Impact. You should search the net for example of bugs that have made the news, and with your judgment, decide for yourself which bug can be categorized under which combination of Severity and Customer Impact.

Warm Regards,
Bhaskar Srikrishna

Hi Suneetha,

Find below the examples of various defect types mentioned by you:

Blocker
The defect which blocks you to go beyond the testing. It can be explained in two ways:
a. Suppose the test case has 10 or 15 steps and you detect a defect at 10th step it will block you from executing the further steps beyond the 10th one.
b. A defect has been raised for a test case, and this will be a blocker defect and stops the other test cases to start the execution. For example, suppose if you have a test case for testing the entry of text in the text box, and the defect is raised that the text box is not editable. This defect will block the corresponding test cases for testing the login window such as the test case for acceptance of alphabet or alpha-numeric in the text box, the test case to check the non-acceptance of first character of user name not as numeral etc.,

Critical
This the defect that should be fixed for the further processing of the application. One fine example for this kind is in an online banking application, the login window not allowing the user to login even after entering his correct user name and password. The bug will prevents further processing and testing.

Major
The problem affects selected processing to a significant degree, making it inoperable, Cause data loss, or could cause a user to make an incorrect decision or entry.
Example for this kind will be the application allowing the user to getin to the application even after entering the wrong password.

Minor
The problem is cosmetic, and/or does not affect further processing and testing.
Example for this case will be spelling mistakes, logo or images wrongly placed, internal links not working etc.,

Enhancement
These types of bugs are to be fixed at the time of enhancement. These bugs are identified in the usability testing and will be incorporated and fixed at the time of enhancement or next release.

Trivial
This type of defect is also the same as the minor defect where the problem is cosmetic in nature.

Regards,
Ganesan

thanks for ur bug related information. it is very help ful to us

i need some information regarding severity and priority and their examples with high,medium and low. i was faced this question in interview. is the developer any rights to change priorites and severity . plz help me out ..............

thanks
in advance

Originally Posted by hikrsna

thanks for ur bug related information. it is very help ful to us

i need some information regarding severity and priority and their examples with high,medium and low. i was faced this question in interview. is the developer any rights to change priorites and severity . plz help me out ..............

thanks
in advance

Hi,

There are lot of posts in this column for which your question was answered, if you browse you can find it easily.

But in general, Severity is the seriousness of the defect or bug in terms of functionality. Severity is usually set by the QA team to intimate the Development team

The severity of defects is classified as follows:

i. Critical The problem prevents further processing and testing.
ii. High The problem affects selected processing to a significant degree, making it inoperable, Cause data loss, or could cause a user to make an incorrect decision or entry.
iii. Medium The problem affects selected processing, but has a work-around that allows continued processing and testing. No data loss is suffered. These may be cosmetic problems that hamper usability or divulge client-specific information.
iv. Low The problem is cosmetic, and/or does not affect further processing and testing.

Defect Priority tells us how soon it is desired to fix the problem. Priority is the importance of defect in terms of customer's requirements.
Priority is set by the Business / Development Lead for the Development team to prioritize in fixing the defects
i. High Must fix the problem NOW (All other defect fixing tasks take least preference). Problem is blocking further progress in this area.
ii. Medium Should fix the problem soon, before product release
iii. Low Fix the problem if time permits; somewhat trivial. May be postponed

There are different ways of representing the Priority and Severity based on the project requirement.

Regards,
Ganesan

Thank you Ganesan for good explanation.